T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:53- Finding
Unverified Remote Installation Scripts Are Executed Directly
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is not clearly malicious, but it publishes SSH access to the internet and includes unsafe installation and connection examples that users should review carefully.
Only install this if you intentionally want to expose an SSH server through aitun. Prefer a pinned, verified package installation over the one-line scripts, avoid running installers as root, use key-only SSH with password login disabled, use a least-privilege account, rotate any token placed on a command line, and stop the tunnel when finished.
SKILL.md:53Unverified Remote Installation Scripts Are Executed Directly
SKILL.md:16Unpinned Third-Party Package Installation
SKILL.md:193Example Disables TLS Certificate Validation and Omits SSH Host-Key Verification
SKILL.md:102Tunnel Authentication Token Is Passed Through Process Arguments
curl -fsSL https://aitun.cc/install.sh | bash fetches and executes remote code in a single step with no integrity verification, review, or pinning. If the server, CDN, DNS, TLS trust chain, or upstream script is compromised, users can execute attacker-controlled code immediately on their machine.
Or install via one-line script (Linux/macOS):
curl -fsSL https://aitun.cc/install.sh | bash
Windows (PowerShell):
The | bash construct directly chains untrusted network content into shell execution, eliminating any opportunity for inspection or validation. This materially increases the blast radius of a compromise because a single malicious response results in arbitrary command execution.
Or install via one-line script (Linux/macOS):
curl -fsSL https://aitun.cc/install.sh | bash
Windows (PowerShell):
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
ssh user@yourname.t.aitun.cc
# With SSH key
ssh -i ~/.ssh/id_rsa user@yourname.t.aitun.cc
# With verbose output for debugging
ssh -v user@yourname.t.aitun.cc
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
ssh user@yourname.t.aitun.cc
# With SSH key
ssh -i ~/.ssh/id_rsa user@yourname.t.aitun.cc
# With verbose output for debugging
ssh -v user@yourname.t.aitun.cc
Repeating the pipe-to-shell install pattern in the CLI reference normalizes insecure software installation and increases the likelihood users will execute unverified remote code. This is especially risky in a skill that already deals with network exposure and privileged system setup.
## 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 skill’s purpose is to expose a local SSH service to the public internet, but the description/front matter does not prominently warn users that this creates a remotely reachable login surface. In this context, omission of an upfront warning is dangerous because users may enable internet exposure without understanding risks like brute force attacks, credential compromise, or unintended access to an internal machine.
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
# Ubuntu/Debian
sudo apt install openssh-server -y
sudo systemctl start sshd
# CentOS/RHEL
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
# Ubuntu/Debian
sudo apt install openssh-server -y
sudo systemctl start sshd
# CentOS/RHEL
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
# Ubuntu/Debian
sudo apt install openssh-server -y
sudo systemctl start sshd
# CentOS/RHEL
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
sudo systemctl start sshd
# CentOS/RHEL
sudo yum install openssh-server -y
sudo systemctl start sshd
# macOS (usually pre-installed)
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
sudo systemctl start sshd
# CentOS/RHEL
sudo yum install openssh-server -y
sudo systemctl start sshd
# macOS (usually pre-installed)
The remote SSH examples show how to connect and run commands against the exposed host, but they do not directly warn that anyone with valid access can execute shell commands on the machine being exposed. Because this skill is specifically for remote shell access, the missing warning increases the chance that users expose sensitive systems without appreciating that they are granting command execution capability.
The Python example explicitly disables TLS hostname verification and certificate validation with check_hostname = False and verify_mode = ssl.CERT_NONE. That permits man-in-the-middle interception of the outer TLS layer, undermining the claimed SSH-over-TLS security guarantees and exposing SSH sessions to traffic interception or redirection to an attacker-controlled endpoint.