T08 · Insecure Dependencies
- Location
README.md:7- Finding
Unpinned npm Package Download and Execution
- Content
View full analysis
Vulnerability Details
File Location:
README.md, lines 7-9
Vulnerability Type: Unsafe execution of a mutable third-party dependency
Risk Level: MediumVulnerable Code:
bash npx clawhub@latest install batch-search-monitorTechnical Analysis
The documented installation procedure uses
npxwith the mutablelatesttag. When followed, this command may download and immediately execute whichever version of theclawhubnpm package is currently associated with that tag.The command does not pin a reviewed package version or verify the downloaded package using an integrity hash. The audited artifact also does not contain the external CLI implementation, so its effective installation behavior cannot be verified from the project files. A future package release, compromised maintainer account, or compromised publication process could therefore change the code executed by this command after the Skill has been reviewed.
Attack Path
- An attacker compromises the npm package maintainer, publication credentials, package namespace, or another part of the package distribution process.
- The attacker publishes a malicious release of
clawhuband assigns it to thelatestdistribution tag. - A user follows the installation instructions in
README.md. npxretrieves the attacker-controlled release from the configured npm registry.- The downloaded package executes as the user running the installation command.
- The malicious release can perform actions allowed by that user's operating-system permissions.
Impact Assessment
Successful exploitation could provide arbitrary code execution with the privileges of the user running
npx. Depending on those privileges and the host configuration, the malicious package could read or modify user-accessible files, access environment variables and credentials, make network requests, install additional software, or alter the user's development envir ...[truncated 299 chars]- Remediation
View remediation
Remediation Suggestions
- Replace the mutable
@latestreference with an exact, reviewed package version, such asclawhub@X.Y.Z. - Verify the selected package version and its transitive dependencies before recommending it.
- Use lockfiles and registry-provided integrity metadata where supported.
- Document the expected npm registry and trusted package provenance to reduce dependency-confusion risk.
- Prefer a controlled installation process that downloads and verifies an artifact before execution rather than combining retrieval and execution in one command.
- Establish an update process in which new package versions are security-reviewed before the documented version is changed.
- Advise users not to run the installation command with administrator or root privileges.
- Replace the mutable
