T08 · Insecure Dependencies
- Location
.- Finding
Mutable Package Version Executed Through npx
- Content
View full analysis
Vulnerability Details
File Location:
README.md:43,SKILL.md:127, andSKILL.md:185
Vulnerability Type: Unsafe execution of an unpinned third-party dependency
Risk Level: MediumVulnerable Code
README.md:43:bash npx clawhub@latest install advisor-board-proSKILL.md:127:bash npx clawhub@latest install advisor-board-proSKILL.md:185:bash npx clawhub@latest install advisor-board-proTechnical Analysis
The documented installation procedure uses
npxto retrieve and execute the mutablelatestrelease of the third-partyclawhubpackage. The project does not pin an audited package version, provide an integrity hash, identify a verified source repository, or include a lockfile that would make the executed dependency reproducible.Because the
latesttag can be reassigned whenever a new package version is published, the effective code executed by users can change after this project has been reviewed. The two documentation files contain no implementation of the advertised skill, so the security properties of the installation and resulting skill depend entirely on externally retrieved package content that is outside the audited artifact.This is a supply-chain exposure rather than evidence that the current external package is malicious. Exploitation requires compromise or malicious control of the package publication channel, publisher account, registry resolution, or a subsequently published release.
Attack Path
- An attacker compromises the package publisher account or another relevant part of the package distribution chain.
- The attacker publishes a malicious
clawhubrelease and assigns it to thelatesttag. - A user follows the installation instructions and runs
npx clawhub@latest install advisor-board-pro. npxresolves and retrieves the attacker-controlled release.- The malicious package code or lifecycle behavior executes ...[truncated 839 chars]
- Remediation
View remediation
Remediation Suggestions
- Replace the mutable
latesttag with an exact, reviewed package version, for example:bash npx clawhub@1.2.3 install advisor-board-pro - Verify the selected release before recommending it, including its package contents, lifecycle scripts, maintainer identity, and dependency tree.
- Publish and verify package integrity metadata or cryptographic signatures where supported.
- Document the official registry and source repository so users can confirm the package's provenance.
- Use lockfiles and reproducible installation procedures for any maintained implementation.
- Avoid running the installation command with administrator or root privileges.
- Consider installing the reviewed package without immediately executing it, inspecting its contents first, and then invoking a locally pinned binary.
- Add an automated dependency-review process that detects publisher changes, unexpected lifecycle scripts, integrity changes, and newly introduced transitive dependencies.
- Replace the mutable
