Supply chainpostmark-mcp (npm)

A fake Postmark MCP server copied every email it sent to an attacker

An npm package imitating Postmark’s MCP server behaved normally for fifteen versions, then added a hidden BCC to an attacker’s address on every email. It was the first malicious MCP server found in the wild.

By the NoFly team

What NoFly would decideIllustrative
Quarantined before first useMCP gateway
send_email(to: "customer@…", subject: "Your invoice")
Agent
postmark-mcp 1.0.16
Came from
A new version of an approved server
Rule
Server changed after approval
Why
The code changed since it was approved. Calls wait for a new review.

What happened

The package appeared on npm on 15 September 2025, copying the code of Postmark’s own MCP server, which Postmark had not published to npm. After a run of normal versions, version 1.0.16 on 17 September added one line: a blind copy of every outgoing email to the attacker.

Any AI assistant sending mail through it, from password resets to invoices, quietly copied the message to the attacker. The package had 1,643 downloads before the developer deleted it after Koi Security’s findings, and on 25 September Postmark said it had nothing to do with the package.

  1. 01

    An impostor package copies a real vendor’s MCP server.

  2. 02

    A run of clean versions builds trust.

  3. 03

    Version 1.0.16 adds a hidden BCC.

  4. 04

    Every email sent through it is copied to the attacker.

Why it worked

Probable cause

The server came from an unverified publisher using a known brand, and a later version quietly changed what it did with the access it had.

How NoFly stops it

  • Discover

    Every MCP server in use is inventoried with its publisher and version. A server that changes hands or behavior after approval is flagged instead of trusted.

  • Interrogate

    Questioned in a sandbox with no network and planted canaries, a server that tries to send data somewhere it was not asked to is recorded doing it and reaches nothing.

  • Govern

    An automation can quarantine a server the moment it changes after approval, and the gateway then refuses every call to it.

What to do this week

This week3 actions
  1. Remove postmark-mcp if it is installed, and review mail sent through it.
  2. Install MCP servers only from their vendor’s own repository or registry entry.
  3. Pin MCP server versions, and review each update like a code change.
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