T08 · Insecure Dependencies
Warning
- Location
- SKILL.md:21
- Finding
- Unpinned Third-Party Package Execution via npx## Vulnerability Details **File Location**: `SKILL.md`, lines 21-23 **Vulnerability Type**: Unpinned third-party dependency execution **Risk Level**: Medium The documented usage command is: ```bash npx openclaw skill run whale-pulse-monitor ``` ### Technical Analysis The command invokes the `openclaw` npm package through `npx` without specifying an audited version or integrity constraint. If the package is unavailable locally, `npx` may resolve, download, and execute a mutable package from the configured npm registry. Because neither a fixed version nor a lockfile or integrity hash is specified, the code executed by this command can differ from the code originally reviewed. This creates a supply-chain trust boundary in which package compromise, registry-account takeover, or an unexpectedly unsafe future release could result in arbitrary code execution. The repository itself contains only `SKILL.md`; it does not include executable scripts or direct evidence that the current `openclaw` package is malicious. The risk arises from the unsafe, unpinned download-and-execute pattern. ### Attack Path 1. An attacker compromises the relevant package, its publisher account, or another component in the package-resolution path. 2. The attacker publishes a malicious version that can be selected by the unpinned `npx` command. 3. A user follows the documented usage instructions. 4. `npx` resolves and downloads the attacker-controlled release when no trusted local version is available. 5. Package lifecycle hooks or runtime logic execute with the invoking user's privileges. ### Impact Assessment Successful exploitation could execute arbitrary code under the account running the command. Depending on that account's permissions and environment, the malicious package could access readable files, environment variables, developer credentials, wallet-related material, or network services; alter user-owned files; and make outbound network re ...[truncated 218 chars]
- Remediation
- ## Remediation Suggestions - Pin `openclaw` to a specific, audited version rather than allowing mutable resolution, for example: ```bash npx --yes openclaw@<audited-version> skill run whale-pulse-monitor ``` - Prefer installing dependencies through a committed lockfile and executing the locked local binary. - Verify package provenance and integrity through registry integrity metadata, trusted signatures, or approved checksums. - Document the expected package publisher, official registry, source repository, and audited version. - Disable or ignore dependency lifecycle scripts where operationally possible. - Run the command in a least-privileged, isolated environment without unnecessary credentials or sensitive mounted files. - Establish a controlled dependency-update process that reviews new releases before changing the pinned version.