T08 · Insecure Dependencies
- Location
README.md:9- Finding
Unpinned Third-Party Installation Commands Create a Supply-Chain Risk
- Content
View full analysis
Vulnerability Details
File Location:
README.md, lines 9–19
Vulnerability Type: Unpinned npm tooling and mutable remote Skill source
Risk Level: MediumVulnerable Code
bash Install into Claude Code or Cursor with: ```bash npx skills add https://github.com/wpank/Agentic-Uniswap/tree/main/.ai/skills/execute-swapOr via Clawhub:
bash npx clawhub@latest install execute-swaptext ### Technical Analysis The documented installation procedures rely on components that are not pinned to immutable, previously reviewed versions: - `npx skills` resolves and executes npm-delivered tooling without specifying an exact version. - The GitHub source references the mutable `main` branch rather than an immutable commit SHA. - `npx clawhub@latest` explicitly resolves and executes whichever package version currently has the mutable `latest` tag. - The `execute-swap` package installed through Clawhub is not pinned to a reviewed version or content digest. Consequently, the code and Skill instructions installed by these commands can differ from the content reviewed during this audit. This is a supply-chain weakness rather than evidence that the current upstream dependencies are malicious. ### Attack Path 1. An attacker compromises an npm publisher account, package registry path, Clawhub entry, GitHub account, or upstream repository. 2. The attacker publishes a malicious package version, changes the package associated with `latest`, or modifies content on the referenced `main` branch. 3. A user follows the installation instructions in `README.md`. 4. `npx` retrieves and executes the mutable installer package, or the installer retrieves modified Skill content. 5. Malicious installer code runs with the privileges of the invoking user, or attacker-controlled Skill instructions are installed into the user's agent environment. ### Impact Assessment If the npm-executed installer is compromise ...[truncated 694 chars]- Remediation
View remediation
Remediation Suggestions
- Pin every npm command to a reviewed exact version rather than relying on implicit resolution or
@latest, for example:bash npx clawhub@X.Y.Z install execute-swap@A.B.C - Replace the mutable GitHub branch URL with a URL referencing a reviewed immutable commit SHA.
- Publish cryptographic checksums or signed release artifacts and require verification before installation.
- Use npm provenance, package signatures, lockfiles, and registry integrity metadata where supported.
- Run installation in a sandbox or least-privileged environment without wallet secrets or unrelated credentials.
- Document the exact reviewed versions and commit identifiers so users can reproduce the audited installation.
- Audit the external Agentic-Uniswap MCP server and
trade-executorimplementation separately because transaction execution occurs outside this repository.
- Pin every npm command to a reviewed exact version rather than relying on implicit resolution or
