T08 · Insecure Dependencies
Warning
- Location
- SKILL.md:3
- Finding
- Third-Party CLI Execution Without Artifact Integrity Verification## Vulnerability Details **File Location**: `SKILL.md:3-63`; equivalent instructions appear in `SKILL-cn.md:3-63` **Vulnerability Type**: T08: Insecure Dependencies **Risk Level**: Medium ### Vulnerable Code ```yaml metadata: {"clawdbot":{"emoji":"🤖","requires":{"bins":["npm","npx"]},"install":"npm install -g @dlazy/cli@1.2.3","installAlternative":"npx @dlazy/cli@1.2.3","homepage":"https://github.com/dlazy-ai/cli","source":"https://github.com/dlazy-ai/cli","author":"dlazyai","license":"see-repo","npm":"https://www.npmjs.com/package/@dlazy/cli","configLocation":"~/.dlazy/config.json","apiEndpoints":["api.dlazy.com","files.dlazy.com"]},"openclaw":{"systemPrompt":"When invoking this skill, use dlazy search_audio -h for help."}} ``` ```bash npx @dlazy/cli@1.2.3 <command> ``` ```bash npm install -g @dlazy/cli@1.2.3 ``` The Chinese-language document contains equivalent installation and execution directives: ```yaml metadata: {"clawdbot":{"emoji":"🤖","requires":{"bins":["npm","npx"]},"install":"npm install -g @dlazy/cli@1.2.3","installAlternative":"npx @dlazy/cli@1.2.3","homepage":"https://github.com/dlazy-ai/cli","source":"https://github.com/dlazy-ai/cli","author":"dlazyai","license":"see-repo","npm":"https://www.npmjs.com/package/@dlazy/cli","configLocation":"~/.dlazy/config.json","apiEndpoints":["api.dlazy.com","files.dlazy.com"]},"openclaw":{"systemPrompt":"When invoking this skill, use dlazy search_audio -h for help."}} ``` ```bash npx @dlazy/cli@1.2.3 <command> ``` ```bash npm install -g @dlazy/cli@1.2.3 ``` ### Technical Analysis The skill requires installation or direct execution of the npm-hosted `@dlazy/cli` package. Pinning the dependency to version `1.2.3` reduces exposure to unintended upgrades, but it does not authenticate the exact package artifact. The project does not provide an expected npm integrity hash, signed release verification, vendored source, a lockfile covering transit ...[truncated 2404 chars]
- Remediation
- ## Remediation Suggestions 1. Publish and verify an expected npm integrity digest for the exact CLI artifact before execution. 2. Use signed releases or package provenance attestations and verify that the npm artifact corresponds to the reviewed source revision. 3. Vendor and audit the required CLI implementation where practical, rather than executing code fetched at invocation time. 4. Lock and review all transitive dependencies using a committed lockfile and automated dependency scanning. 5. Disable npm lifecycle scripts with `--ignore-scripts` where the package can operate without them; otherwise, explicitly audit every required lifecycle script. 6. Run the CLI in a sandbox or container with least-privilege filesystem and network access. 7. Avoid privileged global installation. Prefer an isolated, non-administrative environment with a controlled package cache. 8. Provide the CLI only the files required for the requested operation and avoid exposing unrelated secrets or environment variables. 9. Store the API key with restrictive permissions, use a narrowly scoped credential where supported, and rotate it immediately if package compromise is suspected. 10. Apply the same hardened installation instructions consistently to both `SKILL.md` and `SKILL-cn.md`.