Malicious npm Package postmark-mcp Exfiltrates User Emails via Hidden BCC
11 sources · Updated 5mo ago · First seen Sep 25, 2025

A malicious version of the npm package postmark-mcp, designed to act as a Model Context Protocol (MCP) server for AI assistants to send emails through the Postmark service, was discovered to be exfiltrating user emails by surreptitiously adding a blind carbon copy (BCC) to an external domain. The package, which appeared to be a legitimate port of the official Postmark MCP server, was published on npm and underwent rapid version iterations between September 15 and September 17, 2025. According to security researchers, the malicious behavior was introduced in version 1.0.16, which added a single line of code to forward all outbound emails to an external address at giftshop[.]club, controlled by the package's developer. This backdoor persisted in subsequent versions, including 1.0.18, and was not present in earlier releases. The package was downloaded approximately 1,500 times during the week it was available, potentially exposing thousands of sensitive emails, including password resets, two-factor authentication codes, financial information, and customer communications. The malicious package was a near-identical replica of the authentic GitHub project, making it difficult for users to distinguish between the legitimate and compromised versions. The abrupt removal of all third-party dependencies in version 1.0.18 suggested attempts to evade detection or launder the package's history. MCP servers typically operate with high trust and broad permissions, meaning any compromise can have significant security implications for organizations relying on agentic workflows. Security experts recommend that anyone who installed or used postmark-mcp since mid-September 2025 should immediately uninstall the package, rotate any credentials that may have been exposed, and review email logs for evidence of BCC traffic to the malicious domain. The incident underscores the risks inherent in supply chain attacks, particularly when attackers impersonate trusted open-source components. The official MCP server hosted by ActiveCampaign on GitHub was not compromised, but the existence of a similarly named and described package on npm facilitated the attack. The developer responsible for the malicious package removed it from npm after the issue was publicized, but not before significant data exposure had occurred. The case highlights the need for rigorous auditing of third-party packages, especially those with access to sensitive communications. Security researchers and media outlets have called for increased vigilance and monitoring of MCP servers and similar components in AI-driven environments. The incident is notable as one of the first widely reported supply chain attacks involving a malicious MCP server targeting AI assistant workflows. Organizations are urged to audit their environments for the presence of the compromised package and to implement stricter controls over the adoption of open-source dependencies. The attack demonstrates how a single line of code in a widely used package can have far-reaching consequences for data privacy and organizational security.


