T08 · Insecure Dependencies
- Location
SKILL.md:17- Finding
Unpinned Third-Party Package Executed Through npx
- Content
View full analysis
--answer 34.5 # → Key saved to ~/.makaron/auth.json # → { "api_key": "mk_live_...", "credits": N, "claim_url": "..." } ``` The same unpinned `npx makaron-cli` execution pattern is used throughout `SKILL.md` for registration, media uploads, project operations, marketplace skill installation, and content generation. ### Technical Analysis The skill directs the agent to execute `makaron-cli` through `npx` without specifying an exact package version, lockfile, integrity hash, trusted registry configuration, or previously reviewed local installation. When the package is not already installed locally, `npx` can resolve and download it from the configured npm registry before executing its package entry point. The code ultimately executed may therefore change after this skill has been reviewed, even if `SKILL.md` remains unchanged. This creates a supply-chain trust boundary in which compromise of the package, its maintainer account, its transitive dependencies, or the configured package registry could result in arbitrary code being executed locally. The risk is amplified because the documented workflows provide the process with access to user media and Makaron credentials. No evidence was found that the currently referenced package is malicious. The vulnerability is the unsafe, unpinned dependency execution mechanism. ### Attack Path 1. An attacker compromises the `makaron-cli` package, a maintainer account, a transitive dependency, or the package source selected by the user's npm configuration. 2. The attacker publishes a modified ...[truncated 1447 chars]- Remediation
View remediation
