T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:53- Finding
Unverified Remote Installation Scripts Are Executed Directly
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:53-60, repeated atSKILL.md:134
Vulnerability Type: Remote payload retrieval and immediate shell execution
Risk Level: CriticalVulnerable Code
bash Or install via one-line script (Linux/macOS): ```bash curl -fsSL https://aitun.cc/install.sh | bashtext ```powershell Windows (PowerShell): ```powershell irm https://aitun.cc/install.ps1 | iextext The same installation methods are repeated in the CLI reference: ```markdown 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:Technical Analysis
The Linux/macOS command downloads mutable content from an external server and sends it directly to Bash. The Windows equivalent retrieves remote content and passes it directly to
Invoke-Expression. In both cases, the fetched payload is executed without being stored for inspection, pinned to a reviewed version, or checked using a cryptographic hash or signature.HTTPS protects the network transport but does not establish the integrity or continued trustworthiness of the script publisher. The effective installation payload can change after this Skill has been reviewed. A compromise of the website, DNS resolution, publishing infrastructure, or account controlling the domain could consequently turn an ordinary installation into arbitrary local code execution.
These methods exceed the minimum behavior necessary for the declared tunneling functionality because the document already provides package-manager installation alternatives. Nothing in the declared functionality requires an unaudited remote script to be executed directly.
Attack Path
- An agent follows the installation instructions in
SKILL.md. - The agent requests
https://aitun.cc/install.shor `https://aitun.cc/install.p ...[truncated 1102 chars]
- An agent follows the installation instructions in
- Remediation
View remediation
Remediation Suggestions
- Remove both direct execution patterns:
curl ... | bashirm ... | iex
- Prefer an audited package-manager installation pinned to an exact version.
- If an installation script must be provided:
- Download it to a local file without executing it.
- Pin it to a versioned, immutable release URL.
- Publish and verify a SHA-256 or stronger cryptographic checksum.
- Prefer a verifiable code-signing mechanism.
- Require inspection and explicit user approval before execution.
- Never request root or administrator execution unless a documented installation operation strictly requires it.
- Host release artifacts through a transparent release process and document their provenance.
- Update the repeated CLI-reference text at line 134 so the unsafe alternatives are not reintroduced elsewhere in the Skill.
- Remove both direct execution patterns:
