T08 · Insecure Dependencies
- Location
SKILL.md:15- Finding
Unpinned CLI Package Download and Execution via npx
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 15 and 21
Vulnerability Type: Unpinned third-party dependency execution
Risk Level: MediumComplete Code Snippet:
yaml install: "npx clawhub install cattail-mat-weaving-basics"shell npx clawhub install cattail-mat-weaving-basicsTechnical Analysis
The documented installation command invokes
clawhubthroughnpxwithout specifying a reviewed package version or integrity constraint. If the package is not already available locally,npxcan retrieve the current package release from the configured package registry and execute its CLI code.Because the package version is mutable from the perspective of this audited Skill, the code executed during installation may differ from the code present when the Skill was reviewed. A compromised maintainer account, malicious package release, package takeover, or compromised registry could therefore turn the installation instruction into a supply-chain execution channel.
The project contains no embedded executable scripts, and the audit found no evidence that the Skill author currently controls or intends a malicious package payload. The risk arises from executing an unpinned external dependency.
Attack Path
- An attacker compromises the
clawhubpackage, its publisher account, or the registry delivery path. - The attacker publishes a malicious release under the expected package name.
- A user follows the installation command in
SKILL.md. npxresolves and downloads the mutable package release from the configured registry.- The downloaded CLI or associated package lifecycle behavior executes with the privileges of the user running the command.
- The malicious package can access data and perform operations permitted to that user.
Impact Assessment
Successful exploitation could provide arbitrary code execution under the installing user's account. The resulting ...[truncated 484 chars]
- An attacker compromises the
- Remediation
View remediation
Remediation Suggestions
- Pin the CLI to a specific reviewed version, for example
npx clawhub@<reviewed-version> install cattail-mat-weaving-basics. - Use an exact version rather than a range or floating distribution tag such as
latest. - Verify the package through a trusted registry and validate package provenance, signatures, or published integrity metadata before execution.
- Prefer installing the audited CLI through a lockfile-backed or organization-approved dependency process, then invoke the verified local binary.
- Disable or ignore dependency lifecycle scripts where operationally possible.
- Run installation with a low-privilege account in a sandbox or container that exposes no unrelated credentials or sensitive files.
- Document the expected package publisher, registry, version, and checksum so users can detect substitution or registry misconfiguration.
- Re-audit the pinned package before intentionally upgrading it.
- Pin the CLI to a specific reviewed version, for example
