T08 · Insecure Dependencies
- Location
README.md:9- Finding
Unpinned Installation Tools and Mutable Remote Skill Source
- Content
View full analysis
Vulnerability Details
File Location:
README.md, lines 9–15
Vulnerability Type: Supply-chain exposure through unpinned installation tools and mutable remote content
Risk Level: MediumVulnerable Code
bash npx skills add https://github.com/wpank/Agentic-Uniswap/tree/main/.ai/skills/rebalance-positionbash npx clawhub@latest install rebalance-positionTechnical Analysis
The documented installation commands execute npm-resolved command-line tools without pinning them to audited package versions or integrity hashes. The first command also installs Skill content from the mutable
mainbranch of a remote GitHub repository. The second command explicitly selects the mutablelatestversion of the Clawhub installer.Consequently, the code executed or installed when a user follows these instructions can differ from the files reviewed during this audit. This creates a time-of-check/time-of-use supply-chain boundary: compromise of an npm publisher account, the GitHub repository, its maintainers, the branch, or the relevant distribution infrastructure could substitute malicious installer code or Skill content.
No malicious dependency or current compromise was established. The vulnerability is the unsafe installation pattern and its exposure to future upstream changes.
Attack Path
- An attacker compromises an applicable npm publisher account, GitHub maintainer account, repository, release process, or distribution channel.
- The attacker publishes a malicious package version or modifies the Skill content referenced by the mutable
mainbranch. - A user follows one of the documented
npxinstallation commands. npxresolves and executes the altered tool, or the installer retrieves altered Skill content.- The malicious installer or installed Skill executes under the installing user's account.
Impact Assessment
Successful exploitation could allow arbitrary code execut ...[truncated 535 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin each npm command-line tool to an exact reviewed version rather than relying on implicit resolution or
@latest. - Replace the mutable GitHub
mainbranch URL with a reviewed commit SHA or immutable signed release tag. - Publish and verify cryptographic checksums or signatures for the installer and Skill package.
- Use lockfiles and npm integrity metadata where applicable.
- Document the expected package version, repository commit, and checksum so users can verify provenance before installation.
- Recommend installation in a least-privileged or sandboxed environment and caution users against running installers with administrative privileges.
- Establish release signing, protected branches, mandatory review, and multi-factor authentication for package and repository maintainers.
- Pin each npm command-line tool to an exact reviewed version rather than relying on implicit resolution or
