Visa, Mastercard and JPMorgan data breach through third-party vendors, November 2026

Visa, Mastercard and JPMorgan data breach (November 19, 2026): what happened, how attackers got in and how it could have been prevented

•8 min read

The Visa, Mastercard and JPMorgan customer data breach reported on November 19, 2026 did not happen inside those companies' payment networks: according to their own spokespeople, attackers got in through outside vendors holding marketing and benefit-program data. Visa says card numbers were not affected. But customer names and email addresses may have been exposed, and that is exactly what phishers need in the week before Black Friday on November 27.

What happened

On Thursday, November 19, 2026, PYMNTS reported, citing The Wall Street Journal, that ransomware attackers had leaked data belonging to thousands of Visa, Mastercard and JPMorganChase customers. According to the same report, a ransomware group calling itself n0n claimed responsibility.

Here is what each company said, per that coverage:

  • Visa: payments data such as card numbers was not affected, and neither were Visa's own systems. The incident involved a third-party service provider in the Asia-Pacific region.
  • Mastercard: a limited amount of information from a subset of cardholders enrolled in a specific benefit program was exposed. There was no impact on its payment network or on customers' ability to use their cards.
  • JPMorgan: the attack targeted third parties that provide services to the bank. The bank believes the attackers reached marketing data that could include customer names and email addresses.

Timeline and context

DateEventSource
November 2, 2026An attack on a third-party email distribution service hits nearly 400 of its customers, including the Osaka city government, exposing roughly 77 million addresses.Check Point Research
Week of November 13–19TSMC confirms employee data leaked through a cloud provider. The attacker claims to hold 6.9 GB covering 46,000 records.Privacy Guides, Check Point
November 19, 2026The leak of Visa, Mastercard and JPMorgan customer data through vendors is reported. n0n claims the attack.PYMNTS / WSJ
November 27, 2026Black Friday: promotional email peaks, giving fake messages their best cover.Calendar

What is still unknown

As of publication, the sources we reviewed do not answer several key questions:

  • whether all three companies used one shared vendor or several different ones;
  • the exact number of people affected (the report says "thousands");
  • when the attackers got in, and how;
  • which countries the affected customers live in.

Treat with caution any more precise figure circulating on social media without an official source.

How it happened

Confirmed: the weak link was a third party

All three companies agree on one point: the attackers did not reach their payment networks or core systems. They reached outside vendors. Visa points to a provider in Asia-Pacific, Mastercard to a benefit program, JPMorgan to third parties holding marketing data. In other words, the data left from where the companies had shared it, not from where they create it.

This is not an isolated pattern. In the same two weeks, Check Point documented three similar cases. TSMC blamed its leak on an unnamed cloud provider. Maersk confirmed data theft from a legacy system inherited through an acquisition. And Osaka had more than a million email addresses exposed through an email delivery vendor. These are very different organizations with the same mechanism: the data lives outside the company, and someone else is responsible for guarding it.

How a data-leaking ransomware group operates

What follows is analysis, not a confirmed fact about this case. Ransomware groups today typically apply two kinds of pressure: they encrypt systems and, increasingly, steal copies of data and threaten to publish them. A report of leaked data and a group claiming the attack fits that extortion model. The damage no longer depends on locking up Visa's or the bank's systems. It depends on publishing whatever was taken from a supplier.

Likely entry points (not confirmed)

There is no public information on how n0n got in. These are the most common ways a vendor gets compromised, and they are worth checking in your own company:

  • Stolen or reused passwords on accounts without two-factor authentication.
  • Internet-facing systems missing security patches.
  • Forgotten or legacy systems, like the one Check Point reports at Maersk.
  • Bulk data exports (CSV files, backups) left lying around long after anyone needed them.

To be clear: this is a list of reasonable hypotheses for your own risk review, not an explanation of this incident.

Why it matters even without card numbers

A name and an email address sound harmless. But a phishing email looks real when it has three things: a name, an email address and the knowledge that this person banks with a specific bank or is enrolled in a card brand's benefit program. And Black Friday week is exactly when people expect messages from their bank and card offers.

How it could have been prevented

We do not know which control failed here. What we can lay out is which controls lower the odds of customer data leaking through a vendor, and how much effort each one takes.

1. Share the minimum with every vendor

What it is: before sending a customer list to a marketing agency, a benefits provider or an email platform, ask which fields it truly needs. Why it works: data you never shared cannot leak from someone else's server. Visa's statement that card numbers were untouched shows the value of this separation: the vendor simply did not have them. Effort: low; it is a field-by-field review of each integration.

2. A vendor inventory and data map

What it is: a living table listing every vendor, the data it receives, since when, the internal owner and how the data is deleted when the contract ends. Why it works: you cannot protect data you forgot you shared, or warn the right people in time. When a vendor reports an incident, this inventory tells you in minutes which customers and which fields are at risk. Effort: medium the first time, low to maintain.

3. Security requirements in the contract, and verified

What it is: require by contract two-factor authentication, encryption, deadlines for reporting incidents and data deletion at the end of the relationship, and ask for evidence periodically. Why it works: it turns "we trust the vendor" into obligations you can measure. Effort: medium; it needs legal input and a yearly review.

4. Pseudonymization and per-vendor identifiers

What it is: when a vendor does not need to contact the customer directly, send an internal ID instead of a name and email. Why it works: if that file leaks, the attacker only gets numbers that are useless for phishing. Effort: medium; it means adjusting the integration, which custom software development can handle without changing how the business works.

5. Canary records to detect leaks

What it is: add one or two fake contacts to every list you share, unique to each vendor and using addresses only you control. Why it works: if those addresses start receiving mail from strangers, you know that list is out and which vendor it came from. Effort: low.

6. Limited, expiring access

What it is: let vendors query data through an API with minimal permissions and keys that expire, instead of receiving full exports by email or in a shared folder. Why it works: it limits how much can be stolen at once and logs every request. Effort: medium to high, depending on how many integrations you have.

7. A communication plan ready before the incident

What it is: customer messages approved in advance, a named owner and one official channel for updates. Why it works: when emails leak, telling customers quickly that you will never ask for their password by email makes the phishing that follows less likely to work. Effort: low.

What to do today

If you run a company

  1. List every vendor that receives customer data: bulk email, CRM, agencies, loyalty programs, payment gateways.
  2. For each one, write down which fields it receives and remove the ones it does not need.
  3. Turn on two-factor authentication for every account on those platforms, starting with admin accounts.
  4. Delete old customer exports still sitting in shared folders and inboxes.
  5. Before November 27, send customers a short note on how you contact them and what you will never ask for.
  6. Check whether your online store loads third-party scripts on the checkout page: Fandango notified customers this week that card details entered on its checkout pages were stolen.

If you are a Visa, Mastercard or JPMorgan customer

  • Be suspicious of emails that mention this breach, a "refund" or a "benefit" and ask you for details or a click.
  • Log in to your bank only through its official app or by typing the address yourself.
  • Watch your card activity over the coming weeks.
  • Turn on purchase alerts and two-factor authentication for online banking.

Frequently asked questions

Were Visa or Mastercard card numbers leaked?

No, according to Visa's statement as reported by PYMNTS: card numbers and Visa's own systems were not affected. Mastercard said there was no impact on its network or on card use.

What JPMorgan customer data was exposed?

The bank believes the attackers got in through third parties that provide services to it and accessed marketing data that could include names and email addresses. The sources we reviewed do not give a number of affected customers.

Who is n0n?

It is the ransomware group that, according to the report, claimed the attack. Beyond that claim, the sources we reviewed have no confirmed information about its origin or methods.

What should I do if I get an email about this breach?

Do not click or reply. Verify any notice by opening your bank's official app or website directly, or by calling the number printed on your card.

Comments

No comments yet. Be the first to share what you think.

Leave a comment

It is never published.