T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:54- Finding
Unverified Remote Installation Scripts Are Executed Directly
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill does what it says, but it guides users to expose Remote Desktop to the internet with unsafe installer shortcuts and persistent/background access paths that need review before use.
Install only if you explicitly need to expose RDP and can harden it first. Prefer a pinned, verified aitun install over the one-line scripts, use strong credentials and NLA, restrict access where possible, run tunnels in visible foreground sessions for temporary use, and verify that RDP services, daemonized processes, ports, and tokens are stopped or revoked afterward.
SKILL.md:54Unverified Remote Installation Scripts Are Executed Directly
SKILL.md:13Unpinned Third-Party Package Installation Creates Supply-Chain Exposure
SKILL.md:94Persistent RDP Service and Background Tunnel Operation Can Outlive the Intended Session
The skill’s description and opening content promote exposing RDP to the public internet but do not lead with a strong, explicit warning about the substantial attack surface this creates. Internet-facing RDP is a frequent target for brute force, credential stuffing, exploitation of RDP flaws, and unauthorized remote access, so presenting it as 'perfect' for agents materially understates the risk.
curl -fsSL https://aitun.cc/install.sh | bash executes remote code directly in the shell without verification, creating a classic supply-chain/code-execution risk. If the remote server, script, DNS, or transport trust chain is compromised, the user will execute attacker-controlled commands immediately.
Or install via one-line script (Linux/macOS):
curl -fsSL https://aitun.cc/install.sh | bash
Windows (PowerShell):
The | bash chain turns a network fetch into immediate command execution, removing any opportunity for inspection or validation. This amplifies the impact of compromise of the remote source and is a well-known dangerous pattern for initial access or arbitrary code execution.
Or install via one-line script (Linux/macOS):
curl -fsSL https://aitun.cc/install.sh | bash
Windows (PowerShell):
These instructions explicitly enable Remote Desktop on Windows and verify port 3389 listening, which changes the host’s security posture by turning on remote access. Without a prominent warning and gating conditions, a user may enable RDP on a machine that was intentionally not remotely accessible, increasing exposure to unauthorized access.
Repeating the pipe-to-shell installation pattern in the CLI reference normalizes unsafe execution of fetched scripts and increases the chance users adopt it without scrutiny. This is especially risky in a skill that already deals with remote access tooling and privileged system changes.
## CLI Reference
The `aitun` command (installed via `pip install aitun`, or alternatively `curl -fsSL https://aitun.cc/install.sh | bash` / `irm https://aitun.cc/install.ps1 | iex` on Windows) accepts these flags:
| Flag | Description |
|---|---|
The install section offers remote script execution via curl/iex patterns without an explicit warning about supply-chain and code-execution risk. Users are encouraged to run fetched code directly in a shell, which can lead to arbitrary code execution if the hosting site, path, DNS, TLS trust, or upstream content is compromised.
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
# Install xrdp
sudo apt install xrdp -y # Debian/Ubuntu
sudo yum install xrdp -y # CentOS/RHEL
# Start xrdp service
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
# Install xrdp
sudo apt install xrdp -y # Debian/Ubuntu
sudo yum install xrdp -y # CentOS/RHEL
# Start xrdp service
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
sudo yum install xrdp -y # CentOS/RHEL
# Start xrdp service
sudo systemctl start xrdp
sudo systemctl enable xrdp
# Verify it is listening on port 3389
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
sudo yum install xrdp -y # CentOS/RHEL
# Start xrdp service
sudo systemctl start xrdp
sudo systemctl enable xrdp
# Verify it is listening on port 3389
systemctl enable xrdp makes the remote desktop service persist across reboots, which prolongs exposure and can leave internet-accessible remote access active long after the user intended. In a skill specifically about tunneling RDP outward, persistence materially increases the chance of forgotten exposure and unauthorized access.
# Start xrdp service
sudo systemctl start xrdp
sudo systemctl enable xrdp
# Verify it is listening on port 3389
ss -tlnp | grep :3389
The guidance to run aitun tcp-proxy in the background encourages a long-lived bridge process that can quietly continue exposing access paths after the user forgets about it. In the context of public RDP connectivity, background persistence increases operational risk even if the author’s intent appears convenience-focused rather than malicious.
```bash
# Linux/macOS: nohup
nohup aitun tcp-proxy -l 13389 yourname.aitun.cc 3389 >/tmp/rdp-bridge.log 2>&1 &
Using nohup ... & creates a detached long-running proxy that may survive terminal closure and remain available unnoticed. Because this skill is intended to facilitate remote desktop access over the internet, hidden persistence raises the chance of unintended continued exposure.
# Linux/macOS: nohup
nohup aitun tcp-proxy -l 13389 yourname.aitun.cc 3389 >/tmp/rdp-bridge.log 2>&1 &