T08 · Insecure Dependencies
- Location
SKILL.md:47- Finding
Unpinned npm Package Is Downloaded and Executed Automatically
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 47–53
Vulnerability Type: Unpinned third-party dependency execution
Risk Level: MediumVulnerable Code
json { "mcpServers": { "pipeworx-holidays": { "command": "npx", "args": ["-y", "mcp-remote@latest", "https://gateway.pipeworx.io/holidays/mcp"] } } }Technical Analysis
The MCP configuration invokes
npxwith both-yand the mutable package referencemcp-remote@latest. This causes npm to resolve, download, and execute the package selected by thelatesttag without an interactive confirmation step.Because the dependency is not pinned to a reviewed version, the code executed during setup can change after the skill has been audited. If the npm package, its publisher account, or a transitive dependency is compromised, a malicious release can be distributed through the same configuration. There is no evidence in the reviewed file that the package is currently malicious; the vulnerability is the unsafe supply-chain execution mechanism.
Attack Path
- An attacker compromises the
mcp-remotenpm publisher, package, or one of its dependencies. - The attacker publishes a malicious release and causes the
latesttag to resolve to it. - A user or agent applies the documented MCP configuration.
npx -y mcp-remote@latestdownloads the compromised release without requesting confirmation.npxexecutes the package with the privileges and environment of the agent process.- The malicious package can access resources available to that process and execute further commands.
Impact Assessment
Successful exploitation could result in arbitrary local code execution under the account running the MCP server. Depending on that account's permissions and runtime isolation, an attacker could read accessible files and environment variables, steal credentials, modify user-owned data, initiate network connections, or install additional payloads. Th ...[truncated 148 chars]
- An attacker compromises the
- Remediation
View remediation
Remediation Suggestions
- Replace
mcp-remote@latestwith an exact, reviewed package version rather than a mutable distribution tag. - Install the dependency locally through a lockfile-backed workflow and preserve npm integrity metadata.
- Review the pinned package and its transitive dependency tree before deployment.
- Use automated dependency monitoring, but require review and testing before version upgrades.
- Avoid
npx -ywhere practical so unexpected downloads do not execute without confirmation. - Run the MCP bridge in a sandbox or restricted service account with minimal filesystem, environment-variable, process, and network access.
- Consider using a trusted internal package mirror and package provenance verification to reduce registry supply-chain exposure.
- Replace
