The Postmark-MCP NPM Incident: What Happened, Why It Matters, and How to Hunt It Down
npm包postmark-mcp 1.0.16版本被植入后门,导致所有发送邮件被抄送至攻击者邮箱。该包已被移除,但已安装版本仍存在数据泄露风险。影响涉及数百组织。 2025-9-28 07:27:22 Author: infosecwriteups.com(查看原文) 阅读量:3 收藏

Supply-chain compromise in the npm package postmark-mcp enabled silent email exfiltration, impacting hundreds of organizations daily.

Aditya Bhatt

TL;DR status: If [email protected] shows up in your environment, treat it as compromised and follow remediation immediately. 🚨
Free Article Link

Press enter or click to view image in full size

Executive summary

On a recent disclosure, a malicious npm package published under the name postmark-mcp (an MCP connector for Postmark) contained a backdoor in release 1.0.16 that silently BCC’ed outgoing emails to an attacker-controlled address. The package was removed from the registry after discovery, but installations that already pulled that release can still be exfiltrating data. This is a textbook supply-chain compromise affecting connector tooling — high impact because these libraries handle email (tokens, password resets, invoices). 😬

Quick facts & impact statistics

  • Weekly downloads (npm): ~1.5K+ — meaning it was in active developer workflows and could be transitively included in many projects. 📥
  • Estimated impact: conservative…

文章来源: https://infosecwriteups.com/the-postmark-mcp-npm-incident-what-happened-why-it-matters-and-how-to-hunt-it-down-37431757472f?source=rss----7b722bfd1b8d---4
如有侵权请联系:admin#unsafe.sh