LATEST INCIDENT: Aug 25, 2026

Ransomware Incident Tracker

Attackers claim thousands of hits on leak sites. We track the ones the organization actually confirmed.

Get updates on new incidents

Days since the last confirmed incident

00

incidents logged

The 00 so far, at a glance

What happened

18Reported an outage
11No outage reported

One of 29 said exactly when it was back up and running. Time a full restore of your most critical database, so you’d know your own answer.

How we count
Cite or reuse (CC BY 4.0)

Cite this tracker

The Datamaxxer, "Ransomware Incidents," Eon, eon.io/ransomware-incident-tracker. Last updated Aug 28, 2026.

Copy citation

Reuse the data

The data is free to use under CC BY 4.0. Share it, chart it, or build on it, commercially too. Credit "The Datamaxxer by Eon" and link back to this page.

Download CSV

Writing about this? Email [email protected] with questions about a row or how we count.

Ransomware incidents, by date detected

Detected
Incident
What happened
Recovered
Source
October 19, 2025
004
Askul
E-commerce
Ransomware
Infected with ransomware via unauthorized external access (外部からの不正アクセスによりランサムウェアに感染)
Cited backups
Partial: Soloel Arena web orders resumed Nov 12, 2025 (24 days); ASKUL web orders resumed in a staged restart through Dec 3; no LOHACO date
October 16, 2025
038
黒金化成株式会社 (Kurogane Kasei)
Chemicals manufacturing
Ransomware
The company's Oct 28, 2026 notice says a ransomware attack in October 2025 left its business systems and email unusable (「2025年10月に弊社が受けたランサムウェア攻撃により、弊社の業務システムやメールが使用不能となる事態」). Several sites lost internal network and internet access on Oct 16, 2025. Names, addresses, phone numbers, emails and job titles of business contacts, directors, employees and applicants may have leaked.
Not stated
October 15, 2025
003
Jewett-Cameron Trading
Manufacturing and distribution
Encryption
"unauthorized access and deployment of encryption and monitoring software by a third party"; threat actors threatened to release information unless paid
Not stated ("full operational capability shortly")
October 6, 2025
002
Wiz research (no victims)
Databases
Extortion
Logs in through missing or weak auth, copies data, drops databases, leaves a ransom table (README_TO_RECOVER, PLEASE_READ_ME, PWNED)
No outage reported
September 29, 2025
046
Asahi Group Holdings
Beverages
Asahi's Nov 27, 2025 investigation report says a disruption began about 7:00 a.m. JST on Sep 29, 2025, that "Ransomware was deployed simultaneously, encrypting data on multiple active servers," and that it spent about two months containing the attack and restoring systems, with shipments resuming in stages. Personal information on data-center servers may have been exposed; none seen published. Backup strategies and BCP plans are being redesigned.
About 2 months to contain and restore systems (company, Nov 27, 2025); all products shipping again from Apr 7, 2026 per press
September 20, 2025
001
Takeuchi Mfg (US subsidiary)
Construction equipment
Ransomware
Company notice: the US subsidiary's server was hit by ransomware and 「サーバーに保管されている一部のファイルが暗号化されている」 (some files stored on the server were encrypted); confirmed Sep 20 local time. Normal operations continued.
No outage reported
September 19, 2025
066
RTX (Collins Aerospace)
Aerospace and defense
RTX said it became aware of "a product cybersecurity incident involving ransomware" on systems supporting MUSE, Collins Aerospace's passenger check-in and boarding software used at airports. Airlines and airports moved to manual processes and saw flight delays and cancellations. RTX didn't expect a material financial impact.
Not stated
August 25, 2025
035
Accretive Co., Ltd. (contractor to the PPIH / Don Quijote group)
Business services (slip-processing contractor)
Ransomware
Company notice (PPIH group, with Accretive), 2025-10-10: the contractor's server was hit by unauthorized access and 「サーバ内がランサムウェアにより暗号化され」 (server contents were encrypted by ransomware). Detected 2025-08-25 right after an external vendor replaced the firewall; some servers including the file server were encrypted and unreadable. Reported to the Personal Information Protection Commission. Specialist investigation found no confirmed leak but could not rule it out; the notice says logs suggest low likelihood of external leakage. Possibly affected customer data: name (trade name), address, phone, payment account/transaction information; employee data: name and department.
Not stated
August 24, 2025
065
State of Nevada
State government
Nevada's after-action report says "the attacker deleted backup volumes and deployed ransomware, encrypting VMs and disrupting critical services" across more than 60 state agencies. The state didn't pay the ransom and recovered about 90% of the affected data; the deleted backups extended the recovery. Statewide restoration finished on day 28.
Cited backups
About 4 weeks (restoration complete on day 28)
August 16, 2025
064
Data I/O
Electronics manufacturing equipment
Data I/O said it "experienced a ransomware incident" on internal IT systems that disrupted communications, shipping, receiving, and manufacturing production. By Sep 10 it had restored the affected systems, said the attack came through a third-party firewall service's vulnerability, and estimated about $388,000 in costs.
About 3.5 weeks (upper bound; restored by Sep 10)
Show all

"Or less" means the organization said it was back as of a filing or notice date. If we missed a confirmed attack, email us. To hear about the next one, get updates.

How we count

What counts

Ransomware, encryption, extortion, and data-wiping attacks confirmed by the organization that was hit (or a national cybersecurity agency), detected since January 1, 2025. Any company, university, hospital, or government body counts. Database ransomware campaigns from security researchers are tagged Database campaign.

What doesn’t Count

Leak-site claims don’t get a row. If an attacker says it hit a company and the company hasn’t confirmed it, we don’t list the attack or name the company. If the organization only calls it a “cyber incident,” it doesn’t get a row, even when the press says ransomware. We only name an attacker when the organization or the police do, never from press reports alone.

How we source

Each row cites the organization’s own words, plus its follow-ups: SEC 8-K filings, stock exchange disclosures, breach notification letters, government statements, and notices from companies, universities, and hospitals.

The Datamaxxer newsletter

Hear about it before your boss forwards it to you.

  • 1Tracker updates: every new AI agent and ransomware incident, and whether the data came back
  • 2New research from Eon's engineers, starting with how nine AI models did on a generated company
  • 3Datamaxxing in the wild: real teams getting more out of their data
  • 4One thing to check on your own systems before Monday