T08 · Insecure Dependencies
- Location
SKILL.md:13- Finding
Unpinned Package Execution Through npx
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 13 and 22
Vulnerability Type: Unpinned third-party package execution
Risk Level: MediumVulnerable Code
Line 13:
yaml install: "npx clawhub install birch-bark-container-making-basics"Line 22:
shell npx clawhub install birch-bark-container-making-basicsTechnical Analysis
The documented installation command invokes the unversioned
clawhubnpm package throughnpx. If that package is not already available locally,npxmay retrieve and execute the version currently resolved by the configured npm registry.The project does not pin an exact
clawhubversion or provide a lockfile, package integrity hash, signature-verification procedure, or trusted-registry constraint. Consequently, the executable dependency may change after this Skill has been reviewed. This creates a supply-chain risk if the package, publisher account, registry resolution path, or a future package release is compromised.Attack Path
- An attacker compromises the
clawhubpackage, its publisher account, or the package-resolution infrastructure, or causes an unsafe release to become the version selected bynpx. - A user follows either installation instruction in
SKILL.md. npxresolves and downloads the unpinned package from the configured registry.- npm lifecycle behavior or the package executable runs attacker-controlled code.
- The payload executes under the account and environment of the user who invoked the command.
Impact Assessment
Successful exploitation could permit arbitrary code execution with the invoking user's privileges. Depending on that user's permissions and environment, the payload could read or modify accessible files, access environment variables and credentials, make network requests, install additional software, or alter local development state.
The reviewed repository contains no evidence of privilege escalation or persistence itself. Any practi ...[truncated 143 chars]
- An attacker compromises the
- Remediation
View remediation
Remediation Suggestions
-
Pin
clawhubto an exact, reviewed version rather than allowing dynamic resolution, for example:shell npx --yes clawhub@<reviewed-exact-version> install birch-bark-container-making-basics -
Validate that exact release before recommending it, including its package contents, lifecycle scripts, executable entry point, and transitive dependencies.
-
Use a trusted registry explicitly and enforce approved registry configuration in managed environments.
-
Verify package provenance, signatures, or published integrity metadata before execution.
-
Prefer a lockfile-backed installation workflow with integrity-protected dependency resolution where possible.
-
Avoid executing newly downloaded packages directly. Install reviewed artifacts in a restricted environment first, then invoke the verified executable.
-
Run the installer with least privilege and without unnecessary secrets, credentials, filesystem permissions, or network access.
-
Keep the version and integrity information in
SKILL.mdsynchronized with each security review.
-
