T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:133- Finding
Remote Installer Downloaded and Executed Without Integrity Verification
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 133-135
Vulnerability Type: Remote payload retrieval and execution
Risk Level: CriticalVulnerable Code
bash curl -LsSf https://astral.sh/uv/install.sh | sh # Windows: powershell -c "irm https://astral.sh/uv/install.ps1 | iex"Technical Analysis
The installation instructions retrieve mutable scripts from an external server and immediately execute them through
shor PowerShelliex. Neither command pins an installer version, verifies a cryptographic checksum or publisher signature, nor gives the user an opportunity to inspect the downloaded content before execution.HTTPS protects the connection in transit but does not guarantee that the delivered script remains identical to the version reviewed during this audit. The effective payload can change whenever the remote installer changes. Compromise of the hosting domain, delivery infrastructure, DNS or TLS trust chain, or upstream release process could therefore turn the documented installation step into arbitrary code execution.
This behavior exceeds the minimum privileges required for document conversion. Converting documents requires a trusted converter and access to designated input and output files; it does not inherently require executing an unverified remote shell script.
Attack Path
- An Agent determines that
uvxis unavailable and follows the setup instructions. curlor PowerShell retrieves the current installer fromastral.sh.- The response is passed directly to a command interpreter without integrity verification.
- A compromised or malicious response executes with the privileges of the user running the Agent.
- The payload can access resources available to that user and may download or execute additional components.
Impact Assessment
Successful exploitation provides arbitrary command execution under the invoking user's account. Depending on that ...[truncated 318 chars]
- An Agent determines that
- Remediation
View remediation
Remediation Suggestions
- Remove all pipe-to-shell and download-to-
iexinstallation instructions. - Prefer a trusted operating-system package manager with package signing and explicit version selection.
- If direct installation is unavoidable, download a version-pinned installer as a separate step.
- Verify the downloaded artifact against a hard-coded cryptographic checksum and, where available, a publisher signature.
- Require explicit user approval before running the verified installer.
- Execute installation without administrator privileges unless a documented, necessary operation specifically requires elevation.
- Document the files and directories modified by installation and provide a removal procedure.
- Pin the expected installer release and review any change before updating the documented hash or signature.
- Remove all pipe-to-shell and download-to-
