T08 · Insecure Dependencies
Warning
- Location
- SKILL.md:5
- Finding
- Unverified Third-Party npm Package Installation and Execution## Vulnerability Details **File Location**: `SKILL.md:5, 47-54`; duplicated in `SKILL-cn.md:5, 47-54` **Vulnerability Type**: Third-party supply-chain execution without artifact integrity verification **Risk Level**: Medium ### Vulnerable Code From `SKILL.md:5`: ```json 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 suno-music -h for help."}} ``` From `SKILL.md:47-54`: ```bash npx @dlazy/cli@1.2.3 <command> ``` ```bash npm install -g @dlazy/cli@1.2.3 ``` Equivalent installation and execution instructions appear in `SKILL-cn.md`. ### Technical Analysis The Skill installs or directly executes `@dlazy/cli@1.2.3` from the npm registry. The external package implementation is not included in the audited project, and the Skill does not specify or verify an immutable package integrity hash or trusted local artifact. Pinning the package to version `1.2.3` reduces version drift but does not independently establish the integrity or safety of the registry artifact. Both `npm install -g` and `npx` can execute package lifecycle scripts or package-provided executable code with the permissions of the invoking user. The global installation option additionally persists the executable in the user's environment. No evidence establishes that the referenced package is currently malicious. The security issue is the unverified external execution boundary: compromise of the package artifact, publisher account, registry distribution path, or a transitive dependency could turn normal Skill install ...[truncated 1606 chars]
- Remediation
- ## Remediation Suggestions 1. Vendor the required CLI implementation or include its auditable source in the reviewed project. 2. Distribute the dependency through a controlled artifact repository and verify a cryptographic integrity hash before execution. 3. Generate and enforce a lockfile with integrity metadata for the complete dependency graph. 4. Review the package source, lifecycle scripts, and transitive dependencies before approving a release. 5. Prefer ephemeral, sandboxed execution over global installation. 6. Disable npm lifecycle scripts where compatible, such as by using `--ignore-scripts`, and explicitly run only reviewed setup operations. 7. Restrict filesystem and network access for the CLI to the minimum resources required for music generation. 8. Do not expose unrelated environment variables or credentials to the process. 9. Avoid running npm or the CLI with administrator or root privileges. 10. Add package provenance or signature verification to the installation workflow and document how users can verify the expected artifact. 11. Periodically audit the pinned package and all transitive dependencies for compromised releases and known vulnerabilities.