T08 · Insecure Dependencies
Warning
- Location
- SKILL.md:5
- Finding
- Third-Party CLI Execution Without Integrity Verification<![CDATA[ ## Vulnerability Details **File Location**: `SKILL.md:5, 53-59`; equivalent instructions in `SKILL-cn.md:5, 53-59` **Vulnerability Type**: Unverified third-party npm dependency execution **Risk Level**: Medium ### Vulnerable Code From `SKILL.md`: ```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 gemini-2.5-tts -h for help."}} ``` ```bash npx @dlazy/cli@1.2.3 <command> ``` ```bash npm install -g @dlazy/cli@1.2.3 ``` The same installation and execution mechanisms appear in `SKILL-cn.md`: ```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":"当调用此技能时，可以使用 dlazy gemini-2.5-tts -h 查看帮助信息。"}} ``` ```bash npx @dlazy/cli@1.2.3 <command> ``` ```bash npm install -g @dlazy/cli@1.2.3 ``` ### Technical Analysis The Skill depends on and executes `@dlazy/cli@1.2.3`, but the dependency implementation is not included in the audited project. Pinning the version reduces exposure to unexpected version upgrades, but it does not cryptographically verify the retrieved artifact. The project provides no package lockfile, checksum, signature-validation step, vendored source, or reproducible-build verification. Both document ...[truncated 2014 chars]
- Remediation
- <![CDATA[ ## Remediation Suggestions 1. Vendor and audit the required CLI implementation or distribute it through a controlled, reviewed build process. 2. Publish cryptographic checksums or signed provenance for the exact package artifact and verify them before execution. 3. Commit a lockfile containing integrity metadata where the deployment model supports it. 4. Prefer a project-local, isolated installation instead of `npm install -g`, reducing persistence and system-wide exposure. 5. Disable npm lifecycle scripts with `--ignore-scripts` when they are not strictly required, and explicitly review any required scripts. 6. Run the CLI in a least-privilege sandbox or container with restricted filesystem, credential, and network access. 7. Avoid exposing unrelated environment variables or files to the CLI process. 8. Verify that `@dlazy/cli@1.2.3` corresponds to a reviewed source revision and use reproducible builds to confirm that the published artifact matches that source. 9. Document package verification and incident-response procedures, including API-key rotation if dependency compromise is suspected. ]]>