A ransomware and extortion group called n0n posted stolen data from JPMorgan Chase, Visa, and Mastercard on the dark web after a 48-hour ransom deadline expired. The largest set appears to be JPMorgan Chase customer contact data: roughly 16,000 email addresses, some phone numbers, and account identifiers, according to reporting on the leak. No payment card numbers or transaction data were exposed.

The group listed the three companies as victims on November 16 and published the files after the deadline passed. JPMorgan said its own systems were not breached and that the data came from third-party vendors. Visa and Mastercard gave similar accounts, describing small sets of non-payment information from providers and programs.

What was leaked

The JPMorgan data covers about 16,000 customer email addresses, some phone numbers, JPMorgan account identifiers, and 124 bank employee email addresses, for a total of about 502 kilobytes. Researchers at Cybernews said the records appear to be tied to Chase's invitation-only Reserve Visa card, a product for customers with roughly $10 million or more in assets under management.

That detail matters for the risk assessment. A list of Reserve cardholders is a list of affluent customers, and the contact data is exactly what a phishing campaign needs. The leaked set does not include card numbers or passwords, so it cannot be used to make a fraudulent purchase directly. It can be used to craft a message that looks credible to a high-value customer.

Visa confirmed that a third-party provider in the Asia-Pacific region was affected, with data on more than 6,000 premium cardholders. Mastercard confirmed limited non-payment information from a benefits program. Both companies said payment data was not exposed.

What the Reserve card is

Chase's Reserve card is an invitation-only product for customers with substantial assets. The card offers travel and lifestyle benefits, and the customer list is a concentrated group of affluent households.

That is why the leak is sensitive even without payment data. A list of names, emails, and phone numbers for high-net-worth customers is valuable to anyone running a targeted phishing campaign. The attacker does not need the card number if the customer can be persuaded to provide it.

The bank's decision to offer credit monitoring reflects the risk. The monitoring helps with identity theft, and the larger risk is a convincing message that tricks a customer into granting access or making a payment.

What the companies say

JPMorgan's statement described the incident as an attack on third-party vendors that accessed certain marketing data, which may include some customer names and email addresses. The bank said its systems were not breached, that services were not disrupted, and that affected customers would be contacted and offered free credit monitoring.

The bank also said the incident was unrelated to a service outage earlier in the week, which it attributed to a software bug. That clarification matters because two unrelated technology problems in the same week can look like a pattern.

Visa and Mastercard described limited exposures through vendors and programs. Neither company reported a breach of its own network. The pattern is consistent with an attack on the marketing and benefits supply chain rather than on the card networks themselves.

The vendor problem

The leak is a case study in third-party risk. Banks and card networks use vendors for marketing, analytics, rewards, and benefits programs. Those vendors hold customer data, and their security is only as good as their contracts and their controls.

A marketing database is an attractive target because it often contains names, emails, phone numbers, and account identifiers in a form that is easy to exfiltrate. The data may not include payment credentials, and it is still valuable for phishing and account takeover attempts.

The regulatory response is likely to focus on vendor oversight. Banks are required to manage third-party risk, and a vendor breach can become a bank's problem if the contract and the monitoring were inadequate. The investigation will examine what data the vendors held, why they held it, and how it was protected.

The extortion economy

Ransomware groups have evolved from encrypting files to stealing data and threatening to publish it. The shift makes the attack profitable even when the victim has backups, because the leverage is reputational and regulatory rather than operational.

The 48-hour deadline is part of the pressure. A short window forces the victim to decide quickly, before the investigation is complete and before the board has met. The group publishes when the deadline passes, which gives the threat credibility for the next victim.

The model has a weakness: the data is often less valuable than the gang claims. A 502-kilobyte file may be a sample, not the full dataset. The group's claim of hundreds of thousands of marketing interactions may be an exaggeration. The victims and the public have to assess the claim carefully.

The gang

The n0n group emerged in September 2026 and has claimed about 200 incidents since then, including a breach at Expedia. It operates as an extortion operation: it steals data, demands payment, and publishes the data when the deadline passes.

The group's model depends on the threat of disclosure. A company that pays may keep the data out of public view, and a company that does not pay faces the leak. The model works because the data has value even when it is not payment data.

The JPMorgan leak is one of the group's highest-profile claims. The bank is one of the largest financial institutions in the world, and the Reserve card population is a concentrated group of wealthy customers. The publicity is part of the group's leverage.

The regulatory picture

Financial institutions are subject to federal and state requirements for safeguarding customer data and for reporting incidents. The Gramm-Leach-Bliley Act requires a written information security program and oversight of service providers. New York's cybersecurity regulation requires incident reporting within 72 hours and specific controls.

The question in this case is whether the vendors were properly overseen and whether the bank's contracts required the security controls the data warranted. A vendor breach does not automatically become a bank violation, and regulators will look at the diligence and the monitoring.

The SEC's disclosure rules are the other track. A public bank may have to disclose a material incident, and the determination of materiality is a judgment call. JPMorgan's statement described the incident as limited to marketing data, which is the company's assessment of materiality.

The phishing risk

The practical risk for affected customers is social engineering. An attacker who knows a customer's email address, phone number, and bank relationship can send a message that references the bank and asks the customer to verify information, click a link, or call a number.

The message may look like a security alert about the breach itself. That is a common pattern: the attacker uses news of a leak to create urgency and to persuade the customer to hand over credentials or a one-time code. A bank will not ask for a password or a one-time code in an email or a text.

Customers should treat unexpected messages about the breach as suspect, especially if they ask for personal information or direct the customer to a link. The safest path is to contact the bank using the number on the card or the bank's website, not the number in the message.

The vendor contracts

A bank's contract with a marketing vendor should specify what data the vendor can hold, how it is protected, who can access it, and when it must be deleted. It should also give the bank audit rights and require notification of a breach within a defined period.

Those clauses are only as good as the enforcement. A vendor that holds more data than it needs, or keeps it longer than the contract allows, increases the bank's exposure. The investigation will examine whether the vendors followed the terms and whether the bank checked.

The broader lesson is data minimization. A marketing program does not need a customer's full account history to send an email. A vendor that collects only what it needs is a smaller target and a smaller loss when it is breached.

What customers should do

Monitor account activity and statements for anything unfamiliar. The leaked data does not include card numbers, so a fraudulent transaction is less likely, but account takeover attempts are possible.

Watch for phishing messages that reference the breach. Do not click links in unexpected emails or texts, and do not provide credentials or codes. If a message claims to be from the bank, verify it through the bank's official channels.

Consider the credit monitoring offer if the bank provides one. It is not a cure, and it can help detect identity theft. The bank's notice will explain how to enroll.

What the leak does not mean

The leak does not mean that a customer's account was accessed, that a card was compromised, or that money was taken. It means that contact data held by a vendor was stolen and published. The distinction is important for customers who are deciding how worried to be.

It also does not mean that the bank's own security failed in the way a network breach would. The bank's statement says its systems were not breached, and the evidence in the reporting is consistent with a vendor attack. That is a different failure mode, and it is still the bank's responsibility to manage.

A contact-data breach

The JPMorgan leak is not a breach of accounts. It is a breach of contact data held by vendors, and its main risk is the phishing and social engineering that the data enables. That is a smaller risk than a payment-card breach and a real one for the customers on the list.

The incident is a reminder that the supply chain is part of the security perimeter. A bank can secure its own network and still lose data through a marketing vendor. The response has to include the vendors, their contracts, and the data they are allowed to keep. That is where the next breach will come from, and where the next fix has to start.

Primary sources

  1. Arab Times, for the leaked data types, the Reserve card connection, and the n0n group's claims.
  2. The Next Web, for the companies' statements and the vendor descriptions.
  3. Financial Advisor Magazine, for the size of the leaked JPMorgan dataset and the Cybernews analysis.