AttackResearch disclosuremcp-remote (npm)

Connecting to a malicious MCP server could run commands on your laptop

A flaw in mcp-remote, a popular proxy that connects local AI clients to remote MCP servers, let a malicious server run commands on the client machine during login. It was fixed in version 0.1.16.

By the NoFly team

What NoFly would decideIllustrative
Allowed, with a flagDiscover · machine scan
npx mcp-remote https://mcp.unknown-vendor.example/sse
Agent
Claude Desktop
Came from
An MCP config on a developer laptop
Rule
Vulnerable package version (CVE-2025-6514)
Why
This mcp-remote version is affected. Update to 0.1.16 or later.

What happened

JFrog disclosed CVE-2025-6514, rated 9.6, on 9 July 2025. When mcp-remote connects to a server that requires OAuth, it opens the server’s authorization address in a browser, and it passed that address straight to the operating system.

A malicious or hijacked server could return a crafted address that, on Windows, ran any command with full control of its arguments, and on macOS and Linux launched programs. Versions 0.0.5 to 0.1.15 were affected, and the package had been downloaded more than 437,000 times.

  1. 01

    A laptop uses mcp-remote to reach a remote MCP server.

  2. 02

    The server asks it to log in with OAuth.

  3. 03

    The server returns a crafted login address.

  4. 04

    mcp-remote hands it to the operating system, which runs it.

Why it worked

Probable cause

An address controlled by the remote server reached an operating-system open call without being checked.

How NoFly stops it

  • Discover

    The packages behind every MCP config are matched against vulnerability data, so the machines running an affected mcp-remote version show up with the fix: update to 0.1.16.

  • Protect

    Agents can reach remote MCP servers through one NoFly gateway with their own credentials, rather than a proxy running on every laptop.

  • Govern

    Only approved MCP servers are allowed, so an agent is not pointed at an unknown server in the first place.

What to do this week

This week3 actions
  1. Update mcp-remote to 0.1.16 or later everywhere.
  2. Connect only to MCP servers you trust, over HTTPS.
  3. List which laptops connect to remote MCP servers, and through what.
Keep reading

More from the blog.

Find out what your AI is allowed to do today.

Book a call and we will map your agents, MCP servers and keys with you, or start on one laptop with the free scan.

Book a demo
npm i -g @nofly/agent