Research

Visa, Mastercard and JPMorgan Say a Vendor Leaked Card Program Data. Card Numbers Were Not Reported Exposed. Premium Cardholders Should Expect Phishing That Knows Their Name and Card

Visa, Mastercard and JPMorgan Say a Vendor Leaked Card Program Data. Card Numbers Were Not Reported Exposed. Premium Cardholders Should Expect Phishing That Knows Their Name and Card

If you hold a Visa, Mastercard or Chase premium card, especially an invitation-only one, expect email and text that uses your real name, your card program and your real email address. Treat it as phishing until you prove otherwise. Your bank will not ask for a card number, a one-time code or a login by email or text. If a message about your card program asks you to act, close it and call the number on the back of your card.

Do not replace your card just because of this story. None of the three companies has said card numbers were exposed. Visa says they were not. Replace the card if your bank tells you to, or if you see charges you did not make.

What to do now

Cardholders. Read every "urgent" message about your card program, your rewards, your concierge or a booking as suspect. That is exactly the data that was reported taken. Do not click links in those messages. Do not call numbers printed in them. Use the number on the card or the bank's app. Turn on transaction alerts in the app if you have not. If your bank sends a breach notice, check it by logging in to the app yourself, not through the email.

Companies. This is a vendor story, not a bank story. Marketing, loyalty and benefit-program vendors hold your customers' names, emails and program tiers, and that alone is enough to run a convincing phishing campaign against your best customers. Three things:

  1. Inventory which outside vendors hold customer data, and what fields. Marketing platforms, email service providers, loyalty and concierge programs, analytics firms. Most companies cannot answer this list from memory.
  2. Put breach notice in the contract, with a deadline in hours, not "promptly".
  3. Send vendors the minimum. A campaign tool rarely needs a phone number, a postal code and an account ID together. Every extra field you send is a field someone can leak.

Am I affected?

There is no lookup for this. No company has published a list or a checker, and you should not trust any site that claims to have one. Watch for a notice from your bank or card issuer. Glitchwire reports that Chase says it will contact affected customers and offer free credit monitoring. Until then, assume your name, email and card tier may be in the hands of people who will use them in a lure.

What the companies have said

All three statements below reached us through press reports. We could not read the original Wall Street Journal story, which is paywalled, so we used outlets that quote or paraphrase the companies.

Visa said the incident began at a third-party service provider in the Asia-Pacific region. As reported, Visa said "Visa's systems were not involved and were not impacted," and that payment information, including card numbers, was not affected. Visa did not name the provider.

JPMorgan Chase said outside vendors were attacked. A spokesperson said: "Based on our investigation so far, we believe the attackers accessed certain marketing data held by those vendors." The bank said that data may include some customer names and email addresses. It has not given a count and has not named the vendors. It said: "There is no disruption to our services."

Mastercard said, as reported, that a limited amount of information belonging to some customers enrolled in a specific benefit program was exposed. We found no direct quote with a named recipient.

The Monday outage is separate. Some Chase customers had trouble with transactions on Monday, November 16. JPMorgan said that was caused by a software bug in on-premise hardware systems and told CNBC "there is no evidence it is cyber-related." Its statement on the leak says: "There is no connection to service disruption of some customers experienced earlier this week."

What is claimed but not confirmed

Who did it. A group that calls itself n0n (also written N0n) claims the theft. The Wall Street Journal reported the claim citing the threat intelligence firm SOCRadar. That is one source chain: most outlets we read trace back to the Journal piece. None of the three companies has named n0n.

How many people. Newsweek reported about 16,000 email addresses tied to the invitation-only Chase Reserve program. BreachNews described the claim as tens of thousands of email addresses. These are the group's claims as described by the press. JPMorgan has not confirmed any count.

Which vendor. Glitchwire wrote that unnamed ransomware tracker services have linked the JPMorgan data to Qubole, a data platform provider. No company has confirmed that, and we could not find the trackers' own evidence. Treat it as an unconfirmed attribution. Other press reports describe the data as loyalty or benefit-program records. Visa's own words are only "a third-party service provider in Asia-Pacific."

One vendor or three. A researcher was quoted in early coverage saying the three datasets share file layouts, which would point at one common third party. We could not read that quote at its source, so we do not rely on it. International Business Times noted that the Journal's reporting "does not establish that all three companies suffered identical breaches or that the information came from a single compromised system." That is the honest state of it.

The pattern: one vendor, many famous names

BreachNews reports that n0n named 59 organizations across 11 countries in a single leak-site update on November 16. Naming that many big brands at once is a pattern we have seen before. It usually means a breach at a shared vendor, presented as breaches of each of the vendor's famous clients.

We checked one case of that in detail with a different group, The Gentlemen. A South African insurance software firm, MIP Holdings, disclosed an incident in June 2026. Months later the group listed several of MIP's clients as if each had been breached directly. One of them, Hollard, said the data "appears to be linked to the June 2026 cyber security incident involving MIP." The data was real. The client's own systems were not breached. Read it here: How Often Do The Gentlemen Bluff?

n0n is a different group. We present this only as the same pattern, not the same actor. Here the vendor-side exposure is real: all three companies confirm something was taken from an outside provider. What is inflated is the headline that Visa, Mastercard and JPMorgan were hacked. Their statements say their own systems were not.

For a cardholder, that difference does not matter much. A phishing email that knows your name and your card tier works just as well either way.

What we hold on n0n

We wrote about n0n on October 31, after SOCRadar published research on an operator workspace the group left exposed. We added SOCRadar's indicators to our feed then, credited to SOCRadar and labeled "not our discovery." Our corpus holds an n0n actor profile and indicators sourced from SOCRadar, plus third-party feed entries for the same leak-site domain. None of that is a lead on this incident, and none of it ties n0n to Visa, Mastercard or JPMorgan.

No primary source on this incident has published indicators. We added nothing new to the feed for it.

Sources

  • Visa, JPMorgan and Mastercard statements as quoted or paraphrased by the outlets below. The Wall Street Journal original is paywalled and we did not read it.
  • Newsweek: JPMorgan statement and the reported Reserve program count.
  • Gulf News: summary of all three companies' statements and the SOCRadar attribution, credited to the Journal.
  • International Business Times: Visa's statements to the Journal and the caveat on single-source attribution.
  • BreachNews: Visa statement, the November 16 Chase outage statement to CNBC, and the 59-organization leak-site update.
  • Glitchwire: JPMorgan statement and the unconfirmed tracker link to Qubole.
  • OODA Loop brief: Visa's confirmation that the incident began at an Asia-Pacific provider.
  • Cybernews and Quartz covered the story too. Both returned errors when we tried to read them.

We did not visit the group's leak site and did not download or view any leaked data.

Read next: n0n Spent $7,216 on AI Coding Agents and Still Broke In With Stolen Passwords, our October post on how this group gets in and the four controls that close those doors.


Every indicator in this post is in the feed. Free.

1.58M+ IOCs, STIX 2.1 / TAXII, 88% novel vs ThreatFox, exploited-CVE leads ahead of CISA. No credit card — a free API key in 30 seconds, and you can audit every claim above against the live endpoints.

Get your free key → analytics.dugganusa.com/stix/register