T03 · Remote Payload Retrieval and Execution
- Location
scripts/setup.sh:100- Finding
Unverified Remote Installer Is Piped Directly to a Shell
- Content
View full analysis
/dev/null | sh 2>/dev/null; then ``` The error guidance at lines 107 and 111 also recommends executing: ```bash curl -LsSf https://astral.sh/uv/install.sh | sh ``` ### Technical Analysis The setup script downloads mutable content from an external URL and pipes it directly to `sh`. It does not pin an installer version, verify a cryptographic digest or signature, save the script for inspection, or obtain explicit approval immediately before execution. Although `astral.sh` is associated with the declared `uv` dependency, reliance on HTTPS and domain reputation alone does not establish the integrity of mutable executable content. A compromised origin, CDN, DNS path, certificate trust chain, or upstream deployment could alter the effective payload after this Skill has been reviewed. Redirecting standard error to `/dev/null` also suppresses information that could reveal unexpected installer behavior or failures. ### Attack Path 1. The user or Agent runs `scripts/setup.sh`. 2. The script determines that neither `uv` nor `pipx` is installed. 3. The script requests `https://astral.sh/uv/install.sh`. 4. The upstream response is compromised or changed maliciously. 5. The response is passed directly to `sh` without integrity verification. 6. The payload executes immediately with all permissions of the user running the setup script. ### Impact Assessment A malicious installer could execute arbitrary commands under the Agent user's account. Depending on that user's permissions, it could read or modify project files, shell configuration, credentials, browser data, API keys, and user-owned files. If the setup script is run by a privileged account, the impact could extend to system-wide compromise. ]]>- Remediation
View remediation
