T08 · Insecure Dependencies
- Location
SKILL.md:15- Finding
Unpinned npm CLI Execution Creates a Supply-Chain Risk
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:15andSKILL.md:21
Vulnerability Type:T08: Insecure Dependencies
Risk Level: MediumVulnerable Code
yaml openclaw: requires: tools: [filesystem] install: "npx clawhub install mushroom-cultivation-basics"The same command is repeated in the document body:
text npx clawhub install mushroom-cultivation-basicsTechnical Analysis
The installation instructions invoke
clawhubthroughnpxwithout specifying an exact package version, integrity hash, lockfile, or immutable source. If the CLI is not already available locally,npxmay retrieve the current package release from the configured npm registry and execute it with the installing user's privileges.Because the retrieved version can change after this Skill has been audited, the effective installation code is not bounded by the reviewed project contents. Compromise of the package publisher account, registry entry, or transitive dependency could therefore turn the documented installation command into an arbitrary-code execution channel.
No evidence shows that the current
clawhubpackage is malicious. The finding concerns the mutable and unverified dependency execution mechanism.Attack Path
- An attacker compromises the
clawhubnpm package, its publisher account, or one of its executable dependencies. - The attacker publishes a malicious release under the package name resolved by
npx. - A user follows the command in
SKILL.md. npxresolves and downloads the mutable package release from the configured registry.- Package lifecycle logic or CLI entry-point code executes on the user's machine.
- The malicious code operates with the permissions and environmental access of the user running the command.
Impact Assessment
Successful exploitation could execute arbitrary commands with the installing user's privileges. Depending on the e ...[truncated 481 chars]
- An attacker compromises the
- Remediation
View remediation
Remediation Suggestions
- Pin the CLI to an exact reviewed version, for example:
text npx --yes clawhub@X.Y.Z install mushroom-cultivation-basics - Verify the selected release and its transitive dependencies before documenting it as trusted.
- Use a lockfile and npm integrity metadata where the installation workflow supports them.
- Explicitly identify the expected registry and prevent fallback to untrusted package sources.
- Prefer a trusted, preinstalled CLI or a locally vendored and reviewed installer over runtime retrieval.
- Run installation under a least-privileged account without unnecessary secrets in environment variables.
- Apply the hardened command consistently at both
SKILL.md:15andSKILL.md:21.
- Pin the CLI to an exact reviewed version, for example:
