T08 · Insecure Dependencies
Warning
- Location
- SKILL.md:20
- Finding
- Execution of an Unpinned Package from a Mutable Release Tag## Vulnerability Details **File Location**: `SKILL.md`, line 20 **Vulnerability Type**: Unpinned third-party package execution through `npx` **Risk Level**: Medium **Vulnerable Code Snippet**: ```bash npx clawhub@latest install subagent-driven-development ``` ### Technical Analysis The documented installation command instructs users to download and execute the npm package identified by the mutable `latest` tag. Because neither an immutable package version nor an integrity value is specified, the code executed by this command can change after the skill has been reviewed. `npx` may retrieve the selected package from the configured npm registry and execute its command with the privileges of the invoking user. The security of the installation process therefore depends on the package publisher account, registry configuration, package ownership, and whichever release currently resolves from `latest`. The supplied project does not provide a lockfile, checksum, signature, or other mechanism that binds installation to a reviewed artifact. No evidence establishes that the current package is malicious. The vulnerability is the unsafe, mutable supply-chain execution pattern. ### Attack Path 1. An attacker compromises the package publisher account, package ownership, registry resolution, or another relevant release mechanism. 2. The attacker publishes a malicious package release and causes the `latest` tag to resolve to it. 3. A user follows the installation command in `SKILL.md`. 4. `npx` downloads and executes the attacker-controlled package. 5. The malicious package runs with the invoking user's privileges and can access resources available to that account. ### Impact Assessment Successful exploitation can provide arbitrary code execution under the account running the installation command. Depending on that account's privileges and environment, the payload could read or modify project files, access user-readable credentials ...[truncated 369 chars]
- Remediation
- ## Remediation Suggestions 1. Replace the mutable `latest` tag with an explicitly reviewed and immutable package version, for example: ```bash npx clawhub@<reviewed-version> install subagent-driven-development ``` 2. Verify the package's expected registry, publisher, and ownership before installation. 3. Where supported, validate package provenance, signatures, or integrity hashes before execution. 4. Use a lockfile or equivalent dependency-pinning mechanism when integrating the package into a managed project. 5. Avoid running the installer with administrator or root privileges. 6. Execute installation in an isolated environment with no unnecessary credentials or sensitive host mounts. 7. Establish a controlled update process in which new versions are reviewed before the documented version is changed.