T08 · Insecure Dependencies
- Location
SKILL.md:30- Finding
Unpinned Dependency Installation and Execution
- Content
View full analysis
&& pnpm install --frozen-lockfile 2>/dev/null || pnpm install ``` ```bash cd && GRAPH_DIR= npx vite --open ``` ### Technical Analysis The skill first attempts installation with a frozen lockfile but automatically falls back to an unrestricted `pnpm install` if the initial command fails. This fallback can resolve package versions that are not fixed by the reviewed lockfile, weakening dependency integrity guarantees. The subsequent use of `npx vite --open` also does not explicitly require a pinned, locally installed Vite binary. If the executable is unavailable locally, `npx` may offer to retrieve and execute a package from the configured registry. Package installation can additionally execute dependency lifecycle scripts with the privileges of the user running the skill. This creates a supply-chain code-execution boundary in which package registry contents, dependency metadata, lockfile state, and package lifecycle scripts can influence locally executed code. ### Attack Path 1. The dashboard has a missing, invalid, outdated, or incompatible lockfile, or the frozen installation otherwise fails. 2. The `|| pnpm install` fallback performs dependency resolution without requiring the reviewed lockfile to remain unchanged. 3. An attacker-controlled or compromised dependency version is selected from the configured package registry. 4. Malicious code runs through an installation lifecycle script or when the dashboard package is loaded. 5. Alternatively, if no local Vite executable is available, `npx vite` retrieves or executes a registry-supplied package. 6. The package executes with the privileges and environment access of the user who invoked the skill. ### Impact Assessment Successful ...[truncated 503 chars]- Remediation
View remediation
/dev/null`; report failures so users can make an informed decision. ]]>
