T08 · Insecure Dependencies
- Location
SKILL.md:16- Finding
Unpinned npm Package Execution Through npx
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 16
Vulnerability Type: Unpinned third-party package execution
Risk Level: MediumVulnerable Code
yaml install: "npx clawhub install raising-livestock"Technical Analysis
The installation metadata instructs users to invoke the
clawhubnpm package throughnpxwithout specifying an exact package version or integrity digest. If the package is not available locally,npxmay retrieve and execute it from the configured npm registry.Consequently, the code executed during installation is not fixed to the version reviewed alongside this Skill. A compromised package release, maintainer account, registry resolution path, or malicious dependency introduced into a later release could cause arbitrary code to run when a user follows the installation instruction. The project contains no lockfile, vendored installer, checksum, or provenance information that would allow the resolved package to be verified against a reviewed artifact.
This is a supply-chain exposure rather than evidence that the current
clawhubpackage is malicious.Attack Path
- An attacker compromises the npm package, a package maintainer account, or a transitive dependency used by a subsequently published
clawhubrelease. - The attacker publishes a release containing malicious package code or an installation lifecycle script.
- A user follows the Skill metadata and runs
npx clawhub install raising-livestock. - Because no exact version or integrity value is specified,
npxresolves the package version available through the user's configured registry. - The malicious package or lifecycle code executes under the privileges of the user running the command.
- The code may access resources available to that account, including project files, user files, environment variables, developer credentials, and network services.
Impact Assessment
Successful exploitati ...[truncated 582 chars]
- An attacker compromises the npm package, a package maintainer account, or a transitive dependency used by a subsequently published
- Remediation
View remediation
Remediation Suggestions
- Pin
clawhubto an exact reviewed version rather than relying on unconstrained registry resolution:yaml install: "npx clawhub@<reviewed-exact-version> install raising-livestock" - Record and verify package integrity or trusted provenance before execution, such as through registry integrity metadata, signed releases, or an approved internal artifact repository.
- Disable or tightly control npm lifecycle scripts where operationally possible.
- Document the expected package publisher, registry, exact version, and verification procedure so users can detect typosquatting or registry substitution.
- Provide a non-executing or manually verifiable installation method as an alternative.
- Re-audit the pinned installer and its transitive dependencies whenever the pinned version is updated.
- Advise users not to execute the installer with administrator or root privileges.
- Pin
