T08 · Insecure Dependencies
- Location
README.md:5- Finding
Execution of an Unpinned npm Package During Installation
- Content
View full analysis
Vulnerability Details
File Location:
README.md, lines 5–9
Vulnerability Type: Supply-chain risk caused by unpinned package execution
Risk Level: MediumComplete Code Snippet:
markdown ## 安装 ```bash npx clawhub@latest install dream-trackertext ### Technical Analysis The documented installation command invokes `npx` with the mutable `latest` tag: ```bash npx clawhub@latest install dream-trackerDepending on the local npm configuration and cache state,
npxcan retrieve the currentclawhubpackage release from the configured npm registry and execute its command. Thelatesttag can be changed after this skill has been reviewed, so the code eventually executed by users is not cryptographically or immutably tied to the audited project version.The repository supplies no exact dependency version, lockfile, package integrity hash, signature verification procedure, or vendored installer implementation. Consequently, an npm account or package compromise, malicious release, registry substitution, or unexpected future package change could expose users to code that was not included in this audit.
This finding concerns the documented external installer rather than embedded malicious code in the reviewed project. No evidence establishes that the current
clawhubpackage is malicious.Attack Path
- An attacker compromises the npm package publisher, publishing credentials, registry, or another component capable of controlling the package associated with
clawhub@latest. - The attacker publishes a malicious package version and assigns the mutable
latestdistribution tag to it. - A user follows the installation command in
README.md. npxresolves and downloads the attacker-controlled release when it is not already available from a trusted local cache.- The downloaded package executes through the
clawhubcommand and can perform actions with the privileges of the user ...[truncated 725 chars]
- An attacker compromises the npm package publisher, publishing credentials, registry, or another component capable of controlling the package associated with
- Remediation
View remediation
Remediation Suggestions
-
Replace the mutable
latesttag with an exact, reviewed package version, for example:bash npx --yes clawhub@X.Y.Z install dream-tracker -
Publish and verify the expected package integrity hash or signature through a trusted channel.
-
Document the expected npm registry and require secure registry transport to reduce registry-substitution risk.
-
Prefer a lockfile-backed installation workflow where applicable, and review dependency changes before updating the pinned version.
-
In CI or other sensitive environments, execute the installer with a minimally privileged account, restricted credentials, and network or filesystem isolation.
-
Avoid instructing users to run the installation command as an administrator or root user.
-
Consider distributing a reviewed local installer or package artifact whose contents can be verified before execution.
-
