JPMorgan Chase Data Breach: What Leaked, Who Is Affected and What to Do Now

JPMorgan Chase, Visa and Mastercard have all confirmed that customer data was exposed after attackers targeted outside companies that provide services to them. The disclosures, made on November 19, 2026, turned a claim on a criminal leak site into one of the biggest banking security stories of the year.

Chase says the attackers reached marketing data held by its vendors, which may include customer names and email addresses. No card numbers, passwords or Social Security numbers have been reported, and all three companies say their own systems and payment networks were not breached. But reports say the exposed records belong to some of the bank’s wealthiest customers — and that makes the phishing wave that follows the real danger.

What JPMorgan Chase confirmed

JPMorgan Chase, the largest bank in the United States, announced the incident in a post on X on Thursday, November 19: third parties providing services to the firm were targeted in a cyberattack, and attackers accessed marketing data held by those vendors, which may include some customer names and email addresses.

The bank named no vendors, gave no number of affected customers, and did not say how the attackers got in. It did say there was no disruption to its services, and that the attack was not connected to the service problems some Chase customers had earlier the same week — an outage the bank blamed on a software bug, not on a cyberattack.

Chase also said it would contact affected customers directly where appropriate and offer support, including complimentary credit monitoring. Scammers will imitate exactly that offer — fake breach notices promising free credit monitoring are one of the oldest tricks after a real breach.

The leaked records appear to be tied to the bank’s invitation-only Reserve card programme, according to reporting by Reuters and others. The Reserve card serves some of JPMorgan’s wealthiest private banking clients — reports describe it as generally requiring more than 10 million dollars in assets under management, although JPMorgan has not confirmed which product the records involve.

What Visa and Mastercard said

Visa and Mastercard confirmed limited incidents at third-party providers the same day. Visa said the claims were associated with a provider in the Asia-Pacific region, its own systems were not involved, and no payment data such as card numbers was affected. Mastercard said a provider incident had exposed a limited number of email addresses — non-payments information — from a small subset of cardholders in one benefit programme, and that it had been contained.

Neither company named the vendor or gave a total number of affected customers. All three stressed that their core systems and payment networks were not compromised — genuinely reassuring for most cardholders, since no card numbers were in the data described so far.

But the reassurance has a limit: the leaked names, email addresses, phone numbers and account identifiers are precisely the material used to build the phishing emails, texts and calls that follow a breach. A message that greets you by name, mentions your bank and card programme, and warns of a security review is far more persuasive than a generic scam.

What the leaked files reportedly contain

The figures below come from the attackers’ claims and journalists who reviewed the posted files, not from the banks — treat them as reported, not confirmed. Reuters reviewed the files and counted more than 16,000 customer email addresses, along with about 124 bank employee email addresses, some phone numbers and postal codes. Other counts put the figure near 16,500 to 16,700 Reserve programme records, and reports mention member IDs and activity timestamps. Reuters said it could not independently verify the data.

Visa and Mastercard credit cards beside a wallet
Visa and Mastercard credit cards beside a wallet. Photo by Pixabay on Pexels.

Just as important is what has not been reported: no card numbers, no passwords and no payment data. The material appears to be marketing data held by the bank’s vendors, not the contents of customer accounts. That distinction is real, but it should not be overstated — a criminal who knows your name, email, phone number and card programme can write a message that passes most people’s suspicion test.

Who is n0n, and the suspected Qubole connection

The group claiming responsibility calls itself n0n, a ransomware and extortion operation that first appeared in September 2026. It follows the double-extortion playbook: steal data, set a deadline, publish the data if the victim does not pay. According to BleepingComputer and others, n0n listed the three companies on its leak site on November 16 with a 48-hour countdown, then published data it claimed came from them on November 19 — the same day the companies confirmed the incidents.

The group has also claimed an intrusion at Qubole, a cloud data analytics platform owned by Idera, named on November 11. Whether Qubole is the vendor behind the bank disclosures is unconfirmed, and Qubole has not publicly responded. But researchers documented a related intrusion: in a November 9 report, Wiz, working with Sentra and Mandiant, traced October 14–26 activity in which attackers used credentials from an AWS account associated with Qubole to take on roles customers had granted the vendor, including dormant ones, collecting secrets and downloading data from Amazon S3 storage.

The group claims it stole 53.9 gigabytes in 30,000 files from Qubole and holds nearly a petabyte of Qubole customer data — unverified claims. What is documented is the method: a trusted vendor’s credentials used to walk through access its own customers had granted it. That supply-chain pattern is behind many of November’s breaches.

Timeline: how the JPMorgan Chase data breach unfolded

In September 2026, n0n began operating and posting victims on its leak site. Between October 14 and 26, attackers used compromised Qubole credentials to access customer cloud environments through trusted IAM roles, per the Wiz, Sentra and Mandiant investigation. On November 9, Wiz published its report; on November 11, n0n claimed an intrusion at Qubole. On November 16, n0n listed the three companies on its leak site with a 48-hour deadline. On November 19, n0n published data it said came from the three companies, and all three confirmed incidents at third-party vendors the same day. On November 20, coverage confirmed the reported scale — more than 16,000 Chase customer email addresses — while security firms noted the claims remain unverified.

Why one vendor breach hit three financial giants

The most important fact here is not the number of email addresses: three of the largest names in finance were exposed through the same kind of weakness, at the same time, by what appears to be a single campaign. Banks spend billions on their own security, and by all accounts their systems held. But a modern bank runs on hundreds of outside vendors — marketing firms, benefits administrators, analytics platforms and cloud providers — each holding some slice of customer data. Attackers have learned the vendor is often the easier door, and one vendor can serve many large customers at once.

November has produced a string of examples: Expedia Group confirmed on November 12 that attackers reached its systems through a compromised third-party vendor; TSMC confirmed employee data was exposed through an unnamed cloud provider; La Poste in France disclosed a breach at its Maileva subsidiary affecting 22 million people; and Maersk confirmed unauthorised access to a legacy system from an acquisition. The details differ; the shape is the same. You cannot secure your own data by choosing a secure bank, because your data does not stay inside the bank — so the defences that matter most are the ones you control yourself.

What Chase, Visa and Mastercard customers should do now

If you hold a regular Chase account or card, there is no indication you are affected. But scammers exploit breach headlines within hours, so these steps apply to everyone.

Close-up of credit and debit cards
Credit and debit cards. Photo by Towfiqu barbhuiya on Pexels.

First, verify before you respond: check any breach-related message through the Chase app or the number on the back of your card, never through links in the message itself — suspicious emails can be forwarded to phishing@chase.com. Second, never share one-time codes or passwords with anyone who contacts you. Third, refuse any request to move money to a safe account; that is a scam, every time.

Fourth, check your accounts and card activity and report anything unfamiliar right away. Fifth, confirm any credit monitoring offer is real before enrolling — enrol only through a channel Chase itself provides. Sixth, consider a credit freeze: a freeze with Equifax, Experian and TransUnion is free and stops criminals opening new credit accounts in your name. Finally, check whether your email has appeared in this or any other breach — our guide explains the free checks, including Have I Been Pwned.

What happens next

Affected Chase customers should expect direct contact and free credit monitoring, though Chase has not said when notices will go out. Visa and Mastercard have given no indication of individual notifications. The questions regulators and customers will press are which vendors were breached, how the attackers got in, how long they had access, and how many people are affected. None of the three companies has answered them yet, and the suspected Qubole connection remains unconfirmed.

For now, the practical advice is simple: treat every message about this breach as unverified until confirmed in your bank’s app, keep your one-time codes to yourself, and remember no bank will ever ask you to move your money to keep it safe.

Leave a Comment