T08 · Insecure Dependencies
Warning
- Location
- README.md:6
- Finding
- Unpinned Third-Party Package Execution in Installation Instructions## Vulnerability Details **File Location**: `README.md:6` **Vulnerability Type**: Supply-chain risk caused by executing a mutable package release **Risk Level**: Medium **Vulnerable Code Snippet**: ```bash npx clawhub@latest install hiking-tracker ``` ### Technical Analysis The documented installation command instructs users to download and execute the `latest` release of the third-party npm package `clawhub`. The `latest` tag is mutable and does not identify a specific, audited package version or integrity hash. Consequently, the code executed by this command may change after the Skill has been reviewed. `npx` can download and run package code as the current user. If the package publisher account, npm distribution channel, or a future package release is compromised, following the documented installation procedure could execute attacker-controlled code. The repository provides no lockfile, checksum, signature-verification procedure, or pinned version that would allow users to verify the fetched package against a known-good artifact. This finding establishes an unsafe dependency-execution pattern; it does not establish that the current `clawhub` package is malicious. ### Attack Path 1. An attacker compromises the npm publisher account, package distribution path, or release process for `clawhub`. 2. The attacker publishes a malicious release and assigns it the mutable `latest` tag. 3. A user follows the installation command documented in `README.md`. 4. `npx` retrieves the attacker-controlled package release. 5. Package lifecycle behavior or the invoked CLI executes with the privileges of the user running the command. 6. The malicious package can access or modify resources available to that user before or while processing the Skill installation. ### Impact Assessment Successful exploitation could provide arbitrary code execution under the installing user's account. The attainable scope includes reading user-accessi ...[truncated 465 chars]
- Remediation
- ## Remediation Suggestions 1. Replace `@latest` with an explicitly reviewed and pinned package version, for example: ```bash npx clawhub@<reviewed-version> install hiking-tracker ``` 2. Verify the selected package version and publisher before documenting it. 3. Record and validate the expected package integrity hash or use a lockfile-backed installation workflow where applicable. 4. Prefer a trusted internal registry or an independently verifiable signed release when the installation tooling supports it. 5. Configure CI or dependency-monitoring controls to review version changes rather than automatically following mutable tags. 6. Document that users should not run the installation command with administrative privileges.