n0n Hacking Group Visa, Mastercard Claim: What to Do Now
Payments News

Hackers Claim Visa, Mastercard and Chase Data: Merchant Next Steps

The n0n hacking group's Visa, Mastercard and Chase data claim is still unverified. Here's how merchants can prepare for phishing and card testing now.

Hands holding a smartphone as a fingertip touches the screen, releasing a stream of white email envelope icons

Photo: Pixabay

On this page 7 sections
  1. What the n0n Hacking Group Claims About Visa, Mastercard and Chase
  2. Why an Unverified Breach Claim Still Matters at Your Counter
  3. If the Data Is Real: The Fake Network and Bank Messages to Expect
  4. Tighten Card-Testing and Account-Takeover Defenses Now
  5. Train Staff to Spot Fake Visa, Mastercard and Bank Messages
  6. How to Answer Customers Who Ask Whether Their Cards Are at Risk
  7. Signals to Watch Before You Take Further Action

Key takeaways

  • As of Nov. 17, n0n's claim is unverified. Visa confirms an incident at an Asia-Pacific vendor and told Cybernews its own systems weren't involved and it has no indication card numbers were affected. Chase blames its outage on a software bug.
  • The data n0n describes (contact details, reservations, marketing records) would help scammers write convincing phishing. It wouldn't help them clone cards, so you don't need to change how you accept cards.
  • Your merchant account is run by your processor and its sponsor bank, not by Visa or Mastercard. If a message about your account claims to come from a card network, check it with your processor before you act.
  • Before a data sample appears, take 20 minutes to review your recent declines, turn on multi-factor authentication and set velocity limits in your gateway.

On Nov. 16, 2026, the threat intelligence firm Hackmanac flagged a claim by the n0n hacking group. The group says it stole customer and marketing data from Visa, Mastercard and JPMorgan Chase and will publish it unless the companies settle. As of Nov. 17, no one has independently verified the claim. Visa says it did have a security incident, but at a third-party service provider in the Asia-Pacific region. A Visa spokesperson told Cybernews that Visa's own systems weren't involved and that there is no indication payment data such as card numbers was affected. Chase says a recent service disruption came from a software bug and that it has no evidence of a cyberattack.

For merchants, nothing changes about how you take cards today. Still, this is a good week to close the gaps scammers use whenever a breach is in the news: fake "security" emails, callers posing as the card networks, and bots testing stolen cards on your checkout.

What the n0n Hacking Group Claims About Visa, Mastercard and Chase

Hackmanac posted its alert on X on Nov. 16. It lists the data n0n says it has: cardmember profiles, personal contact details, premium travel and dining reservation records, banking associations, and marketing campaign engagement data. Hackmanac didn't put a size on the exposure and marked the claim's status as "pending verification." According to Cybernews and OODA Loop, n0n added the companies to its leak site with a 48-hour countdown to negotiate.

What the claim leaves out matters just as much. Tech writer Pasquale Pillitteri pointed out in his analysis that the claim doesn't mention card numbers, security codes, transaction records or login credentials. When he wrote it, no sample of the data had been published.

CompanyWhat n0n claimsWhat the company has said (as of Nov. 17, 2026)
VisaCustomer and marketing dataConfirmed an incident at a third-party provider in Asia Pacific; told Cybernews "Visa's systems were not involved and were not impacted" and that there is no indication payment data such as card numbers was affected
JPMorgan ChaseCustomer and marketing dataTold Cybernews there is no evidence its service disruption was a cyberattack; attributed it to a software bug
MastercardCustomer and marketing dataNo public statement in the reports we reviewed

The group is new. SecureBlink, a threat intelligence publisher, says n0n was first tracked in mid-September 2026 and tends to name victims before posting any proof. Cybernews reports that n0n also claims to have taken billions of Expedia traveler records, which hasn't been verified so far. For background on the bank and airline outages that same weekend, see our payments news roundup for November 16, 2026.

Why an Unverified Breach Claim Still Matters at Your Counter

Even if it's all real, the data n0n describes is the kind fraudsters use to make scams convincing, not the kind they use to clone a card. A name, a phone number and a record that someone has a premium card and booked dinner last month are enough to write a believable scam message.

Merchants can be targeted from both sides. Your customers may get fake fraud alerts that use your business's name. Your staff may get fake notices from "Visa," "Mastercard" or "Chase" that use the news as bait. Neither scam needs the stolen data to be real. People only need to have heard that something happened.

Card testing is a separate problem. It runs on stolen card numbers from many sources, and on its face this claim doesn't add to that supply. Still, the defenses below take an afternoon to set up and help no matter how the n0n claim turns out.

If the Data Is Real: The Fake Network and Bank Messages to Expect

Start with who actually runs your account. Your merchant agreement is with your processor and its sponsor bank. Visa and Mastercard set the rules and run the networks, but they don't manage your merchant account, your deposits or your terminal. If a message about your account claims to come from a card network, treat it as suspect until you confirm it with your processor.

Brief your team on these patterns:

  • Breach notices with a login link. "Your merchant account was affected by the recent Visa incident. Verify your details here." The link leads to a fake portal that steals your processor login.
  • Deposit account changes. An email or call, often dressed up as coming from Chase or another bank, asks you to change the account your settlements go to. If you change it, a whole batch of sales goes to the scammer.
  • Fake terminal technicians. A caller says the network is pushing an emergency security update. They talk an employee through changing terminal settings or running a "test" refund.
  • Compliance invoices. A bill for an urgent "breach assessment" or PCI fee, to be paid by wire or gift card.

n0n claims to have dining reservation records, so restaurants and bars should expect one more version. Guests may get texts that use your restaurant's name and ask them to "re-confirm" a booking or pay a deposit through a link. You can't stop those texts, but you can tell guests how you actually contact them.

Tighten Card-Testing and Account-Takeover Defenses Now

In card testing, a fraudster runs batches of stolen card numbers through a live checkout, usually for small amounts, to find out which cards still work. Online checkouts, donation pages and free-trial sign-ups are common targets. Watch for a burst of authorizations in a short time, lots of declines, changing card numbers from the same IP address or device, and orders at odd hours.

Illustrative example. Say a bot sends 2,000 attempts through an online store's checkout in one night, and the processor charges that store a $0.10 authorization fee on every attempt, approved or declined. That's 2,000 × $0.10 = $200 in fees with no real sales. Now say 50 of the cards go through and the real cardholders dispute those charges later. The store then has 50 chargebacks, each with its own fee and each raising its chargeback ratio. Your actual authorization fee depends on your processor's pricing, so check your statement.

These steps fit online stores, subscription and membership businesses, and restaurants that take online orders:

  1. Limit attempts. Set velocity limits in your gateway, for example a cap on attempts per IP address, per card or per session within a set time. Add a CAPTCHA or other bot check to the payment page.
  2. Require CVV and address checks on online orders. Decide ahead of time what happens to an order when they don't match.
  3. Use 3-D Secure on riskier orders. 3-D Secure authentication has the card issuer verify the cardholder before you ship. It helps most on large orders and with new customers.
  4. Watch your declines. A jump in "do not honor," "invalid card" or "pick up card" responses is often the first sign of testing. Our guide to credit card decline codes and what each one means explains each response.
  5. Lock down your logins. Turn on multi-factor authentication for your processor portal, your gateway and any virtual terminal access. Remove former employees. Only give refund permission to staff who need it.
  6. Protect stored accounts. Subscription and membership businesses should require a fresh login or a one-time code before anyone can change the card on file, email address or shipping address. Account takeover often starts with a password reset sent to an email address the fraudster controls.

If your store keys in phone orders, take a second look this month at urgent, high-value orders shipping to a new address. Keyed sales are card-not-present, like online orders, and may not get the same automatic checks your online checkout runs.

Train Staff to Spot Fake Visa, Mastercard and Bank Messages

A five-minute talk before a shift covers most of it. Keep the rules short enough for a new hire to remember:

  • Nobody changes the deposit account, terminal settings or processor login because of an email, text or call. Ever.
  • To check a message, call the number printed on your processor statement or agreement, not the number in the message.
  • No refunds to "test" a terminal. A real technician never needs one.
  • Forward anything suspicious to the owner or manager, then delete it.

Restaurants and bars should include closing managers. They handle batches and are often alone when a fake "technician" calls. Retail stores should include anyone who works a register alone on weekends.

How to Answer Customers Who Ask Whether Their Cards Are at Risk

Stick to what you know. A reasonable script: "We haven't been told of any problem with our own systems. The reports involve the card companies and one of their providers, not our store. If you're worried, check your statement and call the number on the back of your card."

Don't tell a customer their card is "safe." You don't know that, and nobody else does yet either. Our piece on what to tell customers before you know the facts of a cyber incident has more on wording.

If you email customers about this, as subscription businesses may want to, don't include links asking them to update a card or log in. A real "update your payment" email trains customers to click exactly what a phisher will send next. Instead, tell them how you do contact them and that you'll never ask for a full card number by text or email. Restaurants that take reservation deposits can post the same note on their booking page.

If you find evidence that your own systems were breached, follow a step-by-step card data breach response plan and call your processor the same day.

Signals to Watch Before You Take Further Action

The advice above applies whether the claim turns out to be true or false. These developments would be reason to do more:

  • A data sample appears. If researchers confirm published data, check whether it includes more than contact and marketing records.
  • Visa or Mastercard says more. A fuller statement from Visa, or any statement from Mastercard, would show whether merchant data was involved.
  • Your processor sends a notice. Confirm it by calling the number on your statement before you act on it.
  • Recurring declines rise. If card issuers replace cards in bulk, subscription merchants will see more "closed account" and "expired card" declines on renewals. At that point, an account updater service and a simple "update your card" page behind your customers' login make a real difference.

Today, set aside about 20 minutes. Log in to your gateway, look at the last seven days of declined transactions, and turn on multi-factor authentication if it's off. If the declines show a pattern you can't explain, or you want to talk through payment gateway options and 3-D Secure authentication, have your recent transaction report ready and contact the MannyPay team.

Sources

  1. Hackmanac on X: n0n claims Visa, Mastercard and JPMorgan Chase data (Nov. 16, 2026)
  2. Pasquale Pillitteri: n0n Group Claims Attack on Visa, Mastercard and JPMorgan Chase
  3. Cybernews: Visa Confirms Cyberattack as Hackers Claim JPMorgan Was Hit Too
  4. OODA Loop: Visa Confirms Third-Party Cyberattack as Ransomware Gang "n0n" Targets Financial Giants
  5. SecureBlink: n0n Ransomware Gang Claims Visa & JPMorgan Chase Data Breach

About the author

Adrian Reyes

Adrian Reyes is Senior Payments & Fintech Editor for Beyond the Swipe, covering credit card processing, merchant accounts, payment technology and processing fees.

This article is for general educational purposes and is not legal, tax or financial advice. Card network rules and state laws change; confirm current requirements for your business.

Related reading