T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:50- Finding
Mutable Remote Installers Are Downloaded and Executed Directly
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:50-58andSKILL.md:141
Vulnerability Type: Remote payload retrieval and execution
Risk Level: HighVulnerable Code
markdown Or install via one-line script (Linux/macOS): ```bash curl -fsSL https://aitun.cc/install.sh | bashWindows (PowerShell):
powershell irm https://aitun.cc/install.ps1 | iextext The unsafe alternatives are repeated in the CLI reference at line 141: ```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 documented commands retrieve mutable content from an external server and pass it directly to
bashor PowerShell'sInvoke-Expression. The downloaded payload is not displayed for inspection, pinned to a reviewed version, validated against a checksum, or authenticated with a cryptographic signature.HTTPS protects the connection against ordinary in-transit modification but does not guarantee that the server, hosting account, DNS infrastructure, or published installer remains trustworthy. The effective code executed by the Skill user can therefore change after the Skill itself has been reviewed.
Direct remote shell execution is not necessary for the declared functionality. The document already provides a Python package installation method, so offering pipe-to-shell installation unnecessarily expands the supply-chain attack surface and gives the remote response all privileges held by the invoking user.
Attack Path
- An attacker compromises or gains control over
aitun.cc, its deployment infrastructure, DNS, or the installer publication process. - The attacker modifies
install.shorinstall.ps1to include a malicious payload. - A user or agent follows the installation instructions in
SKILL.md. curlor ...[truncated 848 chars]
- An attacker compromises or gains control over
- Remediation
View remediation
Remediation Suggestions
- Remove the
curl | bashandirm | iexinstallation alternatives from both the installation section and CLI reference. - Prefer a version-pinned package installation from a verified publisher, performed inside a dedicated virtual environment.
- If a standalone installer must be provided:
- Publish immutable, versioned installer artifacts.
- Download the installer to a local file rather than piping it into a shell.
- Publish a SHA-256 digest through a separately protected release channel.
- Verify the digest or a cryptographic signature before execution.
- Allow users to inspect the downloaded script before running it.
- Run installation with the least-privileged account and clearly state that users must not invoke it with
sudo, root, or an elevated PowerShell session unless a documented operation specifically requires elevation. - Document what files, network endpoints, and configuration changes the installer performs.
- Remove the
