Skip to content
Security & Trust

JPMorgan says vendors were breached; leak reportedly has 16,000 Reserve emails

The bank says attackers reached marketing data held by third-party vendors. Its own services were not disrupted.

W
WebPulse Newsroom
AI-assisted · 4 min read
Share on X LinkedIn
JPMorgan says vendors were breached; leak reportedly has 16,000 Reserve emails

Graphic: WebPulse, drawn from the sourced facts in this story.

In brief
  • JPMorgan says attackers compromised third-party vendors and reached marketing data that may include some customer names and email addresses. It reports no disruption to its services.
  • A security researcher cautions that some of N0n's data appears to come from service providers, not the brands' own networks. The distinction changes how a company responds.
  • Leaders should ask which vendors hold copies of customer contact data, which fields they hold, and what the contracts require when a vendor is breached.

The data was sitting somewhere else

A bank's own network is not the only place its customer data lives. Customer details are copied into more places than the bank's own systems. JPMorgan's breach this week shows how that can happen.

JPMorgan said on X on November 19 that attackers compromised third-party vendors it uses. The bank believes they reached marketing data held by those vendors. Some customer names and email addresses may be in that data.

The bank said its services are not disrupted. Where appropriate, it will contact affected customers directly and offer complimentary credit monitoring. Chase, its consumer banking arm, posted the same statement.

JPMorgan also said the breach is unrelated to a service outage on November 16. It blamed that outage on a fault in software running on its in-house hardware.

What the leak reportedly contains

Before the bank's notice, the ransomware group N0n had added JPMorganChase, Visa and Mastercard to its data leak site. Infosecurity Magazine reports that N0n reportedly published data relating to customers of all three. The group said each organisation had missed a 48-hour payment deadline.

The Wall Street Journal reported that the leak includes personal data from thousands of customers across the three organisations. Among it are 16,000 customer email addresses tied to JPMorgan's invitation-only Reserve card program. Infosecurity Magazine notes the program usually serves clients with at least $10m in managed assets.

Reuters reported that Visa and Mastercard confirmed data breaches resulting from a third-party compromise. Visa said no payment data was affected. A Mastercard spokesperson said the exposed information was not payments data and covered a small subset of cardholders enrolled in one benefit program.

None of the compromised vendors has been named. Infosecurity Magazine says it is unknown whether the three incidents are related.

A breach of the vendor is not a break-in at the bank

Rafe Pilling, a senior director at the Sophos Counter Threat Unit, urged caution about N0n's claims. He said the group is having a "real impact". But he said that in several cases the data looks like it came from outside providers that run marketing, loyalty or concierge programs. He contrasted that with criminals breaking into the brands' own systems.

That distinction changes the response. A break-in at the bank would mean checking its systems. A break-in at a vendor means asking who else holds a copy of the customer list.

Here is the mechanism, in plain terms. A program that markets to customers or runs a card benefit needs those customers' contact details. So the details are shared with the company running the program. That company becomes a second home for the data, with its own security and its own staff.

Think of a bank vault and the mailing house that holds the client address list. The vault can be sound while the mailing house is not. The customer sees one relationship. The attacker sees two targets and picks the easier one.

The sources leave a gap here. JPMorgan's statement does not mention the Reserve program. The Wall Street Journal's 16,000 figure comes from N0n's leak. Nothing in the sources confirms whether those emails came from the vendors in the bank's notice.

Consider what follows if they did. A Reserve client gave an email address to their bank, not to a marketing vendor. If a vendor held it, that client would be exposed by a company they never dealt with. That is a reason to know where your own lists sit.

Infosecurity Magazine says N0n was first observed in September 2026. It also reports that the group has reportedly threatened victims with wiping their backups if they refuse to pay.

Questions to put to your team

The lesson here is that a customer list is only as protected as the least-defended place it was copied to. Leaders can test that with a few direct questions.

First, which vendors hold copies of customer contact data for marketing, loyalty or concierge programs? Ask for the list. If it takes weeks to produce, that is the finding.

Second, which fields does each vendor hold, and does it need all of them? A vendor that only sends offers may not need names alongside emails.

Third, what do the contracts say about notice? If a vendor is breached, how fast must it tell you, and will it name itself? In this case the vendors remain unnamed publicly.

Fourth, what happens to data when a program ends? Old campaign lists are the easiest copies to forget.

Fifth, who tells customers, and in what words? JPMorgan's statement says marketing data, names and emails, no service disruption. Customers will compare that with whatever the leak shows.

Vendor risk is often reviewed from a supplier list. This incident suggests the review should start from the data, not the supplier: what customer information has left the building, and where is it now?

Produced by the WebPulse Newsroom with AI assistance from the original reporting credited below, and checked against that source by our editorial review. How we use AI.
Original reporting: Infosecurity Magazine.