T08 · Insecure Dependencies
- Location
SKILL.md:26- Finding
Mutable npm Package Is Downloaded and Executed During Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 26
Vulnerability Type:T08: Insecure Dependencies
Risk Level: Mediumbash npx clawhub@latest install agentcyTechnical Analysis
The documented installation command directs
npxto resolve and execute the package currently referenced by the mutablelatestdistribution tag. The command does not pin a reviewed package version or require verification against a trusted integrity hash or lockfile.Consequently, the code executed during installation can differ from the code that was available when this skill was audited. If the npm publisher account, package, registry delivery chain, or a relevant dependency is compromised, an attacker could supply malicious installer code through a new release associated with
latest.This is a supply-chain weakness in the documented installation path. The reviewed local shell scripts do not themselves retrieve or execute code.
Attack Path
- An attacker compromises the
clawhubnpm publisher account, package publication process, registry delivery chain, or a dependency incorporated into a new release. - The attacker publishes a malicious package version and causes the mutable
latesttag to resolve to it. - A user follows the installation command in
SKILL.md. npxdownloads and executes the attacker-controlled package in the user's environment.- The malicious installer performs actions with the permissions and environmental access of the user running the command.
Impact Assessment
Successful exploitation could provide arbitrary code execution with the privileges of the installing user. Depending on that user's permissions and environment, the malicious package could read accessible files and environment variables, alter project or user-level files, install additional payloads, or access credentials available to the installation process.
The precise scope is limited by the permissions, sandboxing, and secrets available ...[truncated 160 chars]
- An attacker compromises the
- Remediation
View remediation
Remediation Suggestions
- Replace
@latestwith an exact, reviewed package version. - Use a lockfile or another reproducible installation mechanism that records dependency versions and package integrity metadata.
- Verify the package against a trusted registry integrity hash or independently published checksum before execution.
- Review the selected package version and its dependency tree before recommending it.
- Use npm provenance and signature verification where supported, and document the expected publisher identity.
- Install and execute the package in a least-privileged, isolated environment without unrelated credentials.
- Establish a controlled update process in which newer versions are reviewed before the pinned version is changed.
- Replace
