Chase Cyber Attack: 16,000 Customer Emails Leaked — and the Phishing Wave Aimed at Your Inbox
Chase Cyber Attack: 16,000 Customer Emails Leaked — and the Phishing Wave Aimed at Your Inbox
On November 19, 2026, JPMorgan Chase admitted something banks hate admitting: criminals got hold of its customers' email addresses. Not through Chase's own systems, the bank stressed, but through third-party vendors that handle its marketing data. Hours later, the group behind it dumped the haul on the dark web. The leak is small by breach standards — a 502KB file — and that is exactly what makes it dangerous. It is not a database of passwords. It is a verified mailing list of real people, many of them very wealthy, handed to criminals who now know precisely who to email and what to pretend to be.
This is the story of what happened, what was actually taken, and what comes next for anyone whose address is in that file — including the people who will never know it is.
The 48-hour deadline that ended on the dark web
The attack played out in public, on a timetable the criminals set themselves. Here is the sequence, as reported by Cybernews, Reuters, Neowin and the bank itself:
- September 2026 — A ransomware group calling itself "n0n" first appears. Within weeks it builds one of the larger leak sites in the current ransomware scene; one threat-intelligence database counts 412 victims listed under its name.
- November 16, 2026 — N0n lists JPMorgan Chase, Visa and Mastercard on its dark-web leak site and sets a 48-hour deadline to pay.
- November 19, 2026, 13:29 GMT — JPMorgan confirms the attack publicly on X, saying third-party vendors were targeted and marketing data was accessed.
- November 19–20, 2026 — The deadline lapses. N0n dumps the stolen JPMorgan data. Neowin reports the dump on November 19 at 22:32 EST.
Two things stand out. First, the bank confirmed the incident before the dump, not after it — which means the statement was damage control for a leak it knew was coming, not a reaction to one already public. Second, the whole episode, from listing to dump, took four days. That speed is the new normal: the gap between "we are investigating" and "your data is public" has shrunk to a long weekend.
What n0n actually took: the leak, by the numbers
The file n0n published is 502KB. That size tells its own story — this is not a full customer database. It is a slice, and the slice is what makes it valuable.
- More than 16,000 customer email addresses, according to a Reuters review of the dumped data. Cybernews put the same figure at 16,000.
- Phone numbers and postal codes for some of those customers.
- JPMorgan Chase account IDs in the file.
- More than 100 bank employee email addresses — Reuters counted 124 in the data it reviewed.
- Every record traces to the Chase Reserve program, the invitation-only Visa card for clients with at least $10 million in managed assets.
That last detail changes the arithmetic of the crime. A random list of 16,000 email addresses is spam fodder. A list of 16,000 addresses that all belong to people with at least $10 million under management is a targeting file. Aras Nazarovas, a cybersecurity researcher at Cybernews, put it bluntly: essentially every person on that list "can be a lucrative target to cyber criminals." The employee emails matter for a different reason — they are the raw material for spear-phishing, credential stuffing and social-engineering attacks aimed at the bank's own staff.
What was not taken matters just as much. Chase, Visa and Mastercard all say no card payment information was exposed. The bank has not disclosed how many customers are affected in total, and the Associated Press, quoted in the Economic Times, described the exposed group as a small fraction of Chase's tens of millions of customers. The vendors that were breached have not been named. So the honest picture is this: a small, high-value slice of marketing data, taken from unnamed third parties, now public. Anyone telling you more than that right now is guessing.
What Chase said — and the two things it didn't say
The bank's statement, posted on X by both JPMorgan and Chase on November 19, reads in full:
We have learned that third parties who provide services to the firm were the target of a cyber attack. Based on our investigation so far, we believe the attackers accessed certain marketing data held by those vendors, which may include some customer names and email addresses. There is no disruption to our services. Where appropriate, we will contact affected customers directly and offer support, including complimentary credit monitoring. There is no connection to service disruption some customers experienced earlier this week.
Read it the way a security person reads it. What it confirms: vendors were hit, marketing data was accessed, names and email addresses are probably in it. What it promises: direct contact with affected customers and free credit monitoring. What it does not say: which vendors, how many customers, or how the attackers got in. The phrase "based on our investigation so far" is doing heavy lifting — it is the bank telling you the story may grow. And the final sentence, denying any connection to the week's service disruption, is there because customers were already connecting the two events themselves. They were wrong to, as the next section shows — but the bank had to say so explicitly, which tells you how loud the confusion had become.
One more thing worth noting: the statement says "third parties who provide services to the firm." That is the 2026 version of the supply-chain breach. The attackers did not have to break into JPMorgan Chase. They broke into somebody JPMorgan Chase pays to handle its marketing, and the bank's customers paid the price. Rafe Pilling, senior director of threat intelligence at Sophos, cautioned that the data "appears to have come from third-party providers running marketing, loyalty or concierge programs, rather than from the brands' own networks." That distinction matters to the bank's liability. It matters not at all to the person whose email address is now in a criminal's spreadsheet.
Visa and Mastercard were on the same list
Chase was not n0n's only target on November 16. The group listed Visa and Mastercard the same day, and both companies have since confirmed their own incidents.
Visa said it was aware of n0n's claims and that its incident originated with a third-party service provider in the Asia Pacific region. It confirmed no payment data was impacted. Mastercard said its breach affected non-payments information from a small subset of cardholders enrolled in a specific benefit program. Neither company has named the vendor or vendors involved, and it is not yet known whether the three incidents share a single compromised provider or three separate ones.
The pattern is the point. One group, three of the biggest names in American finance, one week, one method: go after the vendors, take the marketing data, threaten to publish. The banks' own networks held. Their address books did not. If you are wondering whether your email address is sitting in a vendor's marketing database right now — it almost certainly is, at a dozen companies you have never heard of, because that is how modern marketing works. The Chase leak is a reminder that your inbox is only as private as the least careful company that has ever emailed you.
The outage earlier that week was a different story
If you are a Chase customer, you may have had a confusing week: first your transactions failed, then the bank announced a cyberattack. The two events are not connected, and the bank has said so twice.
Earlier in the week, Chase customers experienced problems processing transactions. The cause was a software bug in on-premise hardware systems — the bank's own words — that also affected other banks. It was not cyber-related. US banking regulators noticed: the Treasury and the Office of the Comptroller of the Currency contacted banks within minutes of the incident being reported, to check it was contained and confirm it was not cyber-related.
That matters for two reasons. First, the bank outage that trended earlier in the week was an infrastructure failure, and treating it as part of the attack would be wrong. Second, the timing was a gift to scammers: a week when millions of Chase customers were already anxious about their accounts is exactly the week a phishing email pretending to be Chase gets opened. The attackers did not plan the outage. They did not need to. They just needed to publish their leak while everyone was already nervous.
For the wider context, this week also fits a pattern we have covered before: outages and cyber incidents keep arriving in clusters, and the scam wave that follows each one is now as predictable as the incident itself.
Why an email address is the prize
People hear "email addresses leaked" and shrug. Passwords would be worse; card numbers would be worse. An email address feels like public information — it is printed on business cards, after all. That shrug is the mistake the attackers are counting on.
A verified email address, attached to a name, a phone number, a postal code and a bank, is the starting point for the three attacks that actually cost people money:
- Spear-phishing. A generic "Your Chase account is locked" email is easy to spot. An email that addresses you by name, references the Reserve program, and arrives days after a widely reported breach is not. The leak gives the criminal the details that make the lie believable.
- Credential stuffing. The 124 employee emails are the more dangerous half of this. Attackers will try those addresses against corporate logins, VPNs and email accounts with passwords stolen in older breaches. One reused password on one employee account is a foothold inside the bank.
- Social engineering by phone and text. With a name, a phone number and the knowledge that the person banks with Chase, a caller can sound like Chase. "We are calling about the data breach" is now a true statement, which is what makes it such an effective lie.
The Reserve angle sharpens all three. These are not random consumers; they are people with at least $10 million in managed assets, which means wire-transfer fraud, investment scams and fake "private banking" outreach all become plausible at a scale a normal phishing campaign never reaches. The 502KB file is small. The average net worth of the people in it is not.
The phishing wave: what the messages will look like
The emails have almost certainly started already. Here is what to expect, based on the pattern that followed every comparable breach we have tracked, including the fraud wave during Fraud Awareness Week earlier this month.
First, the "we detected suspicious activity" email, sent to the leaked addresses, linking to a login page that is not Chase's. It will look right: the logo, the colours, the footer. The tell is the link, and the tell is always the link — hover before you click, and if the domain is not chase.com or jpmorganchase.com, delete it.
Second, the "complimentary credit monitoring" offer. Chase genuinely promised free credit monitoring to affected customers. Scammers will offer the same thing first, faster, and by email. The real offer will come through Chase's own channels to people Chase identifies as affected; a monitoring offer that arrives by unsolicited email, asking you to confirm your Social Security number or card details to enrol, is the scam version.
Third, the phone call. "This is Chase's fraud department, calling about the data breach." Chase says it will contact affected customers directly — which gives the scammers cover, because the real call and the fake call now sound identical. The defence is boring and absolute: never verify yourself to an inbound caller. Hang up, call the number on the back of your card, and ask.

And fourth, the message that does not mention Chase at all. The leaked addresses will be sold, shared and re-used for months. The phishing that cites this breach will fade; the spam, the investment scams and the "exclusive opportunity" emails sent to 16,000 verified wealthy inboxes will not. If your address is in that file, the cost is not one bad email. It is a permanently higher background level of targeting, because your address is now a verified address — proven real, proven active, proven attached to money.
The 60-second check if you're a Chase customer
There is no public lookup for this specific leak, and anyone selling you one is lying. Chase has not published a tool to check whether your address was in the file; the bank says it will contact affected customers directly. So the check is a short list of things to do, not a website to visit.
- Wait for Chase to contact you — and verify the contact. If Chase reaches out, it will be through the channels you already use with the bank. Any message about this breach that asks you to click a link, download an attachment or "confirm" account details is not the bank.
- Check your Chase account directly. Open the app or type chase.com into your browser yourself. Look for alerts, messages and any unfamiliar activity. Do not get there by clicking a link in an email about the breach.
- Turn on transaction alerts if they are off. The leaked data contains no card numbers, so the immediate financial risk is low — but alerts are free, and they are the fastest way to catch the fraud that follows a phishing success.
- Change your Chase password if you reuse it anywhere. The leak contains no passwords. But if the password on your Chase login matches a password exposed in any older breach, the employee-email lesson applies to you too. A unique password plus app-based two-factor authentication closes the easiest door.
- Run your address through a breach checker for the older leaks. Have I Been Pwned and similar services track the big historical breaches; this leak is days old and may not be listed yet. The point of the check is not this incident — it is finding out how many older breaches already have your address, because that is the list the credential-stuffing attacks draw from.
If none of that turns up anything, you are probably fine, and "probably" is the honest word. The bank has not published a full list of affected customers, and the vendors have not been named. Certainty is not on offer this week.
The inbox rule that makes the next leak boring
Here is the part nobody at a bank will tell you, because it is not their product: the damage from a leak like this depends almost entirely on which inbox the criminals got. If the address in the file is the one you use for your bank, your government services, your password resets and your tax filings, the leak hands criminals the key to your whole digital life. If the address in the file is a disposable one you used for a single signup three years ago, the leak hands them an empty room.
That is the whole argument for compartmentalising your email, and I tested the tool for it live while writing this. At 22:39 IST on November 20, I opened tempomailusa.com and it handed me a fresh address on load — aeuit74@rover.info — with a countdown reading "Expires in 29d 20h 2m 58s" and ticking down live. The counters on the page read 485,484 emails created and 609,973 messages received. No signup, no personal information, no card.
Two things in that test are worth more than the feature list. First, the "fresh" inbox was not fresh: it already contained one unread message, from support@angeion.zendesk.com, subject "Status - [www.katzprivacysettlement.com] 3166167", timestamped 01:43 AM on November 21 — hours after my visit. The address had clearly been used before and recycled, and someone else's settlement mail was sitting in it. That is the honest downside of shared disposable pools, and it is also the point: a recycled address still tells a criminal nothing about you. Second, one click on "New Inbox" created a parallel inbox instantly — toast message "New parallel inbox created & activated!", new address svhuj35@rover.info, fresh 29d 23h 59m 57s countdown, empty inbox. Free tier is $0 forever; Pro is $4.19 a month. The page's own domain counts disagree with each other (427 in one banner, 467+ and 468+ elsewhere), which is sloppy, but the inbox itself did exactly what it claimed.

So here is the rule, stated plainly. Your real inbox is for your bank, your government, your password resets and the handful of services that can genuinely hurt you. Everything else — newsletters, trials, downloads, quote requests, loyalty programs, marketing lists, the vendor who wants your email before showing you a price — gets a disposable address. That is what a disposable email address is for: not hiding, but sorting. When the next vendor gets breached — and there will be a next vendor, because the Chase attack proves the vendors are now the target — the leaked address will be one you can abandon in a click, attached to nothing that matters. The breach still happens. It just stops being your problem.
That is the only honest promise in this whole story. You cannot stop companies from losing your data. You can decide, in advance, which data they get to lose.
FAQ
Was my Chase account hacked?
No — not in the sense of someone breaking into Chase's systems. JPMorgan says attackers targeted third-party vendors and accessed marketing data held by those vendors. Chase's own systems were not described as breached, and the bank says there is no disruption to its services. Your Chase account itself was not opened by this attack.
Was my card number or account balance exposed?
According to Chase, Visa and Mastercard, no card payment information was exposed. The leaked file contains names, email addresses, phone numbers, postal codes and account IDs — enough to target you with phishing, not enough to charge your card directly. The bank has not disclosed how many customers are affected.
How do I know if my email was in the leak?
You cannot check directly. Chase has published no lookup tool for this incident, and the bank says it will contact affected customers directly. The leak is associated with the Chase Reserve program, so Reserve cardholders are the most likely group. Everyone else should treat unsolicited Chase-related emails with extra suspicion for the next few months regardless.
Did the outage earlier this week have anything to do with the attack?
No. Chase customers had trouble processing transactions earlier in the week because of a software bug in on-premise hardware systems, according to the bank. Chase has stated explicitly that the cyberattack is not connected to that service disruption, and US regulators confirmed the outage was not cyber-related.
Should I change my Chase password?
If your Chase password is unique to Chase and you have two-factor authentication on, there is no urgency from this leak — no passwords were exposed. If you reuse that password anywhere else, change it now, because the leaked email addresses will be tested against passwords from older breaches. That is the credential-stuffing risk, and a unique password closes it.
Can a temporary email address really help after a breach like this?
It helps before the next one, not after this one. A disposable address cannot remove your real address from a file that has already leaked. What it does is shrink the blast radius next time: when a vendor you signed up for with a temp address gets breached, the leaked address is one you can abandon, attached to no bank, no password reset and no identity document. Use your real inbox only for the services that can genuinely hurt you, and give everything else a disposable one.
Need a disposable temporary email?
Protect your real inbox from spam and promotional clutter instantly and free.
Received a suspicious email, text, or charge alert?
Verify whether the sender domain is disposable, spoofed, or unverified before clicking links.