T08 · Insecure Dependencies
Warning
- Location
- SKILL.md:3
- Finding
- Unpinned Remote Package Retrieval and Execution via npx## Vulnerability Details **File Location**: `SKILL.md`, lines 3-10 **Vulnerability Type**: Unpinned third-party package installation **Risk Level**: Medium ### Evidence ```markdown description: "[DEPRECATED] Renamed to polymarket-paper-trader. Run: npx clawhub install polymarket-paper-trader" version: 0.2.0 --- # pm-sim is now polymarket-paper-trader This skill has been renamed. Install the new version: ``` npx clawhub install polymarket-paper-trader ``` ``` ### Technical Analysis The documented command invokes `clawhub` through `npx` without specifying a package version or integrity constraint. If `clawhub` is not already available locally, `npx` may retrieve and execute its current registry version. The requested `polymarket-paper-trader` skill is likewise not version-pinned. Consequently, the code executed or installed when a user follows this instruction is mutable and is not included in the audited project. A registry compromise, maintainer account compromise, malicious package update, or package-name takeover could cause future users to receive behavior different from what was available at audit time. ### Attack Path 1. An attacker compromises the package publishing account, registry entry, or distribution channel for `clawhub` or `polymarket-paper-trader`. 2. The attacker publishes a malicious release under the expected package name. 3. A user follows the instruction in `SKILL.md` and runs `npx clawhub install polymarket-paper-trader`. 4. Because no version or integrity value is specified, the command retrieves mutable remote package content. 5. Malicious package lifecycle code, CLI behavior, or installed skill instructions execute or become available in the user's environment. ### Impact Assessment Malicious `clawhub` code executed by `npx` could run with the privileges of the invoking user. Depending on that user's permissions and environment, it could read or modify accessible files, environ ...[truncated 445 chars]
- Remediation
- ## Remediation Suggestions 1. Pin both the installer and successor skill to explicitly reviewed versions rather than relying on the latest registry releases. 2. Configure and document an approved registry instead of allowing implicit registry selection. 3. Verify package provenance using publisher signatures, trusted release attestations, checksums, or lockfile integrity metadata before execution. 4. Prefer downloading and inspecting the package before running it, rather than allowing `npx` to retrieve and immediately execute mutable code. 5. Run installation in a sandbox or least-privileged environment without production credentials or sensitive filesystem access. 6. Document the expected package publisher, exact version, and integrity digest so users can detect substitution or unauthorized updates. 7. Periodically review pinned releases and update them only after security validation.