T08 · Insecure Dependencies
Warning
- Location
- SKILL.md:16
- Finding
- Unpinned Package Execution Through ClawHub Installation Command<![CDATA[ ## Vulnerability Details **File Location**: `SKILL.md:16-18` **Vulnerability Type**: Unpinned third-party package execution **Risk Level**: Medium ### Vulnerable Code ```bash npx clawhub@latest install realtime-react-hooks ``` ### Technical Analysis The installation instructions use `npx` to download and execute the mutable `latest` release of the third-party `clawhub` package. No exact version, package integrity hash, lockfile, or other reproducibility control is specified. Because the `latest` distribution tag can be reassigned to a different release after this audit, the code eventually executed by users is not necessarily the code that was reviewed. This creates a supply-chain trust boundary in which compromise of the package publisher, npm account, registry, release process, or transitive dependency could introduce arbitrary executable behavior. The command is not evidence that the current package is malicious; the vulnerability is that it automatically executes a mutable external dependency without integrity verification. ### Attack Path 1. An attacker compromises the npm publisher account, package release process, registry entry, or a dependency used by a future `clawhub` release. 2. The attacker publishes malicious code and assigns the `latest` distribution tag to the compromised release. 3. A user follows the documented installation command. 4. `npx` downloads and executes the release currently referenced by `clawhub@latest`. 5. The malicious package executes with the operating-system privileges and environment access of the invoking user. ### Impact Assessment Successful exploitation could permit arbitrary local code execution under the invoking user's account. Depending on that account's permissions and environment, the payload could read or modify accessible source code and configuration files, access environment variables and developer credentials, alter installed skills or tools, and make ...[truncated 202 chars]
- Remediation
- <![CDATA[ ## Remediation Suggestions - Replace `@latest` with an exact, reviewed package version, such as `clawhub@X.Y.Z`. - Verify the package publisher and document the expected package source. - Use lockfiles and npm integrity metadata where installation tooling supports them. - Review the pinned package and its transitive dependencies before recommending execution. - Establish a controlled update process in which new versions are reviewed before the documented pin is changed. - Consider instructing users to download and inspect the package before execution in security-sensitive environments. ]]>