T08 · Insecure Dependencies
Warning
- Location
- SKILL.md:29
- Finding
- Unpinned Third-Party Package Execution During Installation## Vulnerability Details **File Location**: `SKILL.md`, line 29 **Vulnerability Type**: Unpinned third-party dependency execution **Risk Level**: Medium **Vulnerable Code Snippet**: ```bash npx clawhub install ai-doc-generator ``` ### Technical Analysis The documented installation command invokes `npx` without specifying a package version or integrity value. Depending on the user's local npm state and registry configuration, `npx` may retrieve and execute the current registry version of `clawhub`. Consequently, the code executed during installation is mutable and lies outside the reviewed project. This creates a supply-chain trust boundary: future package updates, registry-account compromise, package replacement, or a malicious registry configuration could cause a user following the official installation instructions to execute unreviewed code. The audit did not establish that the current `clawhub` package is malicious; the finding concerns the unsafe, unpinned execution mechanism. ### Attack Path 1. An attacker compromises the package publisher, registry entry, distribution infrastructure, or the user's configured npm registry. 2. The attacker publishes or serves a malicious version of the package resolved as `clawhub`. 3. A user follows `SKILL.md` and runs `npx clawhub install ai-doc-generator`. 4. `npx` downloads the mutable package version selected by dependency resolution. 5. Package lifecycle scripts or CLI entry-point code execute with the invoking user's privileges. 6. The malicious code can access resources available to that user and may modify the local environment. ### Impact Assessment Successful exploitation could provide arbitrary code execution under the privileges of the user running the installation command. The potential scope includes readable user files, environment variables, accessible credentials, project files, and network resources available to that account. Further impact would depend on th ...[truncated 192 chars]
- Remediation
- ## Remediation Suggestions 1. Pin the installer to a specifically reviewed version, for example: ```bash npx --yes clawhub@<reviewed-version> install ai-doc-generator ``` 2. Document the official package registry, publisher identity, and source repository so users can verify provenance. 3. Publish and verify package integrity metadata or signatures where the distribution platform supports them. 4. Review the pinned package, including its CLI entry point and npm lifecycle scripts, before recommending execution. 5. Prefer a locally installed, lockfile-controlled dependency or a verified standalone installer over dynamically executing the latest registry release. 6. Advise users not to run the installation command with administrator or root privileges. 7. Add an update process that requires security review before changing the pinned version.