Cyber & AI intelligence
Briefs indexed3924
Issues37
Published Mondays07:30 CT
█ Ransomware MASTERCARD-N0N-RAN 2026-11-19

Mastercard: n0n Extortion Group Leaks Small, Unverified Customer Dataset

"The n0n extortion group has published data it says it stole from Mastercard. The release is far smaller than the gang threatened. Before its deadline, n0n said it would expose "campaign engagement histories for hundreds…"

The n0n extortion group has published data it says it stole from Mastercard. The release is far smaller than the gang threatened. Before its deadline, n0n said it would expose "campaign engagement histories for hundreds of thousands of cardmember interactions" along with full cardmember profiles. When the 48-hour countdown ran out, Cybernews reports that the group published about 280KB of data, roughly 2,000 entries. Cybernews researchers say the records look poorly formatted and may be test data. Mastercard has not confirmed a breach or commented on the listing, and no regulator filing has been published. The data may not come from Mastercard at all. It may come from a marketing or loyalty partner, which would fit a pattern already seen with Visa: Visa has blamed a third-party supplier for its own incident in the same n0n campaign.

What Happened

On November 16, 2026, n0n added 59 organisations from 11 countries to its leak site in a single update, according to BreachNews and the leak-site tracker Ransom-DB (cited by CyberSIXT). The list included Mastercard, Visa, JPMorgan Chase, Walmart, Procter & Gamble and Eli Lilly. BreachNews reports that 46 of those entries had been on the site since November 9 as anonymous numbered placeholders. The group then filled in company names and marked every entry "NOT PAID, EXPOSED." Each named company was given 48 hours to negotiate.

When the deadline passed, n0n posted the alleged Mastercard dataset. Cybernews and Daily Security Review both describe it as about 280KB with around 2,000 entries. Cybernews says it contains real personal information. However, records for several different people are merged into single entries, so the file does not look like a clean export from a production system.

The three card and banking companies have responded differently:

What Was Taken

What n0n threatened to release and what it actually released are very different.

What the group claimed to hold. According to the leak-site listing as reported by QPulse and Ransom-DB, the Mastercard data covers:

What the group published. About 280KB and roughly 2,000 entries. That is two orders of magnitude below the claimed volume. Aras Nazarovas, a researcher at Cybernews, told Daily Security Review that the data is likely test data rather than real customer information, and that its main use for criminals would be phishing.

None of the listings mention full card numbers, account logins or balances. BreachNews and CyberSIXT both note that the entries for the payment companies describe marketing and loyalty programme data, not payment-processing data. No one has independently confirmed that the published data is authentic or that it came from Mastercard.

Ratings of severity also vary. QPulse scored the incident "critical" (95/100) based on what the listing claimed. Ostorlab and CyberDelegate both conclude that the evidence does not show a breach of Mastercard's core systems.

Why It Matters

The most likely explanation is a breach at a supplier, not at Mastercard itself. Regional programmes, campaign engagement and premium-member bookings are the kind of data held by marketing, loyalty and concierge vendors. Visa has already said its incident started at an Asia-Pacific provider, and Daily Security Review raises the same possibility for Mastercard. Whether or not this file is genuine, the risk to cardmembers comes from those third parties.

n0n is also growing fast. CyberSIXT's timeline follows the group from its first reporting in September 2026, through claims against 38 maritime firms in October, to 93 listed victims in five weeks, as counted by SOCRadar. Ostorlab says n0n reached the top three ransomware groups by number of published victims within a month. A group trying to build a reputation has reasons to name famous brands even when it holds little data. Defenders should treat leak-site claims as claims until the data is checked.

Even a small or partly fake dataset can still cause harm. Names, emails and mobile numbers linked to an issuing bank, published while there is public concern about Visa, Mastercard and Chase, give scammers convincing material for fraud calls and phishing messages.

The Attack Technique

There is no public account of how the Mastercard-linked data was obtained. What is known about n0n's methods comes from an investigation by SOCRadar, reported by The Register. Researchers found one of the group's servers left exposed, which revealed its tools and methods:

Ostorlab adds that n0n's encryption program uses a single hardcoded AES key for each build, and two builds share the same key. That means one victim's decryptor would probably unlock another victim's files. Ostorlab also says extortion emails have come from notice@n0n-cases[.]net.

What Organizations Should Do

  1. List every vendor that holds cardmember or customer data. Include marketing, loyalty, analytics and concierge providers, especially in Asia-Pacific and the Middle East and Africa. Ask each one directly whether it has seen n0n activity or received an extortion email.
  2. Lock down remote access. Require phishing-resistant MFA, such as hardware security keys, on FortiGate SSL-VPN, RDP and WinRM, or take them off the internet. Alert on bursts of failed logins from residential IP ranges.
  3. Remove long-lived cloud keys. Replace static AWS access keys with short-lived role credentials. Remove delete permissions wherever they are not essential. Turn on S3 versioning and Object Lock so stolen keys cannot wipe out archives.
  4. Keep backups out of reach. Store backups that cannot be changed and are kept separate from production credentials. n0n deliberately goes after backups.
  5. Prepare customers for phishing. If you issue cards or run cardmember programmes, warn customers about calls, texts and emails that mention Visa, Mastercard or Chase, and remind them that you will never ask for card details or one-time codes.
  6. Check leak-site claims before acting on them. Search your environment and vendor logs for the access paths above and for mail from notice@n0n-cases[.]net. Don't treat a leak-site listing as proof of a breach, and don't dismiss it either.

Sources: Mastercard data leak: hackers publish alleged customer data Cybernews | Crim spent $7K+ on AI services in extortion attacks, then left evid... | Ransomware Group N0n Claims Data Exfiltration from Mastercard Incor... | n0n Ransomware Leaks Small Mastercard Dataset After Deadline Passes... | n0n's Claims Against Visa, Mastercard and JPMorgan: What the Eviden... | Visa Confirms Vendor Incident as N0n Lists JPMorgan Chase | Visa data breach claim: supplier blamed as n0n names 59 | Visa Confirms Supplier Incident as n0n's Data Claims Against Three...