T08 · Insecure Dependencies
- Location
SKILL.md:27- Finding
Unpinned npm Package Is Automatically Downloaded and Executed
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 27-28
Vulnerability Type: Unsafe dependency resolution and automatic execution
Risk Level: HighVulnerable Code
json { "mcpServers": { "pipeworx-launches": { "command": "npx", "args": ["-y", "mcp-remote@latest", "https://gateway.pipeworx.io/launches/mcp"] } } }Technical Analysis
The documented MCP configuration invokes
npxwith both the-yoption and the mutable dependency specifiermcp-remote@latest. The-yoption suppresses installation confirmation, while@latestresolves to whichever package version the npm registry currently marks as latest.Consequently, the code executed by this configuration is not fixed to the version reviewed when the skill was published. A future release can change the effective executable without any corresponding modification to this repository. If the package publisher account, package ownership, release pipeline, or npm distribution channel is compromised, an attacker can cause users following this configuration to download and execute attacker-controlled package lifecycle or runtime code.
Attack Path
- A user copies the documented MCP server configuration into an MCP client.
- An attacker compromises the
mcp-remotepublishing account or otherwise gains the ability to publish or designate a malicious release. - The malicious release becomes the npm package's
latestversion. - The MCP client starts the configured server and runs
npx -y mcp-remote@latest. npxautomatically downloads the newly resolved package without requesting confirmation.- Package installation hooks or the package executable run with the privileges of the user who launched the MCP client.
- The malicious code can access resources available to that user and can potentially establish additional compromise.
Impact Assessment
Successful exploitation provides arb ...[truncated 619 chars]
- Remediation
View remediation
Remediation Suggestions
- Replace
mcp-remote@latestwith a specifically reviewed version, such asmcp-remote@X.Y.Z. - Prefer installing the dependency through a committed lockfile and using
npm ci, which enforces the resolved package version and integrity metadata. - Where practical, verify the package artifact against an independently recorded cryptographic digest or trusted provenance attestation.
- Remove
-yif interactive approval is acceptable so unexpected installation is not silently authorized. - Establish a controlled dependency-update process that reviews release notes, package ownership, provenance, lifecycle scripts, and code changes before updating the pinned version.
- Run the MCP process in a restricted account or sandbox with minimal filesystem, credential, environment-variable, and network access.
- Replace
