What the attackers say they took
The bank’s statement did not come out of nowhere. Days earlier, on November 16, 2026, an emerging ransomware outfit called n0n added J.P. Morgan to its leak site. The group claimed it had obtained access to data.
The leaked material reportedly included approximately 16,000 emails, totaling around 502 KB in size. Those emails were associated with a premium Reserve card program. Some employee communications were also in the mix.
A review of the leaked data suggested the breach likely came from a shared marketing or data platform. That points away from a direct intrusion into the bank’s core systems.
J.P. Morgan has not named the vendors involved. It has described them only as third-party service providers.
A separate outage, and a firm denial
The timing made things messier. The same day n0n posted its listing, November 16, J.P. Morgan dealt with a service outage. That outage had been attributed to a software bug.
J.P. Morgan has answered it directly: the bank denied any link between the outage and the breach.
Background: the vendor problem keeps returning
This is not J.P. Morgan’s first encounter with vendor risk. A previous incident in 2025 involved SitusAMC, an outside vendor. That episode also put third-party exposure in the spotlight for the bank and its clients.
The bank’s own security leadership has been sounding this alarm for a while. J.P. Morgan’s Chief Information Security Officer warned about third-party vulnerabilities in April 2025. The CISO has repeatedly cautioned that these weak points could have repercussions for security standards across the industry.
What this means for customers and the industry
For J.P. Morgan customers, the immediate risk looks narrow but real. Names and email addresses alone cannot drain an account. They can, however, fuel phishing campaigns.
A scammer who knows you hold a premium Reserve card can write a far more convincing fake email. Something that references your card program by name feels legitimate in a way a generic “Dear customer” message does not.
Several questions remain open. The vendors have not been publicly identified. It is unclear whether n0n will release more material, or how many customers the bank will ultimately notify. The size of the leaked sample also invites a fair question about whether attackers hold more than they have posted.
What to watch next: any formal customer notifications from J.P. Morgan, any identification of the affected service providers, and whether regulators respond with fresh attention to third-party risk. The bank’s own security chief has spent more than a year warning that the weakest link is often outside the building.