T08 · Insecure Dependencies
- Location
SKILL.md:21- Finding
Unpinned Third-Party Package Download and Execution
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 21–22
Vulnerability Type: Unpinned and automatically executed third-party dependency
Risk Level: Mediumjson { "mcpServers": { "pipeworx-nutrition": { "command": "npx", "args": ["-y", "mcp-remote@latest", "https://gateway.pipeworx.io/nutrition/mcp"] } } }Technical Analysis
The configuration invokes
npxwithmcp-remote@latest. Thelatesttag is mutable and does not identify a specific reviewed package release. If the package is unavailable locally,npxcan retrieve its current release from the npm registry and execute it. The-yoption automatically accepts the installation prompt, removing an opportunity for the user to review or reject the downloaded version.Consequently, the code executed at installation or connection time is not fully determined by the audited Skill contents. A compromised maintainer account, malicious package release, or supply-chain compromise could cause arbitrary package code to run. The package also connects to an external MCP endpoint whose behavior can change independently of this repository; however, the endpoint is disclosed and consistent with the Skill's stated remote nutrition functionality, so it is not independently classified as malicious.
Attack Path
- An attacker compromises the npm package, its maintainer account, or the release process for
mcp-remote. - The attacker publishes a malicious release and assigns or causes it to receive the
latestdistribution tag. - A user applies the documented MCP configuration.
npx -y mcp-remote@latestretrieves the malicious release without an interactive installation confirmation.- The downloaded package executes with the privileges and environment access of the user running the Agent.
- The malicious code can perform actions allowed by that account, including accessing readable local data, ...[truncated 567 chars]
- An attacker compromises the npm package, its maintainer account, or the release process for
- Remediation
View remediation
Remediation Suggestions
- Replace
mcp-remote@latestwith an exact, reviewed package version. - Install the dependency through a lockfile-backed workflow and verify its registry integrity hash.
- Remove
-yso that installation or package changes require explicit user confirmation. - Prefer a preinstalled, locally reviewed executable rather than downloading executable code when the MCP connection starts.
- Monitor the pinned dependency for security advisories and update it only after reviewing and testing the new release.
- Document the trust boundary, data transmitted to
gateway.pipeworx.io, expected tool behavior, and any relevant retention or privacy controls. - Run the MCP client with least privilege and restrict filesystem, environment-variable, credential, and network access where sandboxing is available.
- Replace
