T08 · Insecure Dependencies
- Location
SKILL.md:20- Finding
Unpinned Third-Party Package Is Automatically Downloaded and Executed
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 20-22 and 40-45
Vulnerability Type: Unpinned executable dependency and supply-chain exposure
Risk Level: HighVulnerable code (lines 20-22):
yaml install: - kind: node package: "@mealmastery/mcp-server"Vulnerable code (lines 40-45):
json "command": "npx", "args": ["-y", "@mealmastery/mcp-server"], "env": { "MEALMASTERY_API_KEY": "${MEALMASTERY_API_KEY}" }Technical Analysis
The configuration invokes
npx -ywith no exact package version or integrity constraint. Consequently, execution can resolve to the package version currently supplied by the npm registry rather than to an immutable artifact reviewed with this Skill. The-yoption also suppresses the normal installation confirmation.The downloaded package executes locally and receives
MEALMASTERY_API_KEYin its environment. Its source is not included in the audited project, so this audit cannot verify its credential handling, network destinations, command execution, or access to local resources. A compromised package release, publisher account, or dependency-resolution path could therefore substitute malicious executable code after this Skill has been reviewed.Remote processing of meal preferences, allergy information, grocery lists, subscription state, and checkout requests is consistent with the declared hosted service. The documentation also requires a dry run and explicit confirmation before checkout. The confirmed issue is not the service's necessary network communication itself, but the mutable and automatically executed package used to implement it.
Attack Path
- An attacker compromises the npm publisher account, package publication process, registry resolution, or another relevant supply-chain component.
- The attacker publishes or causes resolution to a malicious version of
@mealmastery/mcp-server. - A user starts the conf ...[truncated 1276 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin
@mealmastery/mcp-serverto a reviewed, exact version rather than relying on the registry's current version. - Install through a committed lockfile and enforce package integrity verification during installation.
- Avoid launching the dependency through an automatically approving
npx -yflow. Use a controlled installation stage followed by execution of the verified local artifact. - Verify package provenance and signatures where supported, monitor publisher and package changes, and require security review before upgrades.
- Run the MCP server in a sandbox or container with narrowly restricted filesystem, process, and outbound-network access.
- Supply a narrowly scoped, revocable API token and avoid exposing unrelated secrets to the process environment.
- Restrict outbound traffic to documented MealMastery endpoints if operationally feasible.
- Publish or vendor the reviewed server implementation so its credential handling and network behavior can be independently audited.
- Pin
