T08 · Insecure Dependencies
- Location
SKILL.md:14- Finding
Execution of an Unpinned npm Package During Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 14
Vulnerability Type: Supply-chain risk caused by mutable dependency execution
Risk Level: MediumComplete Code Snippet:
bash npx clawhub@latest install content-monetizationTechnical Analysis
The documented installation command uses
npxto download and execute the package referenced by the mutablelatesttag. Because no exact package version or integrity hash is specified, the code executed during installation can change after this Skill has been reviewed.An attacker who compromises the
clawhubpackage, its publisher account, or the relevant registry metadata could causelatestto resolve to a malicious release. Following the documented command would then download and execute that release, including applicable CLI and package lifecycle behavior, with the permissions of the invoking user.Attack Path
- An attacker compromises the npm package, its publisher credentials, or the package distribution process.
- The attacker publishes a malicious version and assigns or causes the
latesttag to point to it. - A user follows the installation instructions in
SKILL.md. npxresolvesclawhub@latest, downloads the attacker-controlled package version, and executes its CLI.- The malicious process performs actions available to the invoking account.
Impact Assessment
Successful exploitation could provide code execution with the privileges of the user running the installation command. Depending on that user's permissions and environment, the malicious package could read or modify accessible files, access environment variables and locally available credentials, tamper with the project or user configuration, and initiate network connections. The affected scope is the installation environment and resources accessible to the invoking account. The audited file does not itself demonstrate privilege escalation, persistence, or ...[truncated 28 chars]
- Remediation
View remediation
Remediation Suggestions
- Replace
@latestwith an exact, reviewed package version, for exampleclawhub@X.Y.Z. - Verify the selected release's provenance, publisher identity, and source repository before recommending it.
- Pin and validate the package artifact using an integrity digest or an equivalent trusted verification mechanism.
- Use a trusted registry explicitly and prevent unexpected registry substitution through controlled npm configuration.
- Review package lifecycle scripts and CLI entry points before execution.
- Run installation with least privilege in an isolated environment, without unnecessary credentials or sensitive environment variables.
- Establish a controlled update process in which newer versions are reviewed before the pinned version is changed.
- Replace
