T08 · Insecure Dependencies
- Location
SKILL.md:89- Finding
Unpinned Global npm Package Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 89–92
Vulnerability Type: Supply-chain exposure through an unpinned globally installed dependency
Risk Level: MediumComplete Code Snippet:
bash ## 安装依赖 ```bash npm i -g clawhub clawhub logintext The same unsafe installation command is also documented in: - `prompts/main.md`, lines 13–15 - `README.md`, lines 55–58 ### Technical Analysis The skill directs users to install the mutable latest version of the `clawhub` npm package globally: ```bash npm i -g clawhubNo exact package version, lockfile, integrity hash, provenance check, or verified package-owner guidance is provided. npm packages may execute lifecycle scripts during installation. Because this installation is global, malicious installation behavior would run with the invoking user's privileges and could affect globally available executables.
This finding does not establish that the current
clawhubpackage is malicious. The vulnerability is the unsafe dependency acquisition process: a compromised package account, registry entry, release pipeline, or unsafe future release could turn the documented command into a local code-execution channel.Attack Path
- An attacker compromises the npm package account, publishing pipeline, or another component responsible for distributing
clawhub. - The attacker publishes a malicious release under the same package name and includes a harmful npm lifecycle script or executable.
- A user follows the skill's documented
npm i -g clawhubinstruction. - npm resolves the mutable current release because no exact reviewed version is specified.
- npm installs the package globally and may execute attacker-controlled lifecycle code.
- The payload runs with the user's privileges and can modify files and global command-line tooling accessible to that account.
Impact Assessment
Successful exploitation could provi ...[truncated 555 chars]
- An attacker compromises the npm package account, publishing pipeline, or another component responsible for distributing
- Remediation
View remediation
Remediation Suggestions
- Replace the mutable install command with a reviewed exact version, for example:
bash npm install --global clawhub@<reviewed-exact-version> - Document the official npm registry location and verified package owner so users can detect typosquatting or registry substitution.
- Verify package provenance, signatures, or published integrity metadata before recommending a release.
- Prefer a project-local, least-privileged installation over a global installation where supported.
- Avoid running npm with administrative privileges.
- Review lifecycle scripts and package contents before approving version updates.
- Keep the pinned command consistent in
SKILL.md,prompts/main.md, andREADME.md.
- Replace the mutable install command with a reviewed exact version, for example:
