T08 · Insecure Dependencies
- Location
README.md:10- Finding
Unpinned Third-Party Installation Sources
- Content
View full analysis
Vulnerability Details
File Location:
README.md, lines 10–16
Vulnerability Type: Supply-chain risk caused by mutable, unpinned installation sources
Risk Level: MediumVulnerable Code
bash npx skills add https://github.com/wpank/Agentic-Uniswap/tree/main/.ai/skills/create-test-poolbash npx clawhub@latest install create-test-poolTechnical 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
mainbranch. Its contents can change after this audit without any corresponding change to the command. The Clawhub command usesnpx clawhub@latest, which explicitly executes whichever package release currently carries thelatesttag.Because
npxmay 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
- An attacker compromises the npm publisher account, GitHub repository, upstream maintainer account, or relevant distribution infrastructure.
- The attacker publishes a malicious package under the
latesttag or modifies the content referenced by the repository'smainbranch. - A user runs one of the installation commands documented in
README.md. npxretrieves the current external package and the installer obtains the mutable skill content.- 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
View remediation
Remediation Suggestions
- Replace
npx clawhub@latestwith an exact, reviewed package version. - Pin the GitHub installation source to a specific commit SHA rather than the mutable
mainbranch. - 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-poolbash npx skills add https://github.com/wpank/Agentic-Uniswap/tree/<reviewed-commit-sha>/.ai/skills/create-test-pool- Replace
