T08 · Insecure Dependencies
- Location
SKILL.md:19- Finding
Unpinned npm Package Is Retrieved and Executed During Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 19–25
Vulnerability Type: Unpinned third-party package execution
Risk Level: MediumVulnerable Code
markdown install: "npx clawhub install welding-basics" --- # Welding Basics Master entry-level arc and MIG welding so you can permanently repair farm equipment, vehicles, gates, tools, and custom fabrications without waiting for shops or supply chains. This is not theory — it is a complete, agent-executed training and project protocol that gets you welding safely and productively within 14 days. `npx clawhub install welding-basics`Technical Analysis
The installation command invokes
clawhubthroughnpxwithout specifying an exact package version or integrity constraint. If the package is not already available in a trusted local installation,npxmay resolve and download the currently published package from the configured npm registry before executing its CLI code.Consequently, the code executed by this documented command is not immutable and cannot be verified from the reviewed project. A compromised npm publisher account, malicious replacement release, registry compromise, dependency confusion condition, or compromised transitive dependency could cause a future invocation to execute code different from the version originally reviewed.
No malicious implementation is included in the audited project itself; exploitation depends on compromise or malicious publication within the external package supply chain.
Attack Path
- An attacker compromises the publisher, package, registry resolution path, or a dependency used by the
clawhubnpm package. - The attacker publishes a malicious version that becomes the version selected by the unpinned
npx clawhubcommand. - A user follows the installation instruction in
SKILL.md. npxretrieves the attacker-controlled package version from the configured registry.- The ...[truncated 761 chars]
- An attacker compromises the publisher, package, registry resolution path, or a dependency used by the
- Remediation
View remediation
Remediation Suggestions
- Pin the installer to a specific reviewed version, for example:
shell npx --yes clawhub@<reviewed-version> install welding-basics - Verify the selected package version, official publisher identity, provenance, and published integrity metadata before documenting it.
- Use a lockfile and npm integrity hashes where the installation workflow supports them.
- Prefer installing from a trusted, reviewed artifact or an organization-controlled registry rather than dynamically resolving the latest public package.
- Disable or tightly control lifecycle scripts when feasible and review the package's transitive dependency tree.
- Run installation with a non-privileged account in a restricted environment, exposing only the files and credentials required for installation.
- Establish a controlled update process in which newer package versions are reviewed and tested before the pinned version is changed.
- Pin the installer to a specific reviewed version, for example: