T08 · Insecure Dependencies
- Location
SKILL.md:90- Finding
Unpinned Global npm Package Installation Creates Supply-Chain Risk
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 90-92
Vulnerability Type: Unpinned third-party dependency installed globally
Risk Level: MediumVulnerable Code Snippet:
bash npm install -g clawdhubTechnical Analysis
The Skill instructs users to install the latest available version of the
clawdhubnpm package globally without pinning a reviewed version or verifying package integrity. Consequently, the installed code can change after the Skill has been audited.npm packages may execute lifecycle scripts during installation. If the package, a transitive dependency, or its publishing account is compromised, attacker-controlled installation code could execute with the permissions of the user running the command. Global installation also modifies the user's shared tool environment instead of containing the dependency within the project.
Attack Path
- An attacker compromises the
clawdhubnpm package, one of its dependencies, or the corresponding publisher account. - The attacker publishes a malicious package version containing a lifecycle script or altered executable.
- A user follows the Skill instructions and runs
npm install -g clawdhub. - npm retrieves the current compromised version because no version or integrity constraint is specified.
- Malicious installation code executes under the user's account and installs or replaces the global CLI.
- Subsequent use of the compromised CLI may expose publication credentials, alter uploaded content, or execute additional commands.
Impact Assessment
Successful exploitation can provide arbitrary code execution with the privileges of the user performing the installation. The attacker could access files and credentials available to that user, modify globally installed user-level tools, steal ClawdHub authentication material, or tamper with published Skills. Administrative privileges are not inherently obtained, but the impact in ...[truncated 53 chars]
- An attacker compromises the
- Remediation
View remediation
Remediation Suggestions
- Pin the CLI to a specifically reviewed version, for example
clawdhub@<reviewed-version>. - Document the authoritative npm package scope, publisher, and source repository so users can detect similarly named packages.
- Verify package provenance and integrity before installation, including npm signatures or registry provenance where supported.
- Prefer a project-local or isolated installation over a global installation.
- Where compatible with the package, disable lifecycle scripts during installation and invoke only reviewed artifacts.
- Establish a controlled upgrade process that reviews new package versions and their dependency changes before updating the documented command.
- Pin the CLI to a specifically reviewed version, for example
