T03 · Remote Payload Retrieval and Execution
- Location
README.md:18- Finding
Unverified Remote Installer Is Downloaded and Executed Directly in the English Installation Guide
- Content
View full analysis
Vulnerability Details
File Location:
README.md, lines 18-27
Vulnerability Type: Remote payload retrieval and execution
Risk Level: HighVulnerable Code
markdown **macOS and Linux:** ```bash curl -LsSf https://astral.sh/uv/install.sh | shWindows:
powershell powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"text ### Technical Analysis The installation instructions download mutable content from an external URL and immediately pass it to a command interpreter. The Unix command pipes the HTTP response directly into `sh`, while the Windows command uses `Invoke-RestMethod` and `Invoke-Expression` with the execution policy bypassed. No version is pinned, and the instructions do not require a checksum, cryptographic signature, local inspection, or separation between download and execution. Consequently, the code executed by users can change after this repository has been reviewed. The repository contents alone cannot establish the ongoing integrity of the remote scripts. Although installing `uv` supports the documented workflow, immediate remote-to-shell execution is not necessary for the Skill's functionality and does not follow least-privilege or supply-chain hardening principles. ### Attack Path 1. A user follows the installation instructions in `README.md`. 2. The shell or PowerShell client retrieves the current response from the external installer URL. 3. An attacker compromises the hosting account, distribution infrastructure, DNS/TLS path, or another component capable of controlling the returned content. 4. The attacker substitutes or modifies the installer response with arbitrary commands. 5. The pipeline executes those commands immediately, without giving the user an opportunity to inspect or verify the payload. 6. The malicious payload operates with the privileges of the user who launched the command. ### Impact Assessment Suc ...[truncated 780 chars]- Remediation
View remediation
Remediation Suggestions
- Remove the
curl | shandirm | iexinstallation methods from the primary setup instructions. - Prefer a trusted operating-system package manager with a pinned or constrained version where available.
- If a standalone installer is required:
- Link to a specific, immutable release artifact.
- Download it to a local file without executing it.
- Verify a published cryptographic checksum or signature.
- Allow the user to inspect the downloaded script.
- Execute it only after successful verification.
- Do not recommend bypassing PowerShell execution policy.
- Document that installation should occur as an unprivileged user and should not use
sudo, root, or an elevated PowerShell session unless strictly required. - Maintain a lockfile and integrity controls for the Python dependencies subsequently installed by
uv.
- Remove the
