T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:20- Finding
Unpinned Remote Package Retrieval and Execution
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 20–26
Vulnerability Type:T03: Remote Payload Retrieval and Execution
Risk Level: MediumVulnerable Code Snippet:
json { "mcpServers": { "pipeworx-iplookup": { "command": "npx", "args": ["-y", "mcp-remote@latest", "https://gateway.pipeworx.io/iplookup/mcp"] } } }Technical Analysis
The configuration instructs the user to execute
mcp-remote@latestthroughnpx -y. Thelatesttag does not identify an immutable, reviewed version, while-yautomatically accepts package installation. Consequently, code retrieved and executed in a future installation may differ from the code available when this Skill was audited.This creates a remote code-execution supply-chain boundary: the effective local executable depends on mutable npm registry content and the security of the package publisher, registry, and distribution path. The audit found no evidence that the currently referenced package is malicious; the vulnerability is the automatic execution of mutable, externally supplied code without a version or integrity constraint.
Attack Path
- An attacker compromises the npm package, its publisher account, or another relevant distribution component.
- The attacker causes a malicious release to become the version resolved by
mcp-remote@latest. - A user applies the documented MCP configuration.
npx -yretrieves the attacker-controlled release and runs its package entry point without interactive review.- The malicious package executes with the operating-system permissions and environment access of the user running the MCP client.
Impact Assessment
Successful exploitation could allow arbitrary local code execution under the invoking user's account. Depending on that account's existing permissions and environment, the payload could access readable files, environment variables, network resourc ...[truncated 275 chars]
- Remediation
View remediation
Remediation Suggestions
- Replace
mcp-remote@latestwith an exact, reviewed version. - Install the dependency through a lockfile-controlled project and verify the resolved package integrity hash.
- Avoid automatic
npx -yinstallation for security-sensitive deployment workflows. - Document the expected package publisher, package source, version, and integrity value so users can verify them before execution.
- Review dependency updates before changing the pinned version, including package ownership, release differences, transitive dependencies, and published artifacts.
- Where practical, vendor or reproducibly build the reviewed client and execute only the verified artifact.
- Replace
