Visa has confirmed a third-party cyberattack in Asia Pacific, after the extortion group n0n listed the payments giant on its leak site claiming cardmember data. Visa told Cybernews its own systems were not involved and were not impacted, and there is no indication that payment data such as card numbers has been affected. The provider has not been named. n0n’s listing, discovered on 16 November 2026, claims complete cardmember profiles, premium travel and dining bookings, and more than 1.5 million cardmember interactions. Interactions are not people, no data sample has been published, and Visa has not attributed the incident to n0n. JPMorgan Chase, also named by n0n, says its outage was a software bug with no evidence of a cyberattack. Mastercard has confirmed nothing.
What Visa confirmed, and what it did not
Visa’s confirmation is narrow, and the narrowness is the story. The company told Cybernews it is aware of n0n’s claims and that the incident originated with a third-party service provider in the Asia Pacific region. Its spokesperson said: “Visa’s systems were not involved and were not impacted. There is no indication that payment data such as card numbers have been affected.” Visa has not identified which provider was hit, has not described what data was exposed, and has not said how many people are affected. None of that has been disclosed by any source read.
Two things Visa did not do matter as much as what it did. It did not attribute the incident to n0n. Visa confirmed a third-party incident and said it is aware of n0n’s claims; it did not say n0n caused the incident. And it did not confirm any of n0n’s figures. That sentence is why the “Visa cyberattack” label is misleading: the incident originated with a third-party provider, and Visa’s own systems were not involved. So the confirmed facts are these: a third-party incident in Asia Pacific, Visa’s own systems untouched, no indication card numbers were affected, and a provider that remains unnamed. Everything else is an attacker claim.
The 59-name batch is mostly unmasking
n0n is a data-theft extortion group that began listing victims on 18 September 2026. It steals data and threatens to publish it, and SOCRadar found encryptor code on a server the group left exposed. On 16 November 2026, n0n named 59 organisations on its leak site, including Eli Lilly, Visa, Mastercard, JPMorgan Chase, Walmart and Procter & Gamble. That headline number is misleading in a specific way. Of the 59, 46 had already been on the site since 9 November as numbered placeholders, such as “Company #150”. n0n swapped the numbers for names and marked all 59 as unpaid. That is 78% of the batch. Only 13 names were genuinely new. The “59 companies in one day” headline is mostly unmasking, not 59 fresh listings.
The batch breaks down, by n0n’s own descriptions, into small businesses (19), retailers (13), drug makers (11), advertising and audience-data firms (10), card programmes (3), and three others. The three card programmes are Visa, Mastercard and JPMorgan Chase. They are 5.1% of the batch. The financial giants are the headline, not the bulk. The batch is dominated by small businesses, retailers and drug makers.
The inflation runs deeper than one day. The Ransomtracker holds 363 n0n entries, 168 of them numbered placeholders. Bitdefender, working from data on the group’s own file server, says n0n targeted just over 20 victims, and it removed 126 n0n entries from its October total. n0n listed about 150 entries in October alone. 363 divided by 20 is about 18. The leak-site entry count overstates the group’s real target count by roughly 18 times. The 59-name batch should be read against that roughly 20-victim reality, not as 59 breaches. Ransomnews’s reading is that the repeating data types point to shared suppliers upstream, not 59 separate intrusions, and n0n has not named a source supplier for the 16 November batch.
The Visa third-party incident claim, item by item
The Visa listing describes cardmember programme records for a global payment network across Asia Pacific markets: complete member profiles with full names, personal email addresses and mobile numbers; travel and dining bookings for premium cardmembers, covering hotels, restaurants, cities, dates and confirmation references; and campaign engagement histories for more than one and a half million cardmember interactions. The listing was discovered on 16 November 2026 at 12:08 UTC, with an estimated attack date of 16 November, and is marked “NOT PAID — EXPOSED”. n0n set a 48-hour countdown for negotiation before a promised data leak. Cybernews reports the clock was ticking at the time of writing, with few details from the attackers about what they claim to have stolen. No ransom figure has been published, and the exact expiry was not published, so this article states no leak date or time.
The “more than one and a half million cardmember interactions” figure is n0n’s own claim. Interactions are not people. No confirmed affected-person count exists, and the figure cannot be converted into one. This article does not write “1.5 million people affected” or “1.5 million cardmembers”. It is not an affected-person count, not a record count confirmed by anyone, and not evidence of 500,000-plus victims.
The Mastercard listing describes cardmember programme records from the Middle East and Africa: names, emails, phone numbers, and travel and dining bookings, with “hundreds of thousands” of cardmember interactions claimed. It is an attacker claim only. Mastercard has not confirmed anything as of the time of writing. The JPMorgan Chase entry describes email campaign records for a premium Reserve card programme. None of the three mentions card numbers, account logins or balances. The JPMorgan entry had been on n0n’s site as “Company #150” since 9 November 2026, a full week before the 16 November Chase outage, which the bank attributes to a software bug.
The same batch carried a separate Eli Lilly claim: prescription-fill records covering 1,243,661 patients, 16 million rows, plus a prescriber file of 7.6 million NPI numbers. Those are attacker claims only, n0n does not say whether the patient records carry names, and it is a separate entry for a separate company. It is batch context only, never merged into Visa counts.
Visa confirmed in 21 hours 40 minutes. Expedia took about three days.
n0n’s Visa listing was discovered on 16 November at 12:08 UTC. Cybernews published Visa’s confirmation on 17 November at 09:48 UTC. That is a gap of 21 hours and 40 minutes. Expedia’s listing appeared on 9 November and its confirmation came on 12 November, about three days, or roughly 72 hours. Visa confirmed roughly 3.3 times faster than Expedia. One caveat: the Expedia listing’s time of day is not published, so “about three days” is approximate. The direction, Visa much faster, is robust.
Visa’s third-party incident follows the same pattern as Expedia’s case, which TechReview covered. n0n named Expedia on 9 November. Expedia told Skift on 12 November that attackers had compromised a third-party data platform provider and “used its trusted access to reach systems at multiple companies”. Expedia did not name the provider, confirm n0n’s figures, or say n0n was responsible. Skift reports researchers at Wiz and Sentra tied an October attack to credentials belonging to Qubole, a former Expedia vendor. That Qubole link belongs to the Expedia story only, and even there Expedia has not named Qubole. This article does not write “the vendor was Qubole” for Visa.
The JPMorgan outage is a different story
JPMorgan Chase told Cybernews its service disruption was caused by a software bug and that there was “no evidence” linking the incident to a cyberattack. The bank has not confirmed any connection between the outage and n0n’s claims. Ransomnews notes no link has been shown between the listing, which describes email marketing records, and the outage. The listing cannot be a reaction to the outage: it sat on n0n’s site as “Company #150” since 9 November, a full week before the 16 November outage.
This is also not connected to the 16–17 November US banks outage involving Chase, Bank of America and Wells Fargo, which TechReview covered separately. That outage was attributed to technical issues, and JPMorgan specifically says a software bug, with no evidence of a cyberattack. The banks outage and the n0n claims are separate stories, and this article does not link them.
Visa’s own report, released the same day
On the same day Visa confirmed the incident, 17 November 2026, it released its Fall 2026 Biannual Threats Report, covering threat activity from January to June 2026. The report found third-party incidents surged 62% versus the previous six months, with third-party providers linked to approximately 56% of compromised payment credentials identified in the period. Ransomware cases rose 19% over the preceding six months and 312% since 2021.
That is timing, not causation. The report covers January to June 2026 activity and says nothing about this incident. But the timing is striking: on the day Visa’s own research said third-party incidents had surged 62%, Visa confirmed a third-party incident of its own. The report’s numbers give the incident its context. The incident originated with a third-party provider, the pattern the report says surged 62% in the first half of 2026.
What happens next
Six things would change this story. Visa naming the affected provider. Any Mastercard or JPMorgan statement. Tier-1 pickup. Any published data sample. And the expiry of the 48-hour deadline, which would fall around 18 November at 12:08 UTC if counted from the 16 November listing, though the exact expiry was not published, so that time is approximate. A SEC filing would also matter, if Visa deems the incident material.
For now, the confirmed facts are narrow and the claims are wide. Visa confirmed a third-party incident in Asia Pacific, its own systems untouched, no indication card numbers were affected, and a provider still unnamed. n0n claims cardmember data for Visa, Mastercard and JPMorgan, plus 1.5 million-plus interactions, with no data sample and no proof. Only Visa has confirmed anything, and what it confirmed is a third-party incident, not a breach of its own systems. That distinction is the whole story, and it is the one to keep straight as the deadline runs.


