Chase, Visa, Mastercard hit by n0n third-party vendor breach
JPMorgan Chase, Visa and Mastercard say third-party marketing vendors were breached. Extortion group n0n leaked customer names, emails and phone numbers. No card or payment-network data exposed.
JPMorgan Chase, Visa, and Mastercard each disclosed on November 19 that third-party vendors were breached and some customer data exposed. All three say their own systems were not compromised. The extortion group n0n published a dataset after a 48-hour deadline expired; the breach is being read as a vendor compromise, not an attack on the banks' or networks' infrastructure. Coverage with the company statements is at SecureWorld and Decrypt; no vendor has been named publicly by any of the three.
What each company said
- JPMorgan Chase: A spokesperson said "we believe the attackers accessed certain marketing data held by those vendors," which "may include some customer names and email addresses." Chase says it will contact affected customers directly and that the incident is unrelated to its earlier service outage.
- Visa: Said the incident stemmed from a vendor operating in the Asia-Pacific region and that Visa's own systems were not involved. No payment-card data was affected.
- Mastercard: Described "a limited amount of information from a subset of cardholders enrolled in a specific benefit program," adding "there is no impact to the Mastercard payment network or the ability for people to use their cards."
What's in the leaked data
The counts below come from researchers reviewing n0n's published files, not from the companies, and it is unclear whether the files are a sample or the full haul:
- Cybernews counted roughly 16,000 customer email addresses, plus phone numbers and Chase account IDs, with the records tied to the Chase Reserve program. It also counted over 100 employee email addresses and records on more than 6,000 Visa customers.
- The JPMorgan dataset is about 502 KB.
- The Mastercard file holds about 2,000 entries, which some researchers believe may be test data.
No card numbers, authentication data, or payment-network internals appear in the reporting. The practical risk is follow-on phishing and social engineering against named individuals, using real bank and card-network branding.
Attribution
n0n made its claim on November 16 with a 48-hour deadline and published the data after it lapsed. The Wall Street Journal, citing SOCRadar, attributes the leak to n0n; JPMorgan has not confirmed the group's identity. Keep that distinction — a group's self-promotion on a leak site is a claim, not a confirmed attribution, until a company or investigator says otherwise.
Action checklist
- If you bank with Chase or hold a card in an affected program, expect targeted phishing referencing these brands; verify any message by logging in through the official app or site, never through a link.
- Never act on a call or message asking you to "confirm" account details or move money because of this breach — none of the three companies will ask for that.
- For security teams: inventory marketing, loyalty, and benefits vendors that hold customer PII, and tier them by blast radius, not just by the sensitivity of the data they hold.
- Treat third-party JavaScript and vendor account access as attack surface — restrictive
script-srcandconnect-srcCSP rules, and change-monitoring on trusted scripts, limit what a compromised marketing vendor can reach.
Context
This is the same actor Hacker Posts covered last week when n0n extorted an Expedia marketing vendor. The pattern is consistent: n0n goes after the marketing, loyalty, and benefits providers sitting one hop outside the brands everyone recognizes, then names the recognizable brand to apply pressure. For the customer, the distinction between "the bank was breached" and "the bank's marketing vendor was breached" is thin — the data ends up on the same leak site either way — but it is the difference that determines who has to fix what, and three household financial names disclosing on the same day points at a shared vendor rather than three unrelated incidents.