N0n Puts Visa and Chase on the Clock; Both Deny a Breach
Extortion gang N0n listed Visa and JPMorgan Chase with a 48-hour countdown. Visa says an incident began at an Asia Pacific third-party provider and card data wasn't affected; Chase attributes its outage to a software bug.
The extortion gang N0n has added Visa and JPMorgan Chase to its leak site with a 48-hour countdown, SecureBlink reports. Both companies dispute that their own networks were breached. Visa does confirm it’s investigating an incident that began at an unnamed third-party provider in the Asia Pacific region, and says its own systems and card data weren’t affected. JPMorgan’s separate service outage is, the bank says, a software bug rather than an attack.
For defenders
Claimed vs confirmed:
| Status | |
|---|---|
| Visa | N0n claims data; no sample published. Visa confirms an incident at an Asia Pacific third-party provider, says its systems weren’t involved and it has seen no sign that card numbers or other payment data were affected. |
| JPMorgan Chase | N0n claims data; no sample published. The bank told Cybernews its ongoing outage is a software bug, with no evidence of a cyberattack, and hasn’t commented on any link to the claim. |
Who N0n is: a financially motivated extortion group first seen on Sept. 18, 2026. By mid-October it claimed more than 100 victims in over two dozen countries, according to SOCRadar, which puts financial services at 23% of its claimed victims. Its usual sequence is a quiet intrusion, then a public listing, then leak archives if nobody pays. It also claimed nearly a billion Expedia records; Expedia later confirmed a breach through a third-party data platform but not the numbers. Earlier it listed 38 port and shipping firms in one night.
How it gets in: credentials, not exploits. SOCRadar and The Register found no vulnerability exploitation in any documented intrusion. Instead the gang used credential stuffing through residential proxies against more than 300 FortiGate SSL-VPNs, scanned RDP and WinRM for weak admin passwords, abused long-lived AWS IAM keys and stole admin sessions from hosting portals. SOCRadar maps this to T1078 (Valid Accounts), T1133 (External Remote Services) and T1110.004 (Brute Force: Credential Stuffing). The operators use an open-source coding agent backed by uncensored AI models to write their intrusion scripts.
The locker: AES-256-CBC with Windows, Linux and Cisco firewall builds, appending .n0n. Researchers found several builds share one hardcoded 32-byte key, so a decryptor from one victim would likely work for another.
What it means for you
Right now this is a claim from a criminal group, not a confirmed theft of Visa or Chase customer data. Visa says card numbers weren’t touched, and Chase blames its outage on a software bug. Still, headlines like this bring a wave of scam texts and emails pretending to be your bank or card company, asking you to “verify” your account. Your bank won’t ask for your full card number, PIN or one-time code by text, email or phone.
Do this now
- Ignore any message about a “Visa breach” or “Chase security issue” that asks you to click a link or read out a code. Call the number on the back of your card instead.
- Turn on transaction alerts in your banking app so you see any unexpected charge right away.
- Admins: put MFA on every VPN, RDP and WinRM login, and lock out repeated failed logins on FortiGate SSL-VPN.
- Rotate long-lived cloud access keys and check which suppliers hold standing access to your data.