T08 · Insecure Dependencies
Warning
- Location
SKILL.md:5- Finding
Third-Party CLI Is Retrieved and Executed Without Integrity Verification
- Content
View full analysis
``` The equivalent installation and invocation instructions appear in `SKILL-cn.md:5, 48-54`. ### Technical Analysis The Skill delegates its operation to the externally distributed `@dlazy/cli` npm package. Although the package version is pinned to `1.2.3`, the project does not include the CLI implementation, a vendored dependency, a package lockfile, a cryptographic checksum, or a signature-verification procedure. Version pinning limits unexpected upgrades but does not independently authenticate the retrieved package contents. Both `npm install -g` and `npx` can retrieve executable package content from the npm distribution channel. Package installation may also execute npm lifecycle scripts unless explicitly disabled. Consequently, the effective code executed by the Skill cannot be verified solely by auditing this project. The global installation option increases exposure by persisting the executable outside the Skill directory and making it available to later sessions. The CLI is also expected to access the user's dLazy API key, selected local media, and remote API endpoints, making compromise of this dependency security-sensitive. No evidence was found that the named package is currently malicious. This finding concerns the absence of dependency integrity controls and the resulting supply-chain attack surface. ### Attack Path 1. An attacker compromises the npm package publisher account, package artifact, registry delivery path, or another relevant distribution component. 2. Malicious content is associated with or served for ...[truncated 1436 chars]- Remediation
View remediation