T03 · Remote Payload Retrieval and Execution
Error
- Location
- SKILL.md:71
- Finding
- Unverified Remote Script Piped Directly into Bash## Vulnerability Details **File Location**: `SKILL.md`, line 71 **Vulnerability Type**: Remote payload retrieval and execution **Risk Level**: High **Vulnerable Code**: ```bash curl -L https://foundry.paradigm.xyz | bash && foundryup ``` ### Technical Analysis The installation instruction uses `curl -L` to retrieve mutable content from an external URL and passes the response directly to Bash. Redirect following is enabled, so code returned by either the original server or any server in the redirect chain is executed immediately. The payload is not pinned to a version, saved for inspection, checked against a cryptographic digest, or verified with a trusted digital signature. Consequently, the code actually executed can change after the Skill has been reviewed. Although installing Foundry is relevant to the declared smart-contract development workflow and the named domain appears associated with Foundry, direct remote-to-shell execution is not required to provide that functionality. ### Attack Path 1. A user or agent follows the Foundry setup instructions. 2. The command requests content from `https://foundry.paradigm.xyz` and follows redirects. 3. The source endpoint, hosting infrastructure, DNS resolution, or redirect destination is compromised or otherwise serves altered content. 4. The altered response is streamed directly into Bash without inspection or integrity verification. 5. The malicious script executes with the privileges of the user running the command. 6. The payload can access data and perform operations available to that user, potentially including reading project files and wallet-related secrets, modifying files, installing additional software, or initiating network connections. ### Impact Assessment Successful exploitation provides arbitrary command execution under the invoking user's account. The precise scope depends on that account's permissions and environment. Potentially exposed assets i ...[truncated 516 chars]
- Remediation
- ## Remediation Suggestions Replace the `curl | bash` workflow with a verifiable installation process: 1. Obtain a version-pinned release artifact from the project's authenticated official release channel. 2. Download the artifact to a local file rather than streaming it into a shell. 3. Verify it against a checksum or cryptographic signature published through an independently trusted channel. 4. Abort installation if verification fails. 5. Inspect the installer or use a reputable package manager where practical. 6. Execute installation with an unprivileged account and request elevated privileges only for narrowly defined operations when necessary. 7. Pin the Foundry version to reduce unreviewed supply-chain changes and document how users can update it safely. At minimum, separate retrieval from execution and display an explicit warning that externally downloaded installation code must be authenticated before it is run.