Two financial giants, a cybercriminal group’s threats and a major banking outage. But what actually happened, and what does this tell us about the growing risks of third-party security?
When Visa and JPMorgan Chase appear in the same cybersecurity headline, you know it’s going to attract attention.
After all, we’re talking about two organisations at the heart of the global financial system. Both invest heavily in cybersecurity, operate sophisticated security infrastructures and handle enormous volumes of sensitive financial information.
So, when a cybercriminal group claimed to have compromised both organisations, the headlines were understandably alarming.
But there’s a problem. A cybercriminal claiming to have breached an organisation doesn’t necessarily mean that a breach has occurred.
And in this particular case, separating the facts from the allegations is essential.
What actually happened?
On 17 November 2026, Cybernews reported that a relatively new cyber extortion group, known as n0n, had listed Visa and JPMorgan Chase on its data leak website.
The group reportedly gave both organisations 48 hours to negotiate before it would publish information it claimed to have stolen.
However, the attackers initially provided little publicly verifiable evidence about the information allegedly obtained, its volume or its sensitivity.
Both organisations were subsequently linked to the claims in media reports, but their circumstances were quite different.
Visa: A third-party security incident
Visa acknowledged awareness of the claims and confirmed that an incident involved a third-party service provider operating in the Asia-Pacific region.
Importantly, according to Visa’s statement reported by Cybernews, the company stated that its own systems had not been involved or affected and that there was no indication of payment information, including card numbers, being compromised.
Visa did not publicly identify the affected provider or disclose sufficient technical details to establish precisely how the incident occurred.
This distinction matters.
An incident involving an external service provider is not the same as attackers gaining access to Visa’s own infrastructure.
Nevertheless, it raises an important question: how much exposure can an organisation have through companies operating outside its direct security controls?
We’ll return to that shortly.
JPMorgan Chase: A cyberattack or a software problem?
The situation involving JPMorgan Chase is particularly interesting.
On 16 November, the bank experienced technical problems affecting transaction processing and some banking services.
The disruption generated considerable attention, particularly because other major organisations were experiencing technology problems around the same period.
Given the timing of n0n’s claims, it would have been easy to assume the events were connected.
However, JPMorgan Chase attributed its disruption to a software bug and stated that there was no evidence of a cyberattack.
As Reuters reported on 17 November, US officials also cautioned against attributing several recent technology outages, including JPMorgan Chase’s disruption, to cyberattacks without supporting evidence.
There is an important lesson here.
A service outage is not necessarily a cyberattack. And two events occurring around the same time do not establish a connection between them.
As of 18 November, the sources reviewed do not establish that n0n compromised JPMorgan Chase or caused its banking disruption.
Who is n0n, and what do we know about it?
n0n is a relatively new cyber extortion group, with researchers reporting activity from September 2026.
As described in SecureBlink’s threat intelligence analysis, the group uses a leak website to publicise organisations it claims to have compromised and pressure them into negotiations.
The approach is straightforward: threaten to release allegedly stolen information unless the victim responds to the group’s demands.
This reflects an important evolution in cybercrime.
Ransomware was traditionally associated with encrypting files and demanding payment for their recovery.
Today, attackers may also steal information and threaten to publish it. In some cases, extortion takes place without ransomware encryption at all.
But we need to be careful with terminology. A data-extortion claim does not, by itself, establish that ransomware was deployed, systems were encrypted or information was successfully stolen.
In the Visa and JPMorgan Chase cases, the publicly available evidence does not establish which intrusion techniques n0n may have used against the organisations, whether it directly accessed either company’s infrastructure or precisely what information it possesses.
Anything more specific would be speculation.
The real cybersecurity issue: Your security is only part of the equation
For me, the most interesting aspect of this story isn’t n0n or its threats.
It’s the third-party security question.
Large organisations spend considerable resources protecting their infrastructure. They deploy endpoint detection and response solutions, security monitoring platforms, identity management systems, network controls and incident response capabilities.
But they also depend on external organisations.
Cloud providers, software vendors, payment processors, consultants, managed service providers and countless other suppliers may have access to systems or information belonging to their customers.
And that’s where things become complicated.
Imagine an organisation with excellent internal security controls. Its privileged accounts are protected, systems are regularly patched, network traffic is monitored and employees receive security awareness training.
Now imagine that one of its suppliers stores sensitive customer information in a less secure environment.
An attacker may not need to compromise the organisation’s infrastructure at all.
Compromising the supplier could be enough to obtain valuable information.
This is one of the fundamental challenges of third-party security: you can control your own infrastructure, but you cannot exercise the same level of direct control over every organisation you depend upon.
Of course, not every supplier compromise gives attackers access to its customers’ systems. The actual exposure depends on what information, credentials, permissions and connectivity the supplier possesses.
This is also why MITRE ATT&CK identifies the abuse of trusted relationships as technique T1199. Attackers may exploit existing access relationships between organisations and their suppliers, although there is no verified evidence that this particular technique was used in the incidents discussed here.
Visa’s own research reinforces the concern
Interestingly, on 17 November, Visa published its Fall 2026 Biannual Threats Report, examining threat activity observed between January and June 2026.
The findings provide useful context for the broader discussion.
Third-party and cybercrime trends
Visa Payment Ecosystem Risk and Control, January–June 2026
| +62% Incidents involving third-party agents compared with the previous six months | ~56% Share of identified compromised payment credentials linked to third-party providers |
| >1,200% Increase in recovered payment credentials from data breaches | +19% Ransomware cases compared with the preceding six months |
Source: Visa’s Fall 2026 Biannual Threats Report. These figures describe broader payment ecosystem trends, not the specific incident involving Visa. Visa Inc.
The report also highlights how artificial intelligence is helping criminals scale and refine existing fraud techniques.
However, there is no verified evidence in the sources reviewed that AI was used in the alleged n0n incidents.
What the figures do demonstrate is that third-party exposure deserves serious attention.
A single compromised provider may hold information belonging to multiple organisations, potentially creating consequences well beyond the provider itself.
What should cybersecurity teams be doing?
Rather than simply discussing the risks, let’s consider what organisations should actually do.
1. Identify your critical third-party dependencies
Start by establishing which suppliers have access to sensitive information, privileged accounts or business-critical systems.
This should include relevant subcontractors, not just organisations with which you have direct contracts.
For each critical provider, establish what information it processes or stores, which systems and services it can access, what authentication methods and privileges it uses, and what would happen if its systems became unavailable or compromised.
A supplier inventory is only useful if it accurately reflects the organisation’s actual dependencies.
2. Review privileged access and trusted connections
Third-party access should follow least-privilege principles.
Pay particular attention to persistent administrative accounts, API credentials, service accounts, remote access connections and application permissions.
Where possible, implement phishing-resistant MFA, short-lived credentials, just-in-time privileged access and regular entitlement reviews.
A particularly useful exercise is to identify which external accounts could access sensitive systems today and determine whether that access is still necessary.
3. Monitor for unusual third-party activity
Security monitoring should not stop at your organisation’s employees.
External identities and service accounts can also generate valuable detection signals.
Consider monitoring for unusual authentication locations, unexpected privilege changes, abnormal data transfers and access outside established operational patterns.
These indicators require context. An unusual login isn’t automatically malicious, but it may justify investigation.
4. Test your ability to respond to a supplier compromise
Here’s a question worth asking your security team: if one of your critical suppliers were compromised tomorrow, how quickly could you identify and revoke every access path it has into your environment?
If the answer is unclear, you have identified a worthwhile security exercise.
Test your ability to disable external identities, rotate affected credentials, revoke application tokens, restrict connectivity and identify information potentially exposed through the supplier.
Don’t wait for a real incident to discover that nobody knows which systems a supplier can access.
5. Prepare for data theft, not just system encryption
Backups remain essential for ransomware recovery.
But restoring a system doesn’t recover information already stolen by an attacker.
Incident response plans should address data exfiltration, evidence preservation, information classification, regulatory obligations and communications with affected parties.
This is particularly important for organisations handling financial information or personal data.
For a structured approach, the NIST Cybersecurity Framework 2.0 provides guidance on managing cybersecurity risks, including supply-chain relationships and incident response.
What does this mean for Visa and JPMorgan Chase customers?
At the time of writing, the available evidence does not establish that Visa payment card numbers were exposed through the reported third-party incident.
Similarly, there is no independently verified evidence that n0n obtained JPMorgan Chase customer information.
That doesn’t mean customers should ignore cybersecurity risks, but neither should they assume their information has been stolen.
The sensible approach is to monitor account activity, enable transaction notifications, use strong authentication and remain alert to suspicious communications.
One risk worth remembering is that criminals sometimes exploit the publicity surrounding a security incident to launch phishing campaigns.
An email claiming that your card has been compromised may be fraudulent even when it references a genuine news story.
Always verify such messages through official banking applications or independently obtained contact details.
Final thoughts
The recent headlines involving Visa, JPMorgan Chase and n0n demonstrate two important realities.
The first is that cybercriminals don’t necessarily need to demonstrate a successful intrusion to generate significant attention. Publishing a well-known organisation’s name on a leak website can be enough to create uncertainty and reputational pressure.
The second, and arguably more important, is that third-party security remains a substantial challenge.
Visa has acknowledged an incident involving an external service provider while stating that its own systems were unaffected. JPMorgan Chase has attributed its banking disruption to a software bug, with no evidence that the outage was cyber-related.
We should respect those distinctions rather than turn allegations into established facts.
There are still unanswered questions about the information n0n claims to possess and the full circumstances of the Visa-related incident.
Until further evidence emerges, drawing conclusions about specific attack techniques or the extent of any data theft would be premature.
But one lesson doesn’t depend on the outcome of these investigations.
Organisations need to understand not only how well they protect their own infrastructure, but also how exposed they are through the companies they depend upon.
You may have excellent cybersecurity controls. But do you really know who has access to your systems and information, and how quickly you could revoke that access if something went wrong?
That’s a question every security leader should be able to answer.
Article verification date: 18 November 2026. The article distinguishes confirmed company statements, independent reporting and unverified criminal allegations. Further disclosures could change the assessment.

Be the first to comment