T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:21- Finding
Mutable Remote Package Is Downloaded and Executed Without Version or Integrity Pinning
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 21-29
Vulnerability Type: Remote payload execution through an insecure, mutable dependency
Risk Level: HighVulnerable Code
json { "mcpServers": { "pipeworx-nationalize": { "command": "npx", "args": ["-y", "mcp-remote@latest", "https://gateway.pipeworx.io/nationalize/mcp"] } } }Technical Analysis
The documented configuration invokes
npxwith the-yoption and the mutable package referencemcp-remote@latest. This causes package code obtained from an external registry to be executed automatically without interactive confirmation.The
latesttag does not identify a fixed, reviewed artifact. Its target can change after the skill has been audited, meaning that future installations may execute code different from the version originally assessed. No lockfile, exact version, package integrity hash, or other artifact-verification mechanism is specified.This creates a supply-chain execution boundary: compromise of the package publisher, registry account, package distribution infrastructure, or a future package release could result in arbitrary code running on the local system. The externally operated MCP gateway at
https://gateway.pipeworx.io/nationalize/mcpalso represents a separate trust boundary and should be explicitly documented and constrained, although the reviewed file does not establish that this gateway directly supplies executable local code.Attack Path
- An attacker compromises the
mcp-remotepublishing account or causes a malicious release to become the package'slatestversion. - A user follows the configuration in
SKILL.mdand starts the MCP server. npx -yresolves and downloads the package currently referenced bymcp-remote@latest.- The downloaded package is executed automatically without confirmation or integrity validation.
- Malicious package code runs wit ...[truncated 1001 chars]
- An attacker compromises the
- Remediation
View remediation
Remediation Suggestions
- Replace
mcp-remote@latestwith an exact, reviewed version, such asmcp-remote@x.y.z. - Use a lockfile and verify the package's registry integrity hash before execution.
- Avoid automatic installation with
npx -y; install the approved dependency through a controlled build or deployment process. - Mirror or vendor the reviewed package in a trusted internal repository where practical.
- Run the MCP client with a dedicated, least-privileged account or inside a restricted container or sandbox.
- Limit filesystem access, environment-variable exposure, credential availability, and outbound network access for the MCP process.
- Document the remote gateway as an external trust boundary and validate its TLS endpoint, ownership, data-handling policy, and expected MCP capabilities.
- Establish dependency monitoring and a controlled review process before updating the pinned package version.
- Replace
