T08 · Insecure Dependencies
Warning
- Location
- README.md:10
- Finding
- Unpinned Third-Party Installation Sources## Vulnerability Details **File Location**: `README.md`, lines 10–16 **Vulnerability Type**: Supply-chain risk caused by mutable, unpinned installation sources **Risk Level**: Medium ### Vulnerable Code ```bash npx skills add https://github.com/wpank/Agentic-Uniswap/tree/main/.ai/skills/create-test-pool ``` ```bash npx clawhub@latest install create-test-pool ``` ### Technical Analysis The documented installation procedures depend on mutable external resources without pinning them to reviewed versions or cryptographic integrity values. The GitHub installation command retrieves the skill from the repository's mutable `main` branch. Its contents can change after this audit without any corresponding change to the command. The Clawhub command uses `npx clawhub@latest`, which explicitly executes whichever package release currently carries the `latest` tag. Because `npx` may download and execute package-provided code, users following these instructions must trust the npm registry package, its publisher account, the external repository, and their respective distribution infrastructure. Compromise of any of those components could cause installation or execution of content that was not included in the audited project. ### Attack Path 1. An attacker compromises the npm publisher account, GitHub repository, upstream maintainer account, or relevant distribution infrastructure. 2. The attacker publishes a malicious package under the `latest` tag or modifies the content referenced by the repository's `main` branch. 3. A user runs one of the installation commands documented in `README.md`. 4. `npx` retrieves the current external package and the installer obtains the mutable skill content. 5. The unreviewed version may execute installation-time code or install malicious skill instructions into the user's agent environment. This path depends on an upstream compromise or malicious upstream update; the audited files themselves do ...[truncated 696 chars]
- Remediation
- ## Remediation Suggestions - Replace `npx clawhub@latest` with an exact, reviewed package version. - Pin the GitHub installation source to a specific commit SHA rather than the mutable `main` branch. - Record and verify cryptographic checksums or package integrity metadata before installation. - Use lockfiles and reproducible installation procedures where supported. - Review npm lifecycle scripts and installer behavior before approving a release. - Prefer trusted organizational repositories and protected release workflows with mandatory review. - Use signed commits, signed release artifacts, provenance attestations, and automated dependency scanning. - Run installation in a least-privileged or sandboxed environment, without unnecessary credentials or filesystem access. Example hardened forms, subject to installer support: ```bash npx clawhub@<reviewed-exact-version> install create-test-pool ``` ```bash npx skills add https://github.com/wpank/Agentic-Uniswap/tree/<reviewed-commit-sha>/.ai/skills/create-test-pool ```
