T08 · Insecure Dependencies
- Location
README.md:6- Finding
Unpinned Remote npm Package Execution
- Content
View full analysis
Vulnerability Details
File Location:
README.md, line 6
Vulnerability Type: Mutable third-party dependency execution
Risk Level: MediumVulnerable Code:
bash npx clawhub@latest install blood-pressure-trackerTechnical Analysis
The documented installation command invokes
npxwith the mutablelatesttag. This causes npm to retrieve and execute a remotely published version of the third-partyclawhubpackage whose source is not included in the audited project.Because neither an exact package version nor an integrity hash is specified, the command's effective behavior can change after this project has been reviewed. The risk materializes if the package publisher, npm account, package distribution process, or registry is compromised, or if a future release introduces unsafe behavior.
The repository itself does not contain evidence that the current
clawhubpackage is malicious. The vulnerability is the unsafe dependency acquisition and execution pattern documented for users.Attack Path
- An attacker compromises the npm publisher account, package supply chain, or distribution infrastructure for
clawhub. - The attacker publishes a malicious release and assigns it the
latesttag. - A user follows the installation command in
README.md. npxdownloads the attacker-controlled package from the configured npm registry.- npm lifecycle behavior or the invoked CLI executes code with the privileges of the user running the command.
- The payload can access resources available to that user, subject to operating-system controls and the runtime environment.
Impact Assessment
Successful exploitation could provide arbitrary code execution under the installing user's account. Potential scope includes reading or modifying user-accessible files, accessing environment variables and locally available credentials, making network requests, and installing additional user-level comp ...[truncated 209 chars]
- An attacker compromises the npm publisher account, package supply chain, or distribution infrastructure for
- Remediation
View remediation
Remediation Suggestions
- Replace the mutable
latesttag with a reviewed, exact package version:bash npx clawhub@X.Y.Z install blood-pressure-tracker - Verify the selected package release and its transitive dependencies before recommending execution.
- Use lockfiles and npm integrity metadata where the installation workflow permits them.
- Document the expected registry and advise users not to install from untrusted registry overrides.
- Prefer installing a pinned dependency through a controlled project manifest and then invoking its local binary.
- Avoid recommending elevated privileges for installation.
- Establish a release-update process in which the documented version is changed only after the new package release has been reviewed.
- Replace the mutable
