T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:55- Finding
Remote Installation Scripts Executed Without Integrity Verification
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This is a coherent uv package-manager guide, but it recommends several high-impact install patterns that execute or import mutable external code without verification.
Review before installing. The skill is a normal uv usage guide, but do not blindly copy the quick-install, CI, or Docker examples into a sensitive workstation or build environment. Prefer package-manager installs, pinned versions, pinned GitHub Action commits, pinned container digests, and checksum or signature verification where available.
SKILL.md:55Remote Installation Scripts Executed Without Integrity Verification
SKILL.md:61Unpinned Package and Git-Based Installation Sources
SKILL.md:383GitHub Action Referenced Through a Mutable Major-Version Tag
SKILL.md:409Docker Build Copies Executable From an Unpinned Latest Image
SKILL.md:434Multi-Stage Docker Build Uses an Unpinned Latest Image
The | sh construct chains network retrieval directly into shell execution, eliminating any opportunity for review before code runs. This pattern is especially dangerous in instructional content because it encourages habitual execution of opaque remote code.
# macOS/Linux
curl -LsSf https://astral.sh/uv/install.sh | sh
# Windows (PowerShell)
powershell -c "irm https://astral.sh/uv/install.ps1 | iex"
YARA rule matched a known malware signature (reverse shell, backdoor, ransomware, C2 framework, or info stealer).
eEnvironment": true, "python.testing.pytestEnabled": true, "python.testing.pytestArgs": ["-v"], "python.linting.enabled": true, "python.formatting.provider": "black", "[python]": { "editor.defaultFormatter": "ms-python.black-formatter", "editor.formatOnSave": true } }
## Troubleshooting
### Common Issues
```bash
# Issue: uv not found
# Solution: Add to PATH or reinstall
echo 'export PATH="$HOME/.cargo/bin:$PATH"' >> ~/.bashrc
# Issue: Wrong Python version
# Solution: Pin version explicitly
uv python pin 3.12
uv venv --python 3.12
# Issue: Dependency conflict
# Solution: Check resolution
uv lock --verbose
# Issue: Cache issues
# Solution: Clear cache
uv cache clean
# Issue: Lockfile out of sync
# Solution: Regenerate
uv lock --upgrade
The skill instructs users to pipe a remotely fetched installer script directly into a shell, which executes unreviewed network content with the user's privileges. If the remote host, transport path, or script content is compromised, this becomes an immediate arbitrary code execution path.
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
# Create lockfile (uv.lock)
uv lock
# Install from lockfile (exact versions)
The command fetches an external script over the network and immediately executes it, giving remote content direct influence over the local system. In a developer-oriented skill, users are likely to copy-paste this verbatim, increasing the chance of supply-chain compromise or man-in-the-middle impact if trust assumptions fail.
# macOS/Linux
curl -LsSf https://astral.sh/uv/install.sh | sh
# Windows (PowerShell)
powershell -c "irm https://astral.sh/uv/install.ps1 | iex"
No suspicious patterns detected.