CourseAgentic AI Engineer: The Complete Course · Module 4: Model Context Protocol · part 27 of 97
Part 27 · Module 4: Model Context Protocol

Incident: An email MCP server that copied everything

7 min read·13 Oct 2026
Module 4 · Incident file · About 30 minutes

What happened

In September 2025 Koi Security reported what The Hacker News called "the first-ever instance of a malicious Model Context Protocol (MCP) server spotted in the wild" (Ravie Lakshmanan, The Hacker News, 29 September 2025). The npm package postmark-mcp let AI assistants send email through Postmark, an email delivery service. According to Koi, it "copied an official Postmark Labs library of the same name".

POSTMARK-MCP, AS THE CITED REPORTS GIVE IT before 15 versions work as described 17 Sep 2025 version 1.0.16 one line: hidden copy then Koi flags 1.0.16 publisher does not reply then package removed by the publisher 26 Sep 2025 CSO Online report Koi's estimates 29 Sep 2025 Hacker News report Postmark's statement
Fifteen honest versions (green), then one line in 1.0.16 (red) that copied every email; Koi's detection (blue) came after the release, and the package vanished before it could be reported.

CSO Online reported Koi's account: "For fifteen versions prior, postmark-mcp functioned as a legitimate tool" (Shweta Sharma, CSO Online, 26 September 2025). Version 1.0.16, released on 17 September 2025, added what The Hacker News described as "a one-line change" that forwarded every email sent through the server to an outside address by blind copy. Koi's risk engine flagged the new behaviour in 1.0.16. When Koi's researchers contacted the publisher they got no reply; the package was removed from npm "even before they could report it".

The reported cost is an estimate, not a count. The Hacker News gives 1,643 downloads in total; CSO gives about 1,500 a week. Koi's Idan Dardikman made a "conservative" guess of 3,000 to 15,000 emails per organisation per day across about 500 organisations. Postmark said: "We didn't develop, authorize, or have any involvement with the 'postmark-mcp' npm package." The advice was to remove the package, rotate credentials that may have been sent by email, and check email logs for blind copies to the reported domain.

The rest of this course is yours to keep

This course is bought on its own, once, and stays readable afterwards, including the parts added to it later.