T08 · Insecure Dependencies
- Location
SKILL.md:34- Finding
Execution of Unpinned Third-Party Packages Through npx
- Content
View full analysis
/dev/null || npx madge --circular src/ # SKILL.md:51 npx ts-prune 2>/dev/null || npx madge --not --extensions ts,tsx # SKILL.md:72 npx complexity-report --dest ./complexity-report.html 2>/dev/null # SKILL.md:115 npx npm-check-updates 2>/dev/null ``` ### Technical Analysis The Skill recommends invoking multiple packages through `npx` without fixed versions, integrity verification, a committed lockfile requirement, or the `--no-install` restriction. If a requested package is not already installed locally, `npx` may retrieve and immediately execute it from the configured package registry. This creates a supply-chain exposure because the code executed during an audit can change independently of the reviewed Skill. A compromised package release, registry account, dependency chain, or registry configuration could cause arbitrary package code to run under the Agent's identity. The commands also do not require a previously reviewed local installation. ### Attack Path 1. The architecture-review Skill is activated for a target repository. 2. One of the documented `npx` commands is invoked. 3. The requested package is unavailable in the local dependency installation. 4. `npx` resolves and downloads the package from the configured registry. 5. Package lifecycle behavior or CLI entry-point code executes locally. 6. A malicious or compromised package performs actions with the same filesystem, process, and network permissions available to the Agent. ### Impact Assessment Successful exploitation could provide arbitrary code execution with the privileges of the Agent process. Depending on the execution environment, this may permit reading accessible source code and configuration, modifying the audited workspace, spawning child processes, ...[truncated 231 chars]- Remediation
View remediation
