Subscribe
Cybersecurity

Qubole named as suspected vendor behind the Visa, Mastercard and JPMorgan data leak

Saturday, November 21, 2026 · 6 min read

Ransomware group n0n claims it stole 53.9 GB across 30,743 files from cloud analytics firm Qubole, then used compromised Qubole credentials to reach customers' AWS environments — and JPMorgan confirmed the breach in a post on X on Nov. 19.

Bearish$V$MA$JPM

📊 Scorecard: our Bearish call on $V is scored from $401.87, the last close before it ran. Its first result comes after the next close.

Qubole named as suspected vendor behind the Visa, Mastercard and JPMorgan data leak

The News

The leak of customer data from Visa, Mastercard and JPMorgan Chase, first reported on Nov. 19, now has a suspected source. New reporting names Qubole, a cloud data-analytics company owned by Idera, as the third-party vendor the ransomware group n0n claims to have broken into. The group claimed an intrusion at Qubole on Nov. 11, and says that between Oct. 14 and 26 its hackers used compromised Qubole credentials to get into customers' AWS environments — Amazon's cloud computing service — through IAM roles, the permission settings companies had configured to let Qubole work with their data. In plain terms, the attackers did not break into the banks directly; they used a vendor's key to walk in through a door the banks had opened for that vendor.

The scale of what the group claims to hold is large, and it is the group's own claim, not a verified fact. N0n says it stole 53.9 GB across 30,743 files directly from Qubole — including customer contracts, pricing records, staff and trial-user information and production data — and claims to hold nearly a petabyte of data from Qubole's customer networks. A petabyte is about a thousand terabytes, an enormous amount of data. The group leaked the claimed Chase, Visa and Mastercard data on its extortion site on Nov. 16. The Qubole link itself is unconfirmed, and Reuters reviewed the posted data and could not verify it; its reporting describes more than 16,000 JPMorgan customer email addresses and about 124 bank employee addresses in the dataset.

The companies have confirmed pieces of the story. JPMorgan confirmed the breach in a post on X on Nov. 19, saying attackers accessed marketing data that may include customer names and email addresses, and that the incident is unrelated to a service disruption earlier in the week, which it attributes to a software bug. Visa confirmed an incident at a third-party provider in Asia-Pacific with no card numbers affected. Mastercard confirmed a limited exposure of email addresses from a subset of cardholders in one benefit program, and said it was contained. This post covers the Qubole identification, the credential and IAM attack path, and JPMorgan's X confirmation; the Nov. 20 post covered the original leak report and the companies' confirmations.

The breach was not at the banks — it was at a vendor the banks trusted with a key to their cloud.

Why It Matters

The attack path is the lesson here. The banks' own systems were not the entry point — a vendor's credentials were. Companies routinely give outside vendors permission to access their cloud environments so the vendor can do its job, and those permissions are only as safe as the vendor's own security. When a vendor is breached, the attacker's stolen credentials work exactly like the vendor's legitimate ones, which is why the hackers could reach customer environments across three of the biggest names in payments and banking.

The numbers also show how hard it is to judge a leak from the outside. The group's 53.9 GB and nearly-a-petabyte claims are its own, and Reuters could not verify the posted data. The companies' own statements are narrower: marketing data and email addresses, not card numbers or account details. That gap matters, because the difference between exposed email addresses and exposed card numbers is the difference between a spam and phishing risk and a direct financial one. Until more is confirmed, the honest reading is that the breach is real and the scale is unproven.

For the banks and card networks, the reputational damage is already done even if the financial damage is limited. Customers do not distinguish between a breach at a bank and a breach at a vendor the bank chose — they see their email address in a leak and blame the brand they know. JPMorgan's decision to confirm the breach publicly on X, and to separate it from the week's service disruption, is an attempt to control that narrative before the leak site does it for them.

Analyst's Take

Our call is Bearish. A vendor breach that reaches the customer data of JPMorgan, Visa and Mastercard at once is a bad look for all three, even if the confirmed exposure is limited to names and email addresses. The incident exposes a structural weakness — third-party access — that no single company's security budget can fix on its own, and it hands regulators and customers a fresh reason to ask how vendors are vetted.

What to watch next is whether the Qubole link is confirmed and whether the leaked data is authenticated by anyone other than the group claiming it. If the nearly-a-petabyte claim turns out to be real, the exposure could be far wider than the three named companies, since Qubole serves other customers too. If it does not, the story becomes a narrower, contained incident — but one that still cost three financial giants a week of bad headlines.

For investors, the near-term question is whether this becomes a compliance and vendor-management cost story rather than a fraud story. Email addresses feed phishing attacks, and phishing is the most common way financial fraud starts, so the downstream risk is real even without card numbers. Reader poll: Do you trust third-party vendors with your data — yes or no? Vote: Yes, mostly, No, not really, Depends on the vendor.

Are you bullish or bearish on this story?

By The Numbers

53.9 GBData the n0n group claims it stole directly from Qubole
30,743Files the group claims it stole from Qubole
~1 PBData the group claims to hold from Qubole's customer networks
>16,000JPMorgan customer email addresses in the dataset, per Reuters reporting
~124Bank employee email addresses in the dataset, per Reuters reporting
Oct. 14–26Window when hackers used compromised Qubole credentials to access customer AWS environments

FAQ

What is a ransomware group?

A ransomware group is a criminal organisation that breaks into computer systems, steals or encrypts data, and demands payment — usually in cryptocurrency — to return it or not publish it. Groups like n0n also run extortion sites where they post stolen data to pressure victims into paying.

What is an IAM role?

IAM stands for Identity and Access Management, Amazon's system for controlling who can do what inside its AWS cloud. An IAM role is a set of permissions a company grants to a service or vendor — in this case, Qubole — so it can access specific data. If the vendor's credentials are stolen, the attacker inherits those same permissions.

What is AWS?

AWS, Amazon Web Services, is Amazon's cloud computing platform, where companies rent servers, storage and databases instead of owning their own hardware. Many banks and payment companies store and process data there, and give vendors like Qubole controlled access to it.

What is an extortion site?

An extortion site is a website run by a ransomware group where it publishes data stolen from victims who refuse to pay. The threat of publication is the leverage: the group posts a sample, then promises to release more unless the victim pays.

👁

Source: BleepingComputer

Get the daily briefing. AI news with a markets lens — tickers, bullish/bearish reads, zero hype. Subscribe free on Substack

More on $V

All $V coverage →

More from AI Agent Update