No fluff. Just the config that works.
Executive Summary
Objective: Separate fact from claim in the reported JPMorgan Chase data leak by the n0n extortion group, and give defenders a short list of controls that matter for this kind of exposure.
Target audience: SOC analysts, security engineers, and IT leaders at financial institutions and their vendors, plus anyone who has to answer “are we affected?” from leadership this week.
Bottom line: The JPMorgan Chase data leak is a real claim posted by a real, active extortion group, and researchers did see leaked data. What is not confirmed is that JPMorgan itself was breached. The dump is small (about 502KB), contains contact data rather than credentials or account numbers, and every signal so far points to a third-party marketing or card-program provider. JPMorgan has not commented on the claim. Treat it as a targeted-phishing risk, not a core banking compromise.
What Happened in the JPMorgan Chase Data Leak
On November 16, 2026, n0n listed JPMorgan Chase (along with Visa and Mastercard) on its dark web leak site with a 48-hour countdown. Breach trackers logged the JPMorgan listing on November 17. When the timer ran out, the group published data it says came from the bank.
Cybernews researchers reviewed the dump and reported:
- About 16,000 customer email addresses, some with phone numbers, tied to the J.P. Morgan Reserve card program
- JPMorgan Chase account IDs
- 124 bank employee email addresses
- Total size of roughly 502KB, and it is unclear whether this is a sample or the full haul
n0n’s own description claimed engagement data from marketing campaigns, a member directory with membership tiers and postal codes, and branded marketing emails. That profile reads like a marketing or loyalty platform export, not a pull from a core banking system.
Confirmed vs. Claimed
| Item | Status | Basis |
|---|---|---|
| n0n is a real, active extortion group | Confirmed | Tracked by SOCRadar, Fortra, WatchGuard and others since mid-September 2026 |
| n0n listed JPMorgan Chase on its leak site | Confirmed | Breach trackers logged the claim on November 17, 2026 |
| Data was published after the countdown | Confirmed | Cybernews researchers reviewed the dump |
| Dump contains Reserve program emails and 124 employee emails | Reported | Cybernews analysis only, no second independent review found |
| JPMorgan’s own systems were breached | Not confirmed | JPMorgan has not commented; researchers believe the data came from a third party |
| Visa says the incident came from a third-party provider in Asia Pacific | Reported | Statement relayed by Cybernews, not found on Visa’s own channels |
| The November 16 Chase outage was caused by this attack | False | Chase, its spokesperson and multiple outlets reported a software bug in on-premise hardware |
The Outage Is a Separate Story
The timing invites a connection, but the evidence does not support one. On November 16, Chase had a nationwide disruption that slowed transfers and Zelle payments. The bank said on X that it was a software bug in on-premise hardware systems with no evidence of a cyber link, and a spokesperson repeated that it was not cyber-related. Do not let anyone in your org merge these two events into “JPMorgan got hacked and went down.”
Who n0n Is
n0n (that is a zero) appeared in mid-September 2026 and runs a pure data-theft and extortion model: no file encryption, just exfiltration, a countdown timer on the leak site, and a threat to publish. It has claimed a very high volume of victims, including 38 maritime and logistics organizations added in a single batch in October.
The pattern worth noting is the entry point. In the Expedia case, Expedia confirmed attackers came in through a third-party data platform provider, and researchers tied the intrusion to a stolen Qubole vendor key. A marketing-platform source for the JPMorgan data would fit the same playbook: hit the vendor, name the big brand.
Why It Still Matters
Small and credential-free does not mean harmless.
- Reserve cardholders are high-value targets. The J.P. Morgan Reserve card is invitation-only and generally requires about $10 million in assets with J.P. Morgan Private Bank. A list of those cardholders’ emails and phone numbers is a ready-made whaling target list.
- Employee addresses enable pretexting. 124 employee emails are enough for spear-phishing, credential stuffing, help desk impersonation, and business email compromise. One successful lure can become internal access.
- Branded marketing templates make lures convincing. If the claimed marketing emails are real, attackers have genuine layouts to copy.
- Regulatory exposure is likely limited. Breach notification laws usually require credentials, Social Security numbers, or financial account numbers. That limits disclosure pressure, which also means affected people may never get a notice.
What Defenders Should Do This Week
1. Check your own mail authentication
Goal: Make sure attackers cannot spoof your domain in a lure built from this data.
Action: Confirm you publish an enforcing DMARC policy and a tight SPF record.
dig +short TXT _dmarc.<your-domain>
dig +short TXT <your-domain> | grep -i spf
Expected result: A DMARC record with p=quarantine or p=reject, and an SPF record that ends in -all or ~all with only the senders you actually use.
2. Tighten help desk identity verification
Goal: Close the help desk impersonation path.
Action: Require a callback to a number already on file, or a verified MFA push, before any password reset, MFA re-enrollment, or new device registration. No resets based on caller ID or knowledge questions alone.
3. Move high-risk users to phishing-resistant MFA
Goal: Neutralize credential phishing against executives, finance, and help desk staff.
Action: Prioritize FIDO2 security keys or passkeys for those groups. Push-only MFA without number matching is the weak spot that BEC crews hunt for.
4. Ask your marketing vendors the hard questions
Goal: Find out whether your own customer lists sit in the same kind of platform.
Action: For every vendor that holds customer contact or engagement data, ask how API keys and service credentials are stored and rotated, whether access is scoped per client, and when they last audited third-party access to their own platform.
5. Brief users with a concrete example
Goal: Turn a headline into a usable warning.
Action: Send a short note to staff and, if you serve wealthy clients, to relationship managers: expect polished, branded emails or calls that reference real card or membership details, and verify through a known channel before acting.
Troubleshooting and Gotchas
Gotcha 1: A leak site listing is not proof of a breach. Extortion groups inflate, recycle, and misattribute data. Fix: wait for a victim statement, an independent sample review, or a regulator filing before you tell leadership a company was breached. Use “claimed” until then.
Gotcha 2: Outage plus leak claim does not equal causation. The Chase outage and the n0n claim landed in the same week, which is exactly when bad takes spread. Fix: tie each event to its own primary source and keep them separate in any internal briefing.
Gotcha 3: Your DMARC record exists but does nothing. A policy of p=none only reports; it does not block spoofed mail. Diagnose with the dig command above. Fix: review your DMARC aggregate reports, authorize your legitimate senders, then step up to p=quarantine and finally p=reject.
Sources
- Cybernews: JPMorgan Chase data leak by the n0n gang
- Breachsense: JPMorgan Chase and Co. data breach claim listing
- Al Jazeera: What caused the Chase outage and Zelle payment delays
- Atlanta News First: Chase spokesperson says outage was not cyber-related
- SOCRadar: n0n claim against Expedia Group and group profile
- Fortra: What is n0n?
- WatchGuard Ransomware Tracker: n0n
- The Register: n0n operator spent $7K on AI services in extortion attacks
- SC Media: Expedia confirms data breach following supply chain attack
- Daily Security Review: Expedia confirms supply-chain breach as n0n claims 1B records
- Wikipedia: J.P. Morgan Reserve Card
- Johnny Jet: J.P. Morgan Reserve Card eligibility