When a ransomware gang lists Visa, JPMorgan Chase, and Mastercard on the same leak site within hours of each other — with countdown timers running — the financial sector sits up and pays attention. This week, a new extortion group called n0n did exactly that, and Visa responded with an extraordinary admission: a third-party vendor in the Asia-Pacific region had been breached. For CISOs, security architects, and IT leaders across India and the broader APAC region, the implications are immediate.

Key Takeaways

  • The n0n extortion group has listed Visa, JPMorgan Chase, and Mastercard as alleged breach victims — with 48-hour data-leak deadlines.
  • Visa officially confirmed a cyberattack at a third-party vendor in the Asia-Pacific region; it says its own systems and payment card data are unaffected.
  • JPMorgan Chase says a concurrent outage was caused by a software bug with no evidence of a cyberattack; the gang’s JPMorgan claim remains unverified.
  • n0n previously confirmed a breach at Expedia (via a supplier) on November 12, establishing a pattern of supply-chain targeting.
  • Analyst reviews suggest the stolen data is likely from auxiliary marketing and analytics platforms, not core payment rails — but investigations are ongoing.
  • India-based organisations with payment partnerships, travel integrations, or marketing analytics vendors in the APAC supply chain face elevated exposure right now.

Who Is the n0n Ransomware Gang?

n0n burst onto the threat landscape in late 2026 as a data-extortion group operating a Tor-based leak site. Unlike traditional ransomware operators who encrypt files and demand a decryption ransom, n0n follows the pure-extortion model: steal data, list the victim, start a countdown clock, and threaten public exposure unless paid.

Their track record so far in November is striking. On 12 November 2026, Expedia confirmed that one of its suppliers had been breached — a claim n0n had posted first. Within days, the group listed three of the world’s largest financial institutions simultaneously: Visa Inc., Mastercard, and JPMorgan Chase. Reports also indicate Eli Lilly, the global pharmaceutical giant, was listed on the same site.

The speed and breadth of the listings suggest n0n either has access to a compromised third-party data aggregator serving multiple Fortune 500 companies, or is operating an industrialised exfiltration pipeline that processes supply-chain breaches at scale. Security analysts cited by Cybernews note that the data samples shown across multiple victim listings share similar schema — marketing analytics records, travel booking profiles, and customer contact details — pointing toward a common upstream vendor rather than separate direct intrusions into each financial giant.

What Visa Has Confirmed — and What Remains Disputed

Visa’s response has been carefully worded but unmistakably confirms an incident. The company issued this statement:

“Visa is aware of claims made by a threat actor. This incident originated with a third-party service provider in the Asia Pacific region. Visa’s systems were not involved and were not impacted. There is no indication that payment data such as card numbers have been affected.”

What Visa has not confirmed: the identity of the third-party vendor, which APAC markets are involved, how many records were accessed, or whether customer PII (names, emails, phone numbers) beyond payment data was exposed. Threat intelligence reporting from OODAloop suggests the stolen material includes cardmember profiles and travel booking details, mostly tied to Asia-Pacific markets — a significant concern for India, which is one of Visa’s fastest-growing APAC markets.

JPMorgan Chase’s position is different: the bank says its concurrent service disruption was caused by a software bug and that there is “no evidence” linking it to the n0n claims. That claim remains unverified and investigations are ongoing. Mastercard had not issued a public statement at the time of writing.

Technical Breakdown: How Supply-Chain Extortion Works

The n0n breach pattern fits a well-documented third-party compromise model. Here is how such attacks typically unfold:

Stage What Happens n0n Pattern
Initial Access Phishing, credential stuffing, or exploiting a public-facing app at the vendor Likely via marketing/analytics SaaS platform; multiple Fortune 500 clients share the same data warehouse
Lateral Movement Attacker pivots within vendor network to reach multi-tenant data stores Schema similarities across Visa, Expedia, and Eli Lilly data suggest shared SaaS backend
Exfiltration Bulk export of customer or partner records; often goes undetected for weeks Data described as contact profiles, travel bookings, analytics records — not card PAN/CVV
Extortion Public listing on leak site with countdown timer; 48-hour negotiation window Simultaneous listing of Visa, JPMorgan, Mastercard — maximises media pressure

The key insight here is that the breach did not need to penetrate Visa’s hardened core payment infrastructure. It reached Visa’s data via a trusted third party — almost certainly a vendor with legitimate API access to customer-facing systems. This is precisely why the zero-trust principle of “never trust, always verify” must extend beyond the internal perimeter and into every vendor relationship. For more on how to architect this in an enterprise environment, see our case study: Zero-Trust Across a 15-Building Campus with FortiGate.

India and APAC in the Crosshairs

Visa’s confirmation that the breach involved a vendor in the Asia-Pacific region is a direct alert for Indian organisations. India is Visa’s second-largest transaction market by volume in APAC. Thousands of Indian banks, fintechs, payment gateways, and retail enterprises have data-sharing agreements with Visa and its vendor ecosystem.

The practical exposure areas for Indian enterprises include:

  • Loyalty and co-brand card programs — customer PII shared with marketing analytics vendors
  • Travel and hospitality integrations — booking data tied to Visa checkout platforms, which may flow through the compromised APAC vendor
  • Fintech partnerships — open-banking APIs and payment orchestration layers that connect to Visa’s partner network
  • Call-centre and CRM data — customer service platforms that hold contact details used in loyalty and fraud management programs

If your organisation has any of these touch points with Visa’s vendor ecosystem, the prudent step is to treat your customer data as potentially exposed until Visa names the affected vendor and scopes the incident. This is not an overreaction — it is standard incident response posture during an ongoing investigation.

This story also echoes the recent TSMC cloud-vendor breach we covered last week. The pattern is the same: a world-class organisation with strong internal security suffers data exposure because a vendor in their supply chain was inadequately secured. Third-party risk is no longer a line item in a compliance checklist — it is an active attack surface.

What You Should Do Right Now

Whether or not your organisation has a direct Visa vendor relationship, the n0n campaign is a signal to tighten your third-party security posture across the board. Here is a practical action list:

Immediate (0–48 hours)

  • Inventory your APAC third-party data flows. Identify every vendor in the Asia-Pacific region that holds, processes, or has API access to your customer data. Priority on payment-adjacent, marketing analytics, and CRM SaaS platforms.
  • Activate your vendor breach notification clause. Review contracts with payment brand partners and demand written confirmation of whether they were affected by this incident — and what data you hold in common.
  • Monitor for credential abuse. If customer email or phone data was exposed by the APAC vendor, attackers will pivot to phishing and SIM-swap attacks targeting those customers. Increase fraud monitoring thresholds on high-value accounts.

Short-term (1–2 weeks)

  • Run a third-party access review. Audit which of your vendors have standing API keys, OAuth tokens, or database read permissions. Revoke or rotate credentials for APAC vendors until the Visa incident is scoped.
  • Check your DLP and CASB coverage. Confirm that your Data Loss Prevention and Cloud Access Security Broker tools flag bulk-export operations from shared SaaS environments. Many organisations have blind spots in multi-tenant analytics platforms.
  • Stress-test your incident response playbook for third-party breaches. Most IR playbooks are written for first-party incidents. If a vendor calls you tomorrow saying they were breached, do you have a documented response? The P J Networks team can help you build one.

Strategic (30–90 days)

  • Adopt a vendor risk scoring framework. CISA’s Secure by Demand guidance and ISO 27036 both provide structured approaches to vendor security assessment. Prioritise vendors with access to customer PII and payment-adjacent data.
  • Extend zero-trust segmentation to partner APIs. Every vendor API connection should enforce least-privilege scopes, time-limited tokens, and anomaly-based rate limiting. This is achievable with FortiGate application control and FortiAuthenticator-based API gateway policies.

Frequently Asked Questions

Is Visa’s core payment network safe to use?

Based on Visa’s own statement, the answer is yes — Visa’s payment systems were not compromised, and there is no indication that card numbers, CVVs, or transaction data were exposed. The breach was at a third-party vendor, not in the core Visa payment rails. However, customers should remain alert for phishing emails or unusual contact from anyone claiming to represent Visa, particularly if they receive suspicious loyalty or travel-related communications.

How serious is the JPMorgan Chase claim?

At this point, JPMorgan’s involvement is unverified. The bank has stated there is no evidence of a cyberattack and attributes the service disruption to a software bug. The n0n group’s listing of JPMorgan may be opportunistic — using a publicly known outage to inflate their credibility. That said, until investigations conclude, it cannot be entirely ruled out. Watch for JPMorgan’s official updates.

What data might have been stolen from Visa’s vendor?

Based on threat intelligence analysis, the exposed data appears to include customer contact information (names, email addresses, phone numbers), travel booking profiles, and marketing analytics records tied to Asia-Pacific markets. Payment card numbers and CVVs are reported to be unaffected. Visa has not confirmed the data categories, so treat this as preliminary intelligence subject to revision as the investigation progresses.

Should Indian fintechs and banks be worried?

Yes — with proportionate urgency. India is a key APAC market for Visa, and many Indian payment-adjacent organisations share vendor relationships that may intersect with the breached APAC provider. The Reserve Bank of India’s IT Framework for NBFCs and RBI’s Cyber Security Framework for Banks both mandate third-party risk management; this incident is exactly the scenario those frameworks anticipate. Review your vendor inventory now.

The Bigger Picture: Extortion Groups Are Targeting the Vendor Layer

The n0n campaign illustrates a maturing threat: sophisticated extortion groups are no longer trying to breach the fortified perimeters of global banks and payment networks. Instead, they are systematically targeting the vendors, integrators, and SaaS platforms that those giants trust. A single breach of a shared marketing analytics platform can yield data from a dozen Fortune 500 companies simultaneously — a far higher return on investment than attacking each target individually.

This is the supply-chain attack model applied to data extortion, and it is becoming the dominant threat vector for 2026 and beyond. The MOVEit campaign of 2023, the TSMC cloud vendor incident, and now the n0n APAC campaign all follow the same logic: attack the integrator, harvest the client data.

For Indian enterprises, the message is clear: your security posture is only as strong as the weakest vendor in your supply chain. And right now, that vendor may be sitting in an APAC data centre that n0n has already been through.


Is your vendor risk management programme ready for a supply-chain extortion incident? At P J Networks, we help Indian enterprises implement zero-trust architectures, third-party risk frameworks, and FortiGate-based perimeter controls that reduce your exposure across the supply chain. Book a security assessment today — before the next n0n countdown timer starts with your vendor’s name on it.