T08 · Insecure Dependencies
- Location
README.md:18- Finding
Unpinned Package Execution Through npx
- Content
View full analysis
Vulnerability Details
File Location:
README.md:18-20
Vulnerability Type: Unpinned third-party package execution
Risk Level: MediumVulnerable Code Snippet:
bash # Install through ClawHub npx clawhub install skill-usage-analyzerTechnical Analysis
The documented installation command invokes
clawhubthroughnpxwithout specifying a package version, integrity hash, or verified source. If the package is not already available locally,npxmay retrieve the current package release from the configured npm registry and execute it.Consequently, the code executed during installation is not restricted to the version reviewed during this audit. A compromised publisher account, registry package, or malicious future release could alter installation behavior and execute attacker-controlled code.
Attack Path
- An attacker compromises the npm publisher account, package distribution channel, or registry entry associated with
clawhub. - The attacker publishes a malicious release under the expected package name.
- A user follows the installation command in
README.md. npxretrieves the current unpinned release from the configured registry.- Package lifecycle or CLI code executes with the privileges of the user running the command.
- The malicious package can access or modify resources available to that user.
Impact Assessment
Successful exploitation could result in arbitrary code execution with the installing user's privileges. The affected scope may include the user's files, OpenClaw workspace, environment variables, accessible credentials, and other resources available to the current account. The reviewed project itself contains no confirmed malicious package or payload; exploitation depends on compromise or substitution of the external package supply chain.
- An attacker compromises the npm publisher account, package distribution channel, or registry entry associated with
- Remediation
View remediation
Remediation Suggestions
- Pin the CLI to a specifically reviewed version, for example
npx clawhub@<verified-version> install skill-usage-analyzer. - Document the expected npm registry, package publisher, and verified package identity.
- Verify package provenance, signatures, and integrity metadata before execution.
- Prefer a lockfile-backed installation process or an already installed, trusted CLI instead of downloading executable code on demand.
- Provide a verified-source installation alternative using a fixed commit or immutable release artifact with a published checksum.
- Review pinned updates before changing the recommended version.
- Pin the CLI to a specifically reviewed version, for example