T08 · Insecure Dependencies
Error
- Location
- README.md:16
- Finding
- Unpinned Package Execution in the Documented Installation Command<![CDATA[ ## Vulnerability Details **File Location**: `README.md:16-22` **Vulnerability Type**: Unpinned third-party package execution **Risk Level**: High ### Vulnerable Code ```markdown ## Install ClawHub-style install target: ```bash npx clawhub install ergopitrez/evolution-toolkit ``` ``` ### Technical Analysis The documented installation procedure invokes `clawhub` through `npx` without specifying an audited package version or integrity value. If the package is not already available locally, `npx` can retrieve and execute the version currently resolved by the package registry. Consequently, the executable installer may differ from the version reviewed when this Skill was audited. Compromise of the registry package, its maintainer account, or a future release could turn the installation command into an arbitrary-code execution channel. No evidence shows that the current `clawhub` package is malicious. The vulnerability is the absence of version and integrity controls around executable third-party code. ### Attack Path 1. An attacker compromises the package publisher, registry entry, or distribution account associated with `clawhub`. 2. The attacker publishes a modified release containing malicious installation behavior. 3. A user follows the README and runs the unpinned `npx clawhub install ...` command. 4. `npx` resolves and downloads the attacker-controlled release. 5. The package executes with the privileges of the user running the command. 6. The malicious package can access files and credentials available to that user, alter the workspace, install persistence, or execute additional payloads. ### Impact Assessment Successful exploitation can result in arbitrary code execution under the installer user's account. The accessible scope may include: - The current project and Agent workspace. - Files readable or writable by the user. - Environment variables and developer credentials available to the process. - Network resources accessible from t ...[truncated 224 chars]
- Remediation
- <![CDATA[ ## Remediation Suggestions 1. Pin the installer to a specifically audited version: ```bash npx --yes clawhub@<audited-version> install ergopitrez/evolution-toolkit ``` 2. Publish and verify a cryptographic integrity value or signed release before execution. 3. Prefer a lockfile-backed installation workflow where practical. 4. Instruct users to inspect the resolved package version before running it. 5. Avoid automatically accepting future versions merely because they share the same package name. 6. Run the installer in a restricted container or sandbox without production credentials or sensitive workspace mounts. 7. Document the trusted registry and package publisher identity. 8. Establish a release-review process and update the pinned version only after auditing the new release. ]]>