n0n JPMorgan data leak
n0n extortion gang leaks JPMorgan Reserve cardholder data
Posted · Spectrum Delta Research Team
Summary
The n0n extortion group published a file it said was stolen from JPMorgan Chase on its dark-web leak site after a 48-hour countdown expired, and JPMorgan says attackers targeted its third-party providers and accessed marketing data that may include customer names and email addresses. Cybernews researchers reviewed the 502 KB file: roughly 16,000 customer emails tied to the Reserve card program, phone numbers, account IDs and 124 employee email addresses. n0n, first tracked in mid-September 2026, lists 221 claimed victims on a leak site signed no js no mercy and sends automated countdown warnings to victims' service providers and media, but Bitdefender found only about 20 real victims behind inflated listings. Its intrusions are credential-led: stuffing through residential proxies against 305 FortiGate SSL-VPN portals, weak RDP and WinRM passwords and exposed long-lived AWS keys, run with an opencode AI coding agent across 154 model entries and over 7,216 dollars in LLM spend. Expedia confirmed a supply-chain breach on 12 November that n0n claims covered about one billion records; researchers believe the group operates from Russia, though attribution is not definitive.
Breakdown
Countries
- United States
Targets
OrganizationsIndustries
- Organization: JPMorgan Chase
- Organization: Expedia
- Industry: Financial services
Technical exposure
- Internet-reachable SSL-VPN, RDP and WinRM with weak or long-lived credentials
- Exposed long-lived AWS keys and reused hosting-portal sessions
- Third-party vendors holding bank marketing data with customer emails
- Employee email addresses usable for spear-phishing and help-desk impersonation
Adversary
n0n, a data-theft and extortion group first tracked mid-September 2026; researchers believe Russia-based, attribution not definitive
Procedures (5)
Credential stuffing through residential proxies
- T1110.004Brute Force: Credential Stuffing
Logs
FortiGate VPN log · Repeated failed logins then success on /remote/logincheck from residential SOCKS5 proxies across 305 SSL-VPN portals; cookie APBSID=n0n
Hidden admin accounts and stolen browser sessions
- T1564.002Hide Artifacts: Hidden Users
- T1539Steal Web Session Cookie
Logs
- EDR process and file events · Local admin accounts svc_upd and svc_reg hidden via SpecialAccounts UserList; chrome.exe launched with --remote-debugging-port on a copied profile; mailbox reads of emailed MFA codes
Logs
- EDR file events · Mass renames to the .n0n extension, n0n_READ_ME.txt and C:\Users\Public\n0n\; shadow-copy deletion and free-space wipe
Cisco FMC audit log · Access policies switched to BLOCK; Snort rule n0n-lock (sid 2100001) present on hijacked FMCs
Leak-site publication and pressure campaign
- T1567Exfiltration Over Web Service
Logs
- Threat intel leak-site monitoring · New Company #N entries with 48-hour countdowns on the n0n onion leak site; automated countdown warnings sent to victims' service providers, clients and media
Indicators of compromise
IPs (5)
- 185.157.161.148exposed agent box and kserver C2, /x/i beacon
- 185.157.161.93ntpsync.io origin, PHP payloads
- 81.161.239.10loot vault and implant C2, payloads on port 8455
- 188.214.135.130leak-site backend, payloads on ports 8898 and 8899
- 217.18.55.185self-hosted LLM on port 11434
Domains (4)
- ntpsync.iopayload staging domain
- n0n-cases.netnotice@ mailer domain for countdown warnings
- uberip.comproxy infrastructure
- nongzecboljwv3yfndkggsybsglfrkffw7bvk2zemuteoxe6etpusnad.onionleak site
Sources
- B/2Cybernews: Hacker leaks details of JPMorgan's ultra-wealthy cardholders
- B/2SOCRadar: n0n ransomware: AI-assisted extortion
- B/2The Register: Crim spent $7K+ on AI services in extortion attacks, then left evidence for all to see
- B/2Bitdefender: Threat Debrief November 2026
- B/3SC Media: Expedia confirms data breach following supply chain attack
Grades are source reliability (A–F) and information credibility (1–6).
Questions, detections or sightings of n0n JPMorgan data leak? Bring them to the community.