T08 · Insecure Dependencies
Warning
- Location
- SKILL.md:22
- Finding
- Mutable Package Version Executed Through npx## Vulnerability Details **File Locations**: - `SKILL.md:22-25` - `README.md:29-32` **Vulnerability Type**: Unpinned third-party package execution **Risk Level**: Medium ### Vulnerable Code `SKILL.md:22-25`: ```bash ### OpenClaw / Moltbot / Clawbot ```bash npx clawhub@latest install frontend-design ``` ``` `README.md:29-32`: ```bash ### OpenClaw / Moltbot / Clawbot ```bash npx clawhub@latest install frontend-design ``` ``` ### Technical Analysis The installation instructions direct users to execute `clawhub@latest` through `npx`. The `latest` distribution tag is mutable and does not identify a fixed, previously reviewed package version. Depending on the local npm configuration and cache state, `npx` can download the selected package from the configured registry and execute its command, including applicable package installation behavior. The effective code executed by this command is not present in the audited project. Consequently, it can change after this Skill has been reviewed without requiring any modification to `SKILL.md` or `README.md`. Although no malicious package content was found in the audited files, this creates a supply-chain trust boundary and exposes users to a compromised package release, registry account, maintainer account, or package ownership transfer. ### Attack Path 1. An attacker compromises the `clawhub` package, its publisher account, or its upstream release process. 2. The attacker publishes a malicious version and assigns or causes the `latest` tag to reference it. 3. A user follows the documented installation command. 4. `npx` resolves `clawhub@latest` to the attacker-controlled version and downloads it. 5. The package executes with the privileges of the user running the command. 6. The payload can access data and resources available to that user. ### Impact Assessment Successful exploitation could permit arbitrary code execution under the installing user's ...[truncated 574 chars]
- Remediation
- ## Remediation Suggestions - Replace `@latest` with a reviewed, exact package version, such as `clawhub@X.Y.Z`. - Verify package provenance, signatures, and integrity metadata before execution. - Document the expected package checksum or signed release identity through a trusted channel. - Review package contents and lifecycle scripts before promoting a new pinned version. - Run installation with a non-privileged account in an isolated environment. - In CI, restrict network access and secrets available to installation steps. - Keep the pinned version synchronized in both `SKILL.md` and `README.md`.