T08 · Insecure Dependencies
Warning
- Location
- README.md:40
- Finding
- Unpinned Third-Party Package Is Downloaded and Executed During Installation## Vulnerability Details **File Location**: `README.md:40` **Vulnerability Type**: Supply-chain risk caused by executing a mutable package release **Risk Level**: Medium ### Vulnerable Code ```bash npx --yes clawhub@latest install @orionshaowswmw/heart-of-light ``` ### Technical Analysis The documented installation command instructs `npx` to retrieve and execute the `latest` release of the third-party `clawhub` package. The `latest` tag is mutable, so the code executed by a future user may differ from the version that was available when this Skill was audited. The `--yes` option suppresses the normal installation confirmation. Consequently, following the documented command can download and execute unaudited code without an opportunity to review the resolved package version. Although this command is documentation rather than an automatic runtime action, it establishes an unsafe installation path. The reviewed Skill implementation itself does not contain runtime network access, dependency loading, or remote payload execution. The risk is confined to users who follow this installation instruction. ### Attack Path 1. An attacker compromises the npm package, its publisher account, release process, or an upstream dependency used by a future `clawhub` release. 2. The compromised release is assigned the mutable `latest` distribution tag. 3. A user follows the installation command in `README.md`. 4. `npx --yes` downloads the currently resolved release and executes its package entrypoint without interactive confirmation. 5. The malicious package runs with the operating-system permissions of the user who invoked the command. 6. It could access or modify any files, credentials, processes, or network resources available to that user, independently of the narrow permissions declared by this Skill. ### Impact Assessment Successful exploitation permits arbitrary code execution with the installer user's privileges. The practical ...[truncated 409 chars]
- Remediation
- ## Remediation Suggestions 1. Replace the mutable `@latest` reference with an exact, reviewed version: ```bash npx clawhub@<audited-exact-version> install @orionshaowswmw/heart-of-light ``` 2. Remove `--yes` where practical so users can inspect and approve the resolved package before execution. 3. Publish expected package provenance and integrity information, such as the registry source, exact version, and cryptographic digest. 4. Recommend inspecting the package metadata and resolved dependency tree before execution. 5. For sensitive environments, document a download-and-verify workflow that separates package retrieval from execution. 6. Avoid running the installer with administrator privileges and use a restricted environment with only the filesystem and network access required for installation.
