T08 · Insecure Dependencies
Warning
- Location
- README.md:6
- Finding
- Unpinned npm Package Execution in Installation Instructions## Vulnerability Details **File Location**: `README.md`, line 6 **Vulnerability Type**: Supply-chain exposure through unpinned remote package execution **Risk Level**: Medium **Vulnerable Code:** ```bash npx clawhub install dating-app-coach ``` ### Technical Analysis The documented installation command invokes `clawhub` through `npx` without specifying a package version or integrity value. If the package is not already available locally, `npx` may retrieve and execute the currently published package from the configured npm registry. Because the dependency is mutable and its implementation is not included in this repository, the code executed by this command can differ from the code that was originally reviewed. This creates a supply-chain trust boundary: compromise of the package, its publisher account, or the configured registry could cause the installation command to execute attacker-controlled code. The repository does not provide a lockfile, expected package version, integrity hash, registry constraint, or other mechanism for authenticating the package executed by this command. ### Attack Path 1. An attacker compromises the `clawhub` npm package, its publisher account, or an npm registry used by the victim. 2. The attacker publishes a malicious version under the expected package name. 3. A user follows the installation instructions and runs `npx clawhub install dating-app-coach`. 4. `npx` resolves and downloads the mutable package version from the configured registry. 5. The downloaded package executes with the privileges of the user running the command. 6. Malicious package code can access resources available to that user, subject to operating-system and environment restrictions. ### Impact Assessment Successful exploitation could provide arbitrary code execution with the privileges of the installing user. Depending on that user's permissions and environment, the malicious package could read or modify user-ac ...[truncated 374 chars]
- Remediation
- ## Remediation Suggestions - Pin `clawhub` to a specific reviewed version rather than resolving the latest release implicitly. - Verify the selected release's provenance and integrity before documenting it for installation. - Use a lockfile or an equivalent reproducible dependency mechanism where supported. - Document the trusted npm registry and avoid allowing installation from arbitrary registry configurations. - Prefer installing the pinned package without executing it immediately, reviewing its contents, and then invoking the verified local binary. - In automated environments, run installation with minimal privileges and without unnecessary credentials or sensitive environment variables. - Consider publishing checksums or signed provenance information for the expected installer artifact.