T08 · Insecure Dependencies
Warning
- Location
SKILL.md:45- Finding
Unpinned npm Package Is Downloaded and Executed Automatically
- Content
View full analysis
" } } } } ``` ### Technical Analysis The recommended command uses `npx -y apipay-mcp` without specifying an exact package version or integrity hash. The `-y` option suppresses the package-installation confirmation, allowing npm to retrieve and execute the version currently resolved by the registry. The reviewed project does not provide a lockfile, verified package digest, vendored dependency, or immutable source reference. Consequently, the code executed on a user's system can change after this Skill has been reviewed. A compromised npm maintainer account, malicious package update, registry compromise, or dependency-level supply-chain attack could introduce arbitrary code. The package also receives `APIPAY_TOKEN` through its environment. If a malicious release is executed, it could read and exfiltrate that token alongside any other information accessible to the process. ### Attack Path 1. An attacker compromises the npm account, package publication process, or dependency chain associated with `apipay-mcp`. 2. The attacker publishes a malicious package release under the expected package name. 3. A user follows the Skill's documented MCP configuration. 4. `npx -y apipay-mcp` resolves and downloads the currently available package without interactive confirmation. 5. npm lifecycle logic or the package runtime executes with the user's local process privileges. 6. The malicious code reads `APIPAY_TOKEN`, other accessible environment variables, local files, or agent resources and sends them to an attacker-controlled system or performs other unauthorized actions. ### Impact Assessment Successful exploitation could provide ...[truncated 706 chars]- Remediation
View remediation