T08 · Insecure Dependencies
Warning
- Location
- SKILL.md:10
- Finding
- Execution of an Unpinned Package During Installation## Vulnerability Details **File Location**: `SKILL.md`, lines 10–14 **Vulnerability Type**: Supply-chain risk from an unpinned executable dependency **Risk Level**: Medium **Vulnerable Code:** ```bash ## Installation ```bash npx clawhub@latest install openclaw-free-search ``` ``` ### Technical Analysis The documented installation procedure directs users to execute the mutable `latest` release of the `clawhub` npm package through `npx`. The package version is not pinned, and the documentation provides no integrity digest or other mechanism for verifying the downloaded artifact. `npx` can download and execute package code. Consequently, the code executed by this command may differ from the version that existed when the skill was audited. If the package, registry entry, or publisher account is compromised, a malicious release published under the `latest` tag could run during installation. The audit found no evidence that the current package is malicious. The vulnerability is the unsafe, mutable trust relationship created by the installation command. ### Attack Path 1. An attacker compromises the `clawhub` package, its publisher account, or the relevant package-distribution channel. 2. The attacker publishes a malicious release and assigns it to the `latest` distribution tag. 3. A user follows the installation instructions and runs `npx clawhub@latest install openclaw-free-search`. 4. `npx` downloads and executes the attacker-controlled package release. 5. The malicious package executes with the permissions of the user running the installation command. ### Impact Assessment Successful exploitation provides arbitrary code execution under the installing user's account. Depending on that account's permissions and environment, an attacker could read or modify user-accessible files, obtain accessible credentials or tokens, tamper with installed skills and configuration, or establish user-level persistence. This comman ...[truncated 147 chars]
- Remediation
- ## Remediation Suggestions - Replace the mutable `@latest` reference with an exact, reviewed package version. - Verify the package against a trusted integrity hash or signed provenance before execution. - Use a lockfile or another reproducible dependency mechanism where applicable. - Document the expected registry and trusted publisher identity. - Review the pinned package version, including lifecycle scripts and transitive dependencies, before recommending its execution. - Update the pinned version only through a controlled review and testing process.