T08 · Insecure Dependencies
- Location
SKILL.md:8- Finding
Runtime Download and Execution of Unverified npm Dependencies
- Content
View full analysis
[options] ``` ### Technical Analysis The permitted commands use `npx` to obtain and immediately execute code from the configured npm registry. Although `md-bookify` is pinned to version `2.2.1`, the Skill provides no lockfile, vendored dependency set, package-integrity verification, or other mechanism that verifies the package and its transitive dependency graph before execution. The Puppeteer command is less deterministic because `@24` selects a mutable major-version range rather than one exact reviewed release. Different executions can therefore resolve to different package versions. The browser-installation command also downloads an additional executable artifact. This creates a supply-chain trust boundary in which code not contained in the audited project executes with the Agent process's operating-system permissions. The package version shown in the command reduces version drift for `md-bookify`, but it does not eliminate registry compromise, compromised releases, malicious lifecycle behavior, or risks in unresolved transitive dependencies. ### Attack Path 1. A user asks the Agent to convert a Markdown document or resolve the documented missing-Chromium condition. 2. The Agent invokes one of the permitted `npx` commands. 3. `npx` resolves and, when not already available locally, downloads the package and its dependencies from the configured npm registry. 4. A compromised package release, registry response, or transitive dependency supplies malicious code. 5. npm lifecycle code or package runtime code executes local ...[truncated 669 chars]- Remediation
View remediation
