Claimed, Not Confirmed: What the n0n Listing of Visa and JPMorgan Really Tells Us

Mira, I saw the headline the same way you probably did. Visa and JPMorgan Chase “hit by cyberattack,” 48 hours to negotiate before the data gets dumped.

So I read past the headline. What’s on the record is smaller and, honestly, more useful for us. This isn’t a story about two giants getting kicked over. It’s about suppliers, and about how to read a leak site without letting it read you.

What actually happened

Around November 16, 2026, an extortion group calling itself n0n (written with a zero) listed Visa and JPMorgan Chase on its leak site, and Cybernews reports it set a 48 hour countdown to negotiate. Cybernews reported the listing and says the gang is giving the companies “just 48 hours to negotiate before dumping their stolen data online,” while also noting “the attackers have offered few details about what they claim to have stolen.”

That’s the claim. Now here’s what the companies said.

Visa told Cybernews it is aware of the claims and that the incident originated with a third-party service provider in the Asia Pacific region. The spokesperson’s exact words:

“Visa’s systems were not involved and were not impacted. There is no indication that payment data such as card numbers have been affected.”

Read that carefully, por favor. Visa didn’t call it a cyberattack on Visa. It didn’t name the provider, and it didn’t describe what data the provider held. And “no indication” is not the same as “ruled out.” It’s a statement about what Visa has seen so far.

JPMorgan is a separate story, and I mean separate. The bank had a consumer banking outage on November 16. Its spokesperson told CNBC it was “a temporary issue related to a software bug in on-premise hardware systems” and that “There is no evidence it is cyber-related.” JPMorgan has not confirmed any incident tied to the n0n listing. No source I’ve read connects that outage to the listing. Don’t let the timing do the thinking for you.

What the listing claims, and what it doesn’t

Everything about the supposed data comes from the attacker, relayed by outlets and trackers. Per that reporting, the Visa entry describes Asia Pacific cardmember program records, things like contact details, travel and dining bookings and campaign engagement, and claims “more than 1.5 million cardmember interactions.”

Interactions, amigos. Not people. Not cardholders. Anyone turning that into “1.5 million customers exposed” is inventing a victim count.

And no source says card numbers were taken. If someone in your family asks whether they need a new card because of this, the honest answer is that nothing on the record says so. What they should watch for is phishing that uses real booking details.

As of November 18, I haven’t found any report that data from either company was published. I’m not going to tell you when the countdown ends, because outlets disagree on when it started. Some count from November 16, and one says November 17.

How to read a leak site

A leak site is a pressure tool, and famous brand names get the most attention.

Some context on this group. Ransomnews reports n0n named 59 organisations on its leak site on November 16, including Eli Lilly, Mastercard and Walmart alongside Visa and JPMorgan, and that 46 of those had been sitting on the site since November 9 as numbered placeholders. Ransomnews also reads the repeating data types as pointing to shared suppliers upstream rather than 59 separate break-ins. That’s their reading, not a confirmed fact.

Then there’s Bitdefender. In its November 2026 threat debrief, published November 10 before this listing, Bitdefender says that “According to the data obtained from N0n’s file server, the group targeted just over 20 victims,” and that the group’s image as a potentially significant threat is “just that: a false depiction.” That doesn’t mean nothing happened to anyone. It means the number of names on the wall and the number of real intrusions are two different things.

One more check worth doing. I found no SEC Form 8-K cyber incident filing (Item 1.05) from either company on EDGAR as of November 18. I also didn’t find a CISA advisory on n0n.

Why this matters for critical infrastructure

From here on, this is my analysis, not something the sources say about this incident.

Financial services is a critical infrastructure sector. CISA lists it as one and notes that the Department of the Treasury is the Sector Risk Management Agency. We usually talk pipes, power and plants here, but payments are the plumbing everything else runs on.

And the one confirmed fact in this whole story is a supplier incident. That’s the lesson. Think of it like your house. You can have the best locks on your own doors, but if the cleaning company keeps a copy of your key on a hook in an office across town, your security now depends on their office too.

We’ve watched this movie before. CISA’s advisory on CL0P and MOVEit (AA23-158A) describes a group that “preferred to rely mostly on data exfiltration over encryption,” hitting many organizations through one piece of shared file transfer software. In 2024, the Snowflake campaign tracked by Mandiant as UNC5537 put as many as 165 organizations potentially at risk, and Snowflake “itself has not been compromised,” per CyberScoop. Attackers used stolen credentials against customer accounts without MFA.

Visa’s own Fall 2026 threats report, released November 17 and not about this incident, says incidents involving third-party agents rose 62% compared with the previous six months. It also says criminals “target third-party providers that can provide access to multiple downstream payment organizations.” The Fed’s interagency guidance on third-party relationships (SR 23-4) exists because regulators already know this path.

Same pattern we fight in OT, entiendes? The integrator with remote access, the vendor laptop, the cloud historian. Nobody reported any OT or ICS system touched here, and I’m not claiming one was.

What to do with this

  1. Inventory every third party that holds your data or your access. Marketing platforms and analytics vendors count, not just IT outsourcers.
  2. Revoke dormant vendor integrations. If a connection hasn’t been used in months, it’s a door nobody’s watching.
  3. Require MFA and network allow lists on SaaS and data platforms.
  4. Write breach notification and cooperation terms into your contracts. Your vendor should have to tell you fast.
  5. Map which suppliers serve many of your peers. One provider failing can hit a whole sector at once.
  6. Prepare your people for phishing built on real data.
  7. Before you share a breach headline, check three things. What did the company actually say, is there a filing, and has anything actually been published?

Bottom line

  • A listing is a claim. Visa confirmed a supplier incident and said its own systems were not involved, and JPMorgan’s outage is a separate, unlinked event.
  • The 1.5 million figure is “cardmember interactions” from the attacker’s listing, and no source says card numbers were taken.
  • The real risk lives in the supplier chain. Treat third-party access like it’s your own front door.

Stay sharp out there.

Javier

Sources

  1. https://cybernews.com/security/visa-jpmorgan-data-breach/
  2. https://www.cnbc.com/2026/11/16/jpmorgan-chase-technical-issue.html
  3. https://usa.visa.com/about-visa/newsroom/press-releases.releaseId.22981.html
  4. https://data.sec.gov/submissions/CIK0001403161.json
  5. https://www.cisa.gov/topics/critical-infrastructure-security-and-resilience/critical-infrastructure-sectors/financial-services-sector
  6. https://www.federalreserve.gov/supervisionreg/srletters/SR2304.htm
  7. https://www.cisa.gov/news-events/cybersecurity-advisories/aa23-158a
  8. https://cyberscoop.com/as-many-as-165-companies-potentially-exposed-in-snowflake-related-attacks-mandiant-says/
  9. https://www.bitdefender.com/en-us/blog/businessinsights/bitdefender-threat-debrief-november-2026
  10. https://ransomnews.com/n0n-eli-lilly-visa-jpmorgan-leak-site-claims-2026/

Leave a Reply