CyberDelegateOfficial magazine of The CyberDiplomat

A leading platform for cyber diplomacy, cybersecurity, AI governance, critical infrastructure protection, and international digital policy cooperation.

Front pageRansomware

Ransomware

Visa Confirms Supplier Incident as n0n's Data Claims Against Three Financial Giants Remain Unverified

Visa confirms a third-party incident as n0n's data-theft claims against three financial giants remain unverified. JPMorgan separately blames a software bug for its outage.

Filed
Read
6 min read
Visa Confirms Supplier Incident as n0n's Data Claims Against Three Financial Giants Remain Unverified
"Visual generated using AI"

A ransomware group's decision to name three major financial institutions on its leak site has drawn attention to the security of payment networks and the companies that support them. But the claims surrounding Visa, Mastercard and JPMorgan Chase have not established a breach of their core systems.

On 16 November 2026, the cyber-extortion group known as n0n listed all three organisations on its data-leak site, giving them a 48-hour deadline to negotiate before threatening to publish allegedly stolen information. The listing reportedly described cardmember and marketing-related records, rather than payment-processing data.

The companies' circumstances, however, are not identical. Visa acknowledged a cybersecurity incident involving an unnamed third-party service provider in the Asia-Pacific region, while saying its own systems were not involved or affected. JPMorgan Chase separately attributed a service disruption to a software bug. Mastercard was also named by the group, but no company statement specifically addressing the listing was identified in the reporting reviewed.

As of 14:00 IST on 19 November, the deadline had passed. Public reporting reviewed for this article had not independently established that the alleged Visa or JPMorgan datasets had been published or authenticated.

A Leak-Site Listing Is Not a Breach Confirmation

The n0n listing included Visa, Mastercard and JPMorgan Chase among a wider batch of organisations. According to reporting that examined the group's claims, 59 organisations were named on 16 November.

The attackers provided limited details about the Visa and Mastercard listings. The material allegedly associated with Visa was described as including member profiles, personal email addresses, mobile numbers, travel and dining bookings for premium cardmembers, and marketing campaign engagement histories.

The JPMorgan listing was more specific. It reportedly referred to engagement records for a premium Reserve programme, a member directory containing programme categories and postal codes, and marketing emails carrying the bank's branding.

These descriptions originated from the attackers' leak site. Cybernews reported that the group had not provided screenshots or samples that would allow the claimed datasets to be independently verified.

The distinction matters. A list of alleged victims is a pressure mechanism used in extortion campaigns. It does not, by itself, establish that the listed organisation was compromised, that the data is authentic or that the attacker obtained it directly from that organisation.

Visa's Supplier-Side Incident

Visa's response is the clearest confirmed development involving the three companies.

A Visa spokesperson told Cybernews that the incident originated with a third-party service provider in the Asia-Pacific region. The company stated that its own systems were neither involved nor affected and that there was no indication that payment data, including card numbers, had been compromised.

The provider has not been publicly identified, and Visa has not disclosed the precise information potentially involved or the number of affected individuals.

Crucially, Visa's statement does not establish that n0n was responsible for the supplier-side incident. The timing of the disclosure alongside the group's listing is not enough to demonstrate that the two events are connected.

That distinction should not be lost in the headlines. A supplier can experience a security incident without the payment network it serves suffering a direct compromise. At the same time, information held by external providers can create exposure for organisations and customers further along the supply chain.

Visa's own Fall 2026 Biannual Threats Report, released on 17 November, provides wider context. Covering activity from January through June 2026, it reported a 62% increase in incidents involving third-party agents compared with the preceding six-month period. Those providers were linked to approximately 56% of compromised payment credentials identified during the reporting period.

These are industry-wide observations from Visa's threat intelligence team, not statistics about the unnamed provider or evidence of n0n's involvement in the current incident.

JPMorgan's Software Disruption Is a Separate Development

JPMorgan Chase was also named on n0n's leak site on 16 November, the same day users reported problems with transaction processing.

The bank attributed the disruption to a temporary software bug in its on-premises hardware systems. A spokesperson told Reuters that there was no evidence the issue was cyber-related, and that customers could still access their accounts and funds.

The disruption also affected the processing of some transactions involving other financial institutions. JPMorgan described the issue as temporary and not systemic.

The timing attracted attention because the ransomware listing appeared shortly before reports of the outage. However, the available evidence does not establish a causal connection between the two events.

It is also important to interpret the bank's statement accurately: JPMorgan addressed the service disruption and its technical cause. That explanation does not independently authenticate or disprove the separate data-theft allegation made by n0n.

For now, the software outage and the extortion claim should remain two distinct developments.

The AI Behind n0n's Operations

The group's technical capabilities have attracted attention beyond its latest high-profile listings.

In an investigation published in November, SOCRadar described an exposed staging server associated with n0n's operators. The exposed workspace contained scripts, ransomware-related source code, infrastructure details and configuration information for an AI coding agent.

According to SOCRadar, the operators used OpenCode, an open-source AI coding agent configured to work with multiple models. Billing records indicated more than $7,216 in AI-related API spending by 22 October.

The researchers found that the agent had been used to produce and modify hundreds of scripts and assist with parts of the group's operational workflow.

This does not describe a fully autonomous ransomware operation. SOCRadar characterised the activity as human-directed, with AI supporting the operators' technical work. The reported access methods included credential attacks against FortiGate SSL-VPN appliances, weak or compromised remote-access credentials, exposed cloud keys and compromised administrative sessions.

The distinction is important because AI did not replace the group's initial access methods. The investigation instead suggests that readily available AI coding tools were being used to accelerate scripting and operational tasks within an otherwise human-controlled campaign.

A Larger Victim Count Does Not Necessarily Mean a Larger Threat

There is another reason to approach n0n's public claims carefully: the group's reported scale has been challenged by independent threat research.

Bitdefender's November 2026 Threat Debrief examined the group's exposed file server and identified evidence of inflated or duplicate victim entries. According to the report, the underlying operational data indicated just over 20 actual targets, significantly fewer than the number suggested by the group's public listings.

Bitdefender also removed 126 n0n entries from its October ransomware victim dataset, reducing its reported total for that month from 1,072 to 946.

The findings do not establish that every claim made by n0n is false, nor do they independently disprove the specific listings involving Visa, Mastercard and JPMorgan. They do, however, provide a reason to avoid treating the group's advertised victim count as a reliable measure of its actual operations.

SOCRadar's exposed-server investigation offers a complementary technical picture: the group had access to AI-assisted development tools, but its infrastructure and operational security also showed significant weaknesses.

Taken together, the research presents a more nuanced picture than the group's public image suggests. Its claims deserve investigation, but its own publicity should not be mistaken for independently established capability or impact.

The Bigger Issue Is the Data Outside the Payment Network

For us, the most important lesson is the gap between an organisation's own infrastructure and the wider ecosystem it depends on.

Payment companies and financial institutions rely on service providers for marketing, analytics, customer engagement and other supporting functions. Those providers may hold information that is sensitive even when it does not include payment credentials or direct access to transaction-processing systems.

A dataset containing customer contact details, programme membership and postal codes can still support targeted phishing and impersonation. The absence of confirmed card-number exposure does not make such information harmless.

The incident also demonstrates why organisations and readers should distinguish between an acknowledged security event, an attacker's allegation and an independently verified compromise. Those are different stages of an investigation, and reporting them as interchangeable only creates confusion.

Visa has acknowledged a supplier-side incident. JPMorgan has explained a separate software-related disruption. Mastercard and all three institutions appeared in n0n's claims, but the alleged datasets remain unverified in the public reporting reviewed by this publication.

The 48-hour deadline has passed, but the available evidence does not establish what, if anything, was subsequently published for Visa or JPMorgan.

For organisations assessing the wider risk, the question is not simply whether a prominent company appears on a leak site. It is whether the underlying data can be authenticated, where it originated, and what access the attacker actually obtained. Until those questions are answered, caution is more useful than a premature declaration of compromise.

Sources

This brief was prepared with AI assistance from the sources above and reviewed by our editors.