T08 · Insecure Dependencies
- Location
README.md:23- Finding
Unpinned Remote Package Execution in Installation Instructions
- Content
View full analysis
Vulnerability Details
File Location:
README.md:23-26
Vulnerability Type: Supply-chain risk from executing a mutable remote package version
Risk Level: MediumVulnerable Code Snippet:
bash # Or as an OpenClaw skill via ClawHub npx clawhub@latest install claude-usageTechnical Analysis
The documented installation command instructs users to execute
clawhub@latestthroughnpx. Thelatesttag is mutable and does not identify the exact package release reviewed by the user or project maintainer.npxmay download the selected package and execute its entry point locally.Consequently, the code executed during installation can change after this project has been audited. The command does not pin an exact version or verify an integrity digest. If the upstream package, publisher account, registry record, or release process is compromised, following the documented instructions could execute an attacker-controlled installer.
This is a supply-chain weakness in the installation documentation rather than evidence that the bundled project scripts are malicious.
Attack Path
- An attacker compromises the upstream
clawhubpackage, its publishing credentials, or the package registry distribution channel. - The attacker publishes a malicious release and assigns or causes the mutable
latesttag to resolve to that release. - A user follows the installation command from
README.md. npxretrieves the package currently referenced byclawhub@latest.- The downloaded package executes with the permissions of the user running the command.
- Malicious package code can perform actions permitted to that user before or during installation.
Impact Assessment
Successful exploitation could provide arbitrary code execution with the privileges of the user invoking
npx. Depending on that user's permissions and environment, the malicious dependency could access user-readable files, envir ...[truncated 350 chars]- An attacker compromises the upstream
- Remediation
View remediation
Remediation Suggestions
- Replace the mutable
latesttag with an exact, reviewed package version, for example:bash npx clawhub@<reviewed-version> install claude-usage - Document the expected package publisher, registry, and release provenance so users can verify that they are retrieving the intended package.
- Where supported, verify the downloaded package against a published cryptographic checksum, signature, or registry integrity digest.
- Review new installer versions before updating the pinned command.
- Advise users not to run the installation command with administrator or root privileges.
- Consider documenting a manual installation method that allows users to inspect the installer before execution.
- Replace the mutable
