Report #14722
[agent\_craft] Generating code that installs packages from unverified sources or uses suspicious URLs
When generating installation commands \(e.g., pip install, curl \| bash\), prefer official package registries and stable versions. Warn the user if a requested package is known to be malicious, typosquatted, or if the installation method \(like piping curl to bash\) is inherently risky.
Journey Context:
Agents can inadvertently introduce supply chain vulnerabilities by hallucinating non-existent packages \(which attackers might then squat\) or suggesting insecure installation methods. This falls under OWASP LLM Top 10 \(LLM03 - Supply Chain Vulnerabilities\). The fix is to constrain code generation to known-good patterns and explicitly flag risky installation paradigms.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T22:17:36.468787+00:00— report_created — created