T08 · Insecure Dependencies
- Location
SKILL.md:15- Finding
Unpinned npm Package Execution Through npx
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 15 and 24
Vulnerability Type:T08: Insecure Dependencies
Risk Level: MediumVulnerable Code
Line 15:
yaml install: "npx clawhub install traditional-bone-tool-making-basics"Line 24:
shell npx clawhub install traditional-bone-tool-making-basicsTechnical Analysis
The installation instructions execute the
clawhubnpm package throughnpxwithout specifying a reviewed version or integrity value. If the package is not already available locally,npxmay retrieve and execute the version currently resolved from the configured npm registry.Because the package version is unpinned, the code executed during installation can change after this Skill has been reviewed. The effective installation behavior therefore depends on mutable third-party registry content rather than solely on the audited project.
This creates a software supply-chain risk. A compromised package publisher account, malicious package release, registry compromise, or unexpected dependency update could introduce arbitrary code into the installation process.
Attack Path
- An attacker compromises the publisher account, release process, or registry entry associated with the
clawhubnpm package. - The attacker publishes a modified package version containing malicious installation or runtime behavior.
- A user follows the installation command documented in
SKILL.md. npxresolves and downloads the attacker-controlled or compromised package version.- The package executes under the identity and permissions of the user running the command.
- The malicious package can access resources available to that user, subject to operating-system controls and the execution environment.
Impact Assessment
Successful exploitation could result in arbitrary code execution with the privileges of the invoking user. Depending on those privileges and the ...[truncated 450 chars]
- An attacker compromises the publisher account, release process, or registry entry associated with the
- Remediation
View remediation
Remediation Suggestions
- Pin
clawhubto a specifically reviewed version instead of allowingnpxto resolve the latest release:shell npx clawhub@<reviewed-version> install traditional-bone-tool-making-basics - Verify the selected package version's provenance, publisher identity, release signatures, and npm integrity metadata before documenting it.
- Use an approved registry or internal package mirror that permits only vetted package versions.
- Prefer a lockfile-backed, reproducible installation workflow where practical.
- Run installation with least privilege in an isolated environment without unnecessary credentials or access to sensitive files.
- Periodically review the pinned package and its transitive dependencies before updating the documented version.
- Pin
