T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:14- Finding
Unverified Remote Installer Piped Directly into a Shell
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 14–20
Vulnerability Type: Remote payload retrieval and execution
Risk Level: HighVulnerable Code
json { "id": "uv-install", "kind": "bash", "script": "curl -LsSf https://astral.sh/uv/install.sh | sh", "bins": ["uv"], "label": "Install uv (cross-platform via bash)" }Technical Analysis
The installation command downloads content from
https://astral.sh/uv/install.shand streams it directly tosh. The downloaded payload is not pinned to a specific version, stored for inspection, checksum-verified, or authenticated with a separately verified signature.Although the Astral endpoint is consistent with the declared
uvprerequisite, the effective installer can change after the Skill has been reviewed. A compromise of the remote endpoint, its hosting infrastructure, DNS resolution, or the relevant TLS trust chain could therefore turn Skill installation into arbitrary code execution.This behavior exceeds the minimum privileges required for the declared social-media research functionality. The runtime scripts only need an available Python environment, the
requestsdependency, and access to the ScrapeCreators API; they do not inherently require mutable remote shell code to be executed during installation.Attack Path
- A user or agent initiates installation of the Skill prerequisite.
- The installation framework invokes the configured Bash command.
curlretrieves the current response fromhttps://astral.sh/uv/install.sh.- The response is passed directly to
shwithout local review or integrity verification. - If the response has been maliciously altered, arbitrary shell commands execute with the privileges of the account performing installation.
- Those commands could access user-readable data, modify user-owned files and configuration, install additional payloads, or perform network operations.
...[truncated 688 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove the automatic
curl | shinstallation command and treatuvas an externally managed prerequisite. - Direct users to install
uvthrough a trusted operating-system package manager or another controlled software-distribution mechanism. - If automated installation is essential:
- Pin an exact
uvrelease. - Download the release artifact to disk rather than streaming it into a shell.
- Verify a published cryptographic checksum or signature obtained through a separately trusted channel.
- Abort installation if verification fails.
- Inspect and execute only the verified artifact.
- Pin an exact
- Run installation under an unprivileged account and avoid
sudoor administrator execution. - Where possible, replace runtime dependency resolution with a locked dependency set and verified hashes to improve reproducibility and reduce supply-chain exposure.
- Document the expected files and environment changes made by prerequisite installation so users can assess its scope before approval.
- Remove the automatic
