T08 · Insecure Dependencies
Warning
- Location
- README.md:9
- Finding
- Unpinned Third-Party Installation Sources Create Supply-Chain Risk## Vulnerability Details **File Location**: `README.md`, lines 9–19 **Vulnerability Type**: Unpinned and mutable third-party installation sources **Risk Level**: Medium ### Vulnerable Code ```markdown Install into Claude Code or Cursor with: ```bash npx skills add https://github.com/wpank/Agentic-Uniswap/tree/main/.ai/skills/research-token ``` Or via Clawhub: ```bash npx clawhub@latest install research-token ``` ``` ### Technical Analysis The documented installation procedure instructs users to retrieve and execute third-party npm tooling through `npx`. The Clawhub command explicitly selects the mutable `latest` package version, while the GitHub installation source refers to the mutable `main` branch rather than a reviewed commit. Consequently, the code and Skill content installed by these commands can change after this audit without any corresponding modification to the audited repository. No version pin, commit hash, checksum, or signature is provided to ensure that users receive the reviewed content. This is a supply-chain weakness rather than evidence that the current upstream packages are malicious. Exploitation would require an attacker to compromise an upstream package, publisher account, registry distribution path, repository, or future release. ### Attack Path 1. An attacker compromises the upstream npm publisher, package, GitHub repository, or another relevant distribution component. 2. The attacker publishes a malicious package version under the mutable `latest` tag or modifies content reachable through the GitHub `main` branch. 3. A user follows the installation instructions in `README.md`. 4. `npx` downloads and executes the current third-party installer with the user's local privileges. 5. The compromised installer or remote Skill content executes malicious behavior or installs altered instructions into the user's agent environment. ### Impact Assessment Successful exploitation could ...[truncated 582 chars]
- Remediation
- ## Remediation Suggestions 1. Replace `clawhub@latest` with an exact, reviewed package version. 2. Pin the GitHub source to an immutable commit hash instead of the `main` branch. 3. Provide cryptographic checksums or signed release artifacts and document how users should verify them before installation. 4. Identify the expected package publisher and repository ownership so users can validate the source. 5. Review installation scripts and transitive dependencies before updating pinned versions. 6. Where supported, use lockfiles, package integrity metadata, and a trusted dependency mirror. 7. Recommend installation under a least-privileged account or isolated environment and warn users not to run the commands with elevated privileges.