T08 · Insecure Dependencies
- Location
SKILL.md:24- Finding
Unpinned Global Installation of a Third-Party CLI Package
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 24–27
Vulnerability Type: Unpinned third-party dependency installed globally
Risk Level: MediumVulnerable Code:
bash 1. **ClawHub CLI installed:** ```bash npm install -g clawhub ```Technical Analysis
The workflow directs users to install the latest available version of the
clawhubnpm package globally. It does not pin a reviewed version, verify package integrity, identify an expected publisher, or otherwise constrain the retrieved artifact.npm installations may execute package lifecycle scripts with the permissions of the invoking user. Because
-ginstalls the package globally, a malicious or compromised package release could affect the user's broader development environment rather than an isolated project directory. The effective package contents may also change after this Skill has been reviewed.This finding does not establish that the current
clawhubpackage is malicious. The risk arises from trusting an unpinned, mutable third-party dependency and installing it globally.Attack Path
- An attacker compromises the npm package, its maintainer account, or a future release in its supply chain.
- The attacker publishes a release containing malicious package code or lifecycle scripts.
- A user follows the Skill and runs
npm install -g clawhubwithout a version constraint. - npm downloads the attacker-controlled latest version.
- Malicious lifecycle code executes with the invoking user's permissions, or the globally installed CLI performs malicious actions when subsequently invoked.
Impact Assessment
Exploitation could execute arbitrary code with the permissions of the user running npm. Depending on those permissions and the host configuration, the malicious package could access user-readable files and credentials, alter development tools, intercept future CLI inputs, or modify globally installed ...[truncated 166 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin the CLI to a specifically reviewed version, for example
clawhub@1.2.3. - Record and verify the expected package publisher, registry, and integrity metadata.
- Prefer a project-local dependency with a lockfile over a global installation.
- Disable lifecycle scripts during installation when they are not required, then review any required scripts separately.
- Document a trusted release-verification process and update the pinned version only after review.
- Warn users not to run the installation with
sudoor unnecessary administrative privileges.
- Pin the CLI to a specifically reviewed version, for example
