T08 · Insecure Dependencies
Warning
- Location
- README.md:31
- Finding
- Unpinned Third-Party Package Execution in Installation Recommendations## Vulnerability Details **File Location**: `README.md`, lines 31–33 **Vulnerability Type**: Unpinned third-party supply-chain dependencies **Risk Level**: Medium ### Complete Code Snippet ```bash npx clawhub install openclaw-auto-backup npx clawhub install openclaw-memory-enhancer npx clawhub install openclaw-search-pro ``` ### Technical Analysis The documentation recommends invoking three third-party packages through `npx` without fixed versions, integrity hashes, verified provenance, or source-review requirements. These packages are optional and are not required for the project's local agent-orchestration functionality. Because package names resolve to mutable registry content, the code executed by these commands can differ from the code available when this project was audited. Depending on the behavior of `npx` and the resolved packages, package entry points or lifecycle scripts may execute automatically. This creates a supply-chain trust boundary outside the audited project. The bundled Python implementation itself does not retrieve or execute remote payloads. The risk arises only if a user follows these optional documentation commands. ### Attack Path 1. An attacker compromises a referenced package, its publisher account, or the package registry resolution path. Alternatively, the attacker gains control of an abandoned or unclaimed referenced package name. 2. The attacker publishes a malicious version containing a hostile executable entry point or lifecycle script. 3. A user follows the recommendation in `README.md` without pinning or independently reviewing the resolved package. 4. `npx` retrieves the current package content from the configured registry. 5. The malicious package code executes with the permissions of the user running the command. ### Impact Assessment Successful exploitation could permit arbitrary code execution under the invoking user's account. The resulting scope could include access to files, environment variables, credent ...[truncated 302 chars]
- Remediation
- ## Remediation Suggestions 1. Remove the unrelated third-party installation recommendations unless they are necessary for core functionality. 2. If these integrations must remain, pin every package to a specifically reviewed version rather than resolving the latest mutable release. 3. Document the expected publisher, registry, package digest, and source repository so users can verify provenance. 4. Verify package integrity using cryptographic hashes or lockfile integrity metadata. 5. Review package entry points, transitive dependencies, and lifecycle scripts before recommending execution. 6. Disable lifecycle scripts where practical and install packages in an isolated, least-privileged environment. 7. Clearly mark the commands as optional and warn users that they download and execute third-party code outside this project's audit scope.