T08 · Insecure Dependencies
- Location
README.md:15- Finding
Unpinned npm CLI Package Execution in English Installation Guide
- Content
View full analysis
Vulnerability Details
File Location:
README.md, lines 15-17
Vulnerability Type: Supply-chain risk caused by executing an unpinned npm package
Risk Level: MediumComplete Code Snippet:
bash npx clawhub install maxhub-redditTechnical Analysis
The installation guide invokes
clawhubthroughnpxwithout specifying a package version, lockfile, or integrity hash. If the package is not available locally,npxcan retrieve and execute the version currently resolved by the npm registry.This makes the executed installation code mutable after the Skill has been reviewed. The safety of the command consequently depends on the ongoing integrity of the npm package, its publisher account, and its dependency tree. The repository provides no mechanism for ensuring that users execute the same reviewed CLI release.
Attack Path
- An attacker compromises the npm publisher account for
clawhub, compromises one of its dependencies, or otherwise causes a malicious version to be resolved. - A user follows the installation command in
README.md. npxdownloads the currently resolved, unpinned package version.- Package lifecycle logic or the CLI entry point executes with the privileges of the user running the command.
- The malicious package can perform arbitrary actions available to that user before or during Skill installation.
Impact Assessment
Successful exploitation could provide arbitrary code execution with the installing user's privileges. Depending on the host environment and user permissions, the malicious package could read user-accessible files and environment variables, steal credentials, alter local configuration, install modified Skill content, access network resources, or tamper with other user-owned files.
The command does not inherently grant administrative privileges, so the direct scope is limited to the permissions of the invoking user. The impact may nevertheless b ...[truncated 168 chars]
- An attacker compromises the npm publisher account for
- Remediation
View remediation
Remediation Suggestions
- Pin the CLI to a specifically reviewed release:
bash npx clawhub@<verified-version> install maxhub-reddit - Verify and document the expected package publisher, registry, release provenance, and checksum or integrity metadata.
- Prefer a trusted, already installed local CLI where operationally practical, and provide instructions for verifying its version before use.
- Use lockfiles and reproducible dependency resolution in automated installation environments.
- Disable or carefully review dependency lifecycle scripts where the package manager and workflow permit it.
- Run installation with an unprivileged account and avoid exposing unrelated credentials or sensitive environment variables to the installer.
- Pin the CLI to a specifically reviewed release:
