T08 · Insecure Dependencies
- Location
install.sh:21- Finding
Unpinned Third-Party Dependencies Execute Mutable Supply-Chain Code
- Content
View full analysis
/dev/null || true ``` Related documentation also recommends executing a mutable npm release: ```bash npx clawhub@latest install agentic-ai-gold ``` This instruction appears in `skill.md:29-31` and `QUICKSTART.md:5-7`. A similar command using a different package identifier appears in `README.md:34-36`. ### Technical Analysis The installer downloads and installs six Python packages without exact version constraints or integrity hashes. Consequently, the installed code is determined by the package registry at installation time rather than by the reviewed project contents. Python package installation can execute package build hooks and other package-controlled code with the privileges of the user running the installer. The documented `npx ...@latest` commands similarly request a mutable npm release whose contents may change after this audit. The command also redirects standard error to `/dev/null` and uses `|| true`. This masks dependency resolution errors, integrity problems, package build failures, and partial installation. The installer can therefore continue and report success even when its dependency installation failed or produced an inconsistent environment. No evidence establishes that the named dependencies are currently malicious. The vulnerability is the unbounded and mutable supply-chain trust introduced by the installation process. ### Attack Path 1. An attacker compromises one of the referenced package releases, its maintainer account, its distribution infrastructure, or a mutable `latest` release. 2. A user follows the installation instructions or runs `install.sh`. 3. `pip` or `npx` download ...[truncated 724 chars]- Remediation
View remediation
/dev/null || true`; installation must fail visibly when a dependency cannot be securely installed. 7. Perform installation in an isolated virtual environment rather than modifying the user's general Python environment. 8. Add automated dependency vulnerability, provenance, and package-name verification. 9. Document the expected versions and verify them after installation. ]]>
