T08 · Insecure Dependencies
- Location
README.md:65- Finding
Unpinned Third-Party Package Execution During Installation
- Content
View full analysis
Vulnerability Details
File Location:
README.md, lines 65–69
Vulnerability Type: Mutable third-party dependency execution
Risk Level: MediumVulnerable Code
markdown This is an [OpenClaw](https://openclaw.ai) skill. Install it via ClawHub CLI: ```bash npx clawhub@latest install global-perspectives-newstext ### Technical Analysis The documented installation procedure directs users to execute the `clawhub` npm package through `npx` using the mutable `latest` distribution tag. `npx` can download and execute package code immediately, while `@latest` does not identify a fixed, previously reviewed release. As a result, the package code executed during installation may differ from the code that existed when this skill was audited. The command provides no exact version pin, lockfile, integrity hash, or explicit artifact-verification step. This creates a supply-chain trust dependency on the npm registry, the package publisher account, and every future package version assigned to the `latest` tag. The issue does not establish that the current `clawhub` package is malicious. It establishes that the documented command can execute a subsequently compromised or malicious release without giving users reproducible dependency selection. ### Attack Path 1. An attacker compromises the `clawhub` publisher account, package release process, or another component of its software supply chain. 2. The attacker publishes a malicious package version and causes the npm `latest` tag to resolve to it. 3. A user follows the installation instructions and runs: ```bash npx clawhub@latest install global-perspectives-newsnpxretrieves the attacker-controlled package selected at that time.- The downloaded package executes with the privileges and environment of the invoking user.
- The malicious package can perform actions allowed by that user before or during installation, independently of the audited Markdown skill content.
Impact Ass
...[truncated 604 chars]
- Remediation
View remediation
Remediation Suggestions
- Replace
@latestwith an exact, reviewed package version:bash npx clawhub@X.Y.Z install global-perspectives-news - Document the expected npm package name, publisher identity, and approved version so users can detect typosquatting or publisher changes.
- Provide package integrity information and instruct users to verify the downloaded artifact where supported.
- Use a lockfile or another reproducible dependency mechanism for automated installation workflows.
- Prefer an installation method that downloads a versioned artifact for inspection and verification before executing any installer code.
- Establish a controlled update process in which new CLI versions are reviewed before the documented version is changed.
- Warn users not to execute the installation command with elevated privileges unless explicitly required and justified.
- Replace
