T08 · Insecure Dependencies
- Location
SKILL.md:4- Finding
Unpinned Global npm Dependency Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 4 and 9–12
Vulnerability Type: Unpinned third-party package installed globally
Risk Level: MediumVulnerable Code
yaml metadata: {"clawdbot":{"requires":{"bins":["clawdhub"]},"install":[{"id":"node","kind":"node","package":"clawdhub","bins":["clawdhub"],"label":"Install ClawdHub CLI (npm)"}]}}bash npm i -g clawdhubTechnical Analysis
The skill directs users to install the latest available version of the third-party
clawdhubnpm package globally, without pinning a reviewed version or verifying package integrity. The metadata likewise specifies only the package name.Consequently, the code installed when the instruction is followed can change after this skill has been audited. npm packages may execute lifecycle scripts during installation. If the package, its maintainer account, or one of its transitive dependencies is compromised, attacker-controlled code could execute with the privileges of the user running npm. Global installation also places the resulting executable in a shared command path, increasing its reach beyond this skill.
No evidence establishes that the current
clawdhubpackage is malicious. The confirmed issue is the unsafe, unpinned dependency-installation practice and the resulting supply-chain exposure.Attack Path
- An attacker compromises the
clawdhubnpm package, a maintainer account, or a transitive dependency, and publishes a malicious release. - A user or agent follows
SKILL.mdand executesnpm i -g clawdhubwithout selecting a reviewed version or checking integrity. - npm retrieves the attacker-controlled release and may run its lifecycle scripts during installation.
- Malicious code executes with the installing user's privileges.
- The globally installed executable can subsequently run whenever the user or agent invokes
clawdhub.
Impact Assessment
Successful exploitati ...[truncated 457 chars]
- An attacker compromises the
- Remediation
View remediation
Remediation Suggestions
- Pin the dependency to a specifically reviewed release in both metadata and installation instructions, for example:
bash npm install --global clawdhub@<reviewed-version> - Record and verify the expected package integrity hash or install through a lockfile-backed, reproducible process.
- Review the pinned package, its transitive dependencies, and npm lifecycle scripts before approval.
- Prefer a project-local installation rather than a global installation, then invoke the pinned local binary.
- Disable npm lifecycle scripts with
--ignore-scriptswhen they are not required. If scripts are required, inspect them before installation. - Avoid elevated installation privileges and execute the CLI under a least-privileged account or sandbox.
- Establish a controlled upgrade process in which new versions are reviewed and their integrity is verified before changing the pin.
- Pin the dependency to a specifically reviewed release in both metadata and installation instructions, for example:
