T08 · Insecure Dependencies
Warning
- Location
- SKILL.md:19
- Finding
- Execution of a Mutable npm Package Version Through npx## Vulnerability Details **File Location**: `SKILL.md`, line 19 **Vulnerability Type**: `T08: Insecure Dependencies` **Risk Level**: Medium **Complete Code Snippet**: ```markdown - Use `npx acpx@latest` only for explicit manual experiments or upgrade checks, not as the default OpenClaw runtime backend. ``` ### Technical Analysis The skill permits `npx acpx@latest` for manual experiments and upgrade checks. The `latest` tag is mutable and does not identify a specific audited package artifact. When invoked, `npx` may retrieve and execute the package version currently associated with that tag, including its transitive dependencies and lifecycle behavior. Consequently, the effective executable payload can change after this skill has been reviewed. If the package publisher, npm account, registry distribution channel, release process, or dependency tree is compromised, following this instruction could execute unreviewed code locally. The instruction limits this command to explicit experiments or upgrade checks and separately recommends a pinned plugin-local runtime, reducing likelihood. However, it does not remove the supply-chain execution risk when the permitted exception is used. ### Attack Path 1. An operator requests a manual experiment or upgrade check. 2. The agent follows the permitted instruction and invokes `npx acpx@latest`. 3. `npx` resolves the mutable `latest` tag using the configured npm registry. 4. It downloads the current package release and any required dependencies if they are not already available locally. 5. A compromised or malicious release, dependency, or registry response executes under the invoking user's account. 6. The malicious code can act within that account's process, filesystem, network, and credential-access boundaries. ### Impact Assessment Successful exploitation could provide arbitrary code execution with the privileges of the user running `npx`. Depending on the local environment a ...[truncated 416 chars]
- Remediation
- ## Remediation Suggestions - Remove the authorization to execute `npx acpx@latest`. - Use only the documented plugin-local binary backed by the managed, pinned dependency. - If a separate upgrade check is necessary, query package metadata without executing the package. - Test upgrades using an exact version in an isolated, least-privileged environment with no production credentials or sensitive repository access. - Verify package provenance and integrity before execution, including lockfile and integrity-hash validation. - Subject each proposed version and its transitive dependency changes to security review before updating the managed runtime. - Where supported, restrict package lifecycle scripts and outbound network access during validation.