Skip to main content
Mallory
← Back to News
package-repository-poisoningai-platform-securitydata-exfiltration-methodidentity-impersonation-fraud

GitHub Tightens npm Protections After Malicious MCP Package Exposed Email Data

Supply Chain Risk · 2 sources · Updated 4mo ago · First seen Jan 1, 2026

GitHub Tightens npm Protections After Malicious MCP Package Exposed Email Data

GitHub announced a broader plan to harden the npm supply chain as a malicious package on the registry highlighted how attackers can abuse trust in emerging AI tooling. The package, postmark-mcp, impersonated or reposted a legitimate Model Context Protocol (MCP) server for the Postmark email service and later introduced a subtle payload rather than overt malware, underscoring the risk of seemingly benign packages in public repositories.

According to reporting on the incident, the malicious MCP package silently added a BCC recipient to emails sent through an AI agent, potentially leaking password resets, security alerts, receipts, and other sensitive messages to an attacker-controlled address. The case was described as a software supply-chain attack adapted to the MCP ecosystem, and recommendations focused on using official MCP servers from trusted sources, enforcing least privilege and authentication, reviewing code, and strengthening package verification as npm security controls evolve.

Does this reach your builds?Trace attribution and downstream blast radius.
Trace the chain
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

2 events · Sep 23, 2025 – Jan 1, 2026
  1. Jan 1, 202611mo ago

    Malicious postmark-mcp package discovered on npm

    A malicious npm package named postmark-mcp was identified as impersonating or reposting a legitimate MCP server for the Postmark email service. The package later introduced a subtle payload that added a BCC recipient to emails sent through an AI agent, potentially exposing sensitive messages to an attacker-controlled address.

    So the first malicious MCP server has been found on npm, what does this mean for MCP security? | Semgrep
  2. Sep 23, 20251y ago

    GitHub announces plan to strengthen npm supply-chain security

    GitHub published a plan for a more secure npm supply chain, outlining security changes for the npm ecosystem. The announcement marks a formal response to supply-chain risk in the package registry.

    Our plan for a more secure npm supply chain - The GitHub Blog
Linked entities

Related entities

Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.

Open in app →

Organizations

1 linked
Postmark
Do you run this?See attribution and downstream blast radius, and whether this package or vendor reaches your builds.
Trace the Supply Chain
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.