T08 · Insecure Dependencies
Warning
- Location
- SKILL.md:5
- Finding
- Unreviewed Third-Party npm Package Is Installed and Executed## Vulnerability Details **File Location**: `SKILL.md:5, 55-63` and `SKILL-cn.md:5, 55-63` **Vulnerability Type**: Third-party dependency and supply-chain exposure **Risk Level**: Medium The Skill directs the host to install globally or immediately execute an npm-hosted package whose implementation is not included in the audited project. ```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 this skill is called, run 'dlazy chat --skill file-to-video --prompt ...' for a new task, or 'dlazy chat --project <id> --prompt ...' to continue (discover ids via 'dlazy projects list'). Never pass both --skill and --project."}} ``` ```bash npx @dlazy/cli@1.2.3 <command> ``` ```bash npm install -g @dlazy/cli@1.2.3 ``` The Chinese-language document contains the same installation and execution instructions. ### Technical Analysis `npm install -g` retrieves a package from the npm registry, processes its installation behavior, and persists a globally available executable. `npx` also retrieves and executes package code locally. The source code of `@dlazy/cli@1.2.3`, its transitive dependencies, and any npm lifecycle scripts are absent from this project, so their behavior could not be verified during this audit. Pinning the package to version `1.2.3` reduces exposure to unexpected future upgrades but does not establish the integrity of that release or its transitive dependencies. A compromised npm publisher account, malicious release, dependency compromise, or registry substitution could therefore cause unreviewed code to ...[truncated 1568 chars]
- Remediation
- ## Remediation Suggestions 1. Vendor the exact CLI source and required dependencies into a reviewable, version-controlled build process. 2. Verify downloaded release artifacts against a trusted cryptographic digest or signed provenance record rather than relying on a version number alone. 3. Use a lockfile with integrity hashes and review the complete transitive dependency tree. 4. Disable npm lifecycle scripts where compatible, such as by using `--ignore-scripts`, and explicitly audit any scripts that must remain enabled. 5. Prefer an isolated, least-privileged environment over global installation. Avoid running npm or the CLI as an administrator or root user. 6. If `npx` remains supported, configure an approved registry and package cache, enforce integrity verification, and prevent silent fallback to untrusted registries. 7. Pin dependencies by immutable artifact digest where the distribution mechanism supports it. 8. Run the CLI in a sandbox with restricted filesystem access, narrowly scoped network access, and only the files explicitly selected by the user. 9. Document the package verification procedure and periodically audit the pinned release and all transitive dependencies for known vulnerabilities.