T08 · Insecure Dependencies
- Location
README.md:6- Finding
Execution of an Unpinned npm CLI Dependency
- Content
View full analysis
Vulnerability Details
File Location:
README.md:6-8
Vulnerability Type:T08: Insecure Dependencies
Risk Level: Mediumbash npx clawhub@latest install breathing-exerciseTechnical Analysis
The documented installation command instructs users to execute
clawhubthroughnpxusing the mutablelatestdistribution tag. If the package is not already installed locally,npxcan retrieve it from the configured npm registry and execute its code immediately.Because neither a specific reviewed version nor an integrity value is supplied, the code executed by this command can change after the skill has been audited. The project artifact contains only documentation and metadata, so the remotely retrieved CLI implementation is outside the reviewed scope. A compromised package publisher account, malicious package release, registry compromise, or unexpected update could therefore introduce executable behavior that was not present during this audit.
Attack Path
- An attacker compromises the
clawhubpackage, its publisher account, or the package-distribution channel. - The attacker publishes a malicious release and assigns or causes it to receive the
latesttag. - A user follows the installation instructions and runs
npx clawhub@latest install breathing-exercise. npxdownloads the mutable package release from the configured registry.- Package lifecycle behavior or CLI entry-point code executes with the privileges of the user running the command.
- The malicious dependency can perform actions permitted to that user, such as reading accessible files, modifying user-level configuration, making network requests, or installing additional components.
Impact Assessment
Successful exploitation would provide code execution with the privileges and environmental access of the user invoking
npx. For an ordinary account, the scope generally includes that user's files, credentials exposed t ...[truncated 492 chars]- An attacker compromises the
- Remediation
View remediation
Remediation Suggestions
- Replace the mutable
latesttag with an explicitly reviewed package version, for examplenpx clawhub@<reviewed-version>. - Verify the selected release against a trusted checksum, package signature, provenance attestation, or npm integrity metadata before execution.
- Document the expected registry and package publisher so users can detect registry substitution or similarly named packages.
- Prefer installing dependencies through a committed lockfile with integrity hashes rather than downloading and executing a mutable release directly.
- Review the selected CLI package, including its executable entry points and lifecycle scripts, before recommending it.
- In CI or other sensitive environments, execute installation with minimal privileges, restricted credentials, and limited filesystem and network access.
- Update the audit whenever the pinned dependency version changes.
- Replace the mutable
