T08 · Insecure Dependencies
- Location
README.md:5- Finding
Mutable Third-Party Package Executed Through npx
- Content
View full analysis
Vulnerability Details
File Location:
README.md, lines 5-7
Vulnerability Type: Unpinned third-party dependency execution
Risk Level: HighVulnerable Code:
bash npx clawhub@latest install video-processorTechnical Analysis
The documented installation command instructs users to execute the mutable
latestrelease of the third-partyclawhubpackage throughnpx. Because neither an exact version nor an integrity hash is specified, the code executed by this command can change after this project has been reviewed.Depending on the local npm configuration,
npxcan download the selected package and execute its CLI code. Package lifecycle scripts or the invoked installer may consequently run arbitrary commands. The repository does not contain the installer implementation, a lockfile, an integrity record, or other controls that would allow the retrieved package to be verified against an audited release.Attack Path
- An attacker compromises the upstream
clawhubpackage, its publisher account, or the package distribution channel. - The attacker publishes a malicious release selected by the
latesttag. - A user follows the installation instructions and runs
npx clawhub@latest install video-processor. npxretrieves the attacker-controlled release and invokes its executable code.- The malicious package executes commands under the privileges of the user running the installation.
This exploitation path depends on compromise or malicious modification of the external dependency; the audited repository itself does not contain a remote payload.
Impact Assessment
Successful exploitation could provide arbitrary code execution with the permissions of the installing user. Potential impact includes reading or modifying files accessible to that account, accessing environment variables and developer credentials, altering local project data, initiating network connections, and insta ...[truncated 160 chars]
- An attacker compromises the upstream
- Remediation
View remediation
Remediation Suggestions
- Replace the mutable
@latestreference with an exact, reviewed package version. - Verify the selected release and document the expected package integrity hash.
- Use a lockfile or another reproducible dependency mechanism where supported.
- Configure and document the trusted package registry rather than relying on implicit npm configuration.
- Review the package contents, executable entry point, and lifecycle scripts before recommending execution.
- Prefer installing the verified package first and invoking it separately instead of allowing
npxto download and execute an unresolved release automatically. - Update dependencies through a controlled review process rather than following a moving distribution tag.
- Advise users not to run the installation command with administrative or root privileges.
- Replace the mutable
