High severity

JPMorgan, Visa and Mastercard confirm vendor breaches after N0n extortion claims

The three firms say vendors, not their own systems, lost marketing data, while the N0n ransomware group has published files it says belong to their customers.

By Mr Elite Published 8 min read

Severity
High
Status
Reported by outlets
Sources
3
Last checked

The short version

  • JPMorgan said on X on 19 November that attackers accessed marketing data at vendors, possibly including customer names and email addresses.
  • Visa and Mastercard separately confirmed third-party incidents; Visa said no payments data was affected, Mastercard said a small subset of cardholders had email addresses exposed.
  • BleepingComputer reported that N0n claimed an attack on cloud analytics firm Qubole, suspected to be the provider; Qubole has not responded.
  • Reuters, as cited by Security Affairs, found more than 16,000 JPMorgan-related customer email addresses in the leaked files.
  • None of the three firms has named the vendors or given a total number of affected customers.

What happened

JPMorgan confirmed on 19 November 2026 that third-party vendors it uses were hit by a cyber-attack, and said attackers accessed marketing data that may include some customer names and email addresses. Infosecurity Magazine reported that the bank posted the statement on X at 13:29 GMT, and that Chase issued the same text on its own account.

The bank said services were not disrupted. It also said the incident was unrelated to an outage on 16 November, which it attributed to a software bug in its on-premise hardware systems. Where appropriate, it said, it would contact affected customers directly and offer complimentary credit monitoring.

Claims by N0n, a ransomware and extortion group first seen in September 2026, preceded the disclosure. Security Affairs reported that N0n listed JPMorgan, Visa and Mastercard on its leak site on 16 November, claiming to hold customer engagement and marketing data. BleepingComputer gives the same date for the leak of the claimed data.

Visa told BleepingComputer the incident involved a third-party provider in Asia Pacific, that its systems were not involved, and that no payments data such as card numbers was affected. Mastercard said a third-party provider had exposed a limited number of email addresses, described as non-payments information, from a small subset of cardholders in a specific benefit program. It said the exposure had been contained.

Infosecurity Magazine reported that N0n said all three firms missed a 48-hour deadline to pay, and then released more data. It cited the Wall Street Journal as saying thousands of customers' personal details were in the leak, including 16,000 email addresses tied to JPMorgan's invitation-only Reserve card program, which it described as typically reserved for clients with $10m or more in managed assets.

Why it happened

The companies have said only that vendors were attacked. JPMorgan, Visa and Mastercard have not named those vendors, explained how the attackers got in, or said how long they had access. Security Affairs noted these gaps explicitly.

BleepingComputer reported a more detailed account, which rests on N0n's claims and on reports it attributed to Sentra and Wiz. On 11 November, N0n claimed an attack on Qubole, a cloud data analytics company owned by Idera, which BleepingComputer said is suspected to be the provider. Between 14 and 26 October, the attackers allegedly used compromised Qubole credentials to reach customers' AWS environments through IAM roles, which are permission sets the customers had set up so Qubole could act inside their cloud accounts.

N0n also allegedly took 53.9 GB across 30,743 files directly from Qubole and claimed nearly one petabyte from Qubole customers' networks. BleepingComputer said it contacted Qubole and had received no response. Infosecurity Magazine noted that it is unknown whether the incidents at the three firms are related, and the companies have not confirmed that Qubole is involved.

How this kind of failure works

Large firms hand data to suppliers for marketing, loyalty schemes and analytics. The supplier then holds a copy, and its security becomes part of the firm's own risk. An attacker who cannot get through a bank's defences may find the same data at a smaller company with weaker ones.

Cloud access makes this sharper. A customer often creates a role in its cloud account that lets a vendor read data, so the vendor's tooling can run reports. If an attacker steals the vendor's credentials, the cloud provider sees a trusted party logging in, and the customer's own controls may not flag anything unusual.

Think of a bank giving a printing firm a spreadsheet of names so it can post out a card offer. The printer's office is burgled and the spreadsheet is taken. The bank's vault was never touched, yet its customers' details are in a stranger's hands.

Sophos's Rafe Pilling made this point to Infosecurity Magazine: the data appears to have come from providers running marketing, loyalty or concierge programs rather than from the brands' networks. He said that still matters to those whose data was exposed.

Who is affected

Affected people are customers whose details sat in marketing datasets at the vendors. JPMorgan says it will contact them directly. Security Affairs, citing Reuters, said the JPMorgan-related files held more than 16,000 email addresses, some with phone numbers and postal codes, plus what appeared to be 124 bank employee addresses. The Visa data reportedly held thousands of email addresses, phone numbers and campaign records, mainly in Asia Pacific.

Nobody can yet check a public list. The practical test is whether you receive a notice from your bank or card provider, particularly if you are in a Reserve program, a card benefit scheme or a Visa marketing programme in Asia Pacific. Mastercard says only a small subset of cardholders in one benefit program is affected.

The companies say no card numbers or account credentials were exposed. Even so, names, emails and phone numbers let criminals write convincing phishing messages that mention a real banking relationship. Security Affairs made the same point. High-net-worth clients are an obvious target for tailored fraud.

How to defend against it

Tick each step as you check it. Your progress is saved on this device.

What to learn from this

The concept: Third-party (supply chain) risk

Your security is limited by the weakest organisation that holds your data or has access to your systems. Contracts and questionnaires state what a supplier promises. They do not show what the supplier does.

This pattern appears wherever access is delegated: a payroll provider with employee records, an IT contractor with admin rights, or a software tool with a token into your cloud account. In each case an attacker targets the intermediary and inherits its trust.

The defence is to reduce what any supplier can see and do, and to watch how that access is used.

Data you hand to a supplier is still your risk, so limit what you share and watch how suppliers use their access.

Quick check

Sign in to earn 10 XP for a right answer

A bank's own network was not breached, yet customer emails leaked. What most likely explains this?

Timeline

  1. 14 to 26 October 2026 BleepingComputer reported that attackers allegedly used compromised Qubole credentials to reach customers' AWS environments through IAM roles.
  2. 11 November 2026 N0n claimed responsibility for an attack on Qubole, suspected to be the third-party provider.
  3. 16 November 2026 N0n listed JPMorgan, Visa and Mastercard on its leak site; JPMorgan had an unrelated outage caused by a software bug.
  4. 19 November 2026, 13:29 GMT JPMorgan confirmed on X that third-party vendors were attacked and marketing data may have been accessed.
  5. After 19 November 2026 Infosecurity Magazine reported N0n said the firms missed a 48-hour deadline and released more customer data.
  6. 20 November 2026 Visa and Mastercard statements published, describing limited third-party incidents without payments data exposure.

What is not known yet

  • The identity of the vendors affected has not been confirmed by JPMorgan, Visa or Mastercard.
  • Whether Qubole is the common provider is unconfirmed, and Qubole has not responded to BleepingComputer.
  • The total number of affected customers has not been disclosed.
  • It is unknown whether the three incidents are linked, as Infosecurity Magazine noted.
  • Whether the leaked files are authentic and complete has not been independently confirmed.

Questions people ask

Was JPMorgan hacked?

JPMorgan says third-party vendors were attacked and that attackers accessed marketing data they held. It has not reported a breach of its own systems, and says services were not disrupted. Sophos's Rafe Pilling cautioned that the data appears to come from providers rather than the brands' networks.

Were card numbers or passwords exposed?

Visa said no payments data such as card numbers was affected, and Mastercard said the exposed information was non-payments data. JPMorgan said the data may include customer names and email addresses. None of the companies has reported passwords being exposed.

Who is the N0n ransomware group?

Infosecurity Magazine described N0n as a relatively new group, first seen in September 2026. Security Affairs said it has listed roughly 200 alleged victims on its leak site. It has reportedly threatened to destroy victims' backup infrastructure if they do not pay.

How do I know if my data was exposed?

JPMorgan says it will contact affected customers directly, and Mastercard says it is working with its provider to support affected cardholders. There is no public lookup. Be cautious with messages claiming to come from your bank, and verify them through official channels.

Sources

  • Infosecurity Magazine: JPMorgan Confirms Customer Data Breach Following Third-Party Compromise
  • BleepingComputer: Vendor data breach exposes Chase, Visa, Mastercard customer info
  • Security Affairs: JPMorgan, Visa and Mastercard Report Third-Party Data Breaches After N0n Claims

Know someone who should see this?

Keep reading