T08 · Insecure Dependencies
Warning
- Location
- SKILL.md:16
- Finding
- Unpinned ClawHub Package Execution via npx## Vulnerability Details **File Location**: `SKILL.md:16-18` and `README.md:31-33` **Vulnerability Type**: Unpinned third-party dependency execution **Risk Level**: Medium ### Vulnerable Code `SKILL.md:16-18`: ```bash npx clawhub@latest install auto-context ``` The same command is documented in `README.md:31-33`: ```bash npx clawhub@latest install auto-context ``` ### Technical Analysis The installation instructions direct users to execute `clawhub@latest` through `npx`. The `latest` tag is mutable and does not identify an immutable, previously reviewed package version. When the command is run, `npx` may download and immediately execute whichever package release the registry resolves under that tag at that time. Consequently, the effective executable can change after this skill has been audited. Security depends on the continued integrity of the npm account, registry metadata, package publication process, transitive dependencies, and every future release selected by `latest`. This is a supply-chain weakness rather than evidence that the current ClawHub package is malicious. ### Attack Path 1. An attacker compromises the `clawhub` package publisher, publication workflow, registry entry, or a dependency used by a future release. 2. The attacker publishes a malicious release and causes the mutable `latest` tag to resolve to it. 3. A user follows the documented installation command. 4. `npx` retrieves and executes the attacker-controlled package without an immutable version or integrity value being specified by the project. 5. Malicious CLI, lifecycle, or dependency code runs under the account invoking the command. ### Impact Assessment Exploited code would generally inherit the installing user's privileges and environment. Depending on those privileges, it could read or alter user-accessible files, access credentials exposed to the process, modify development configuration, install additional software, or ...[truncated 204 chars]
- Remediation
- ## Remediation Suggestions - Replace `@latest` with an explicitly reviewed, immutable package version. - Commit and enforce a lockfile where the installation workflow supports one. - Verify package provenance, signatures, and registry integrity metadata before execution. - Review the selected package version and its transitive dependency tree before recommending it. - Run installation with the least-privileged account possible and avoid elevated shells. - In CI, use an allowlisted internal registry or verified artifact mirror and restrict network, filesystem, and secret access during installation. - Keep `SKILL.md` and `README.md` synchronized so both use the same pinned and reviewed command.