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
February 15, 2026
011
Advantest
Semiconductor test equipment
Ransomware
"responding to a cybersecurity incident involving ransomware that may have impacted certain systems within its network"; an unauthorized third party "may have gained access to portions of the company's network and deployed ransomware." Affected systems isolated.
Not stated
February 13, 2026
010
Washington Hotel
Hospitality
Ransomware
Company notice title: 「ランサムウェア感染被害のお知らせ」 (notice of ransomware infection). Final report (Sep 7): ransomware entered through an external connection device and some servers were encrypted; backups survived and were used to restore. Card terminals were down at some hotels.
Cited backups
Not stated (Sep 7 final report: operations no longer impaired)
February 1, 2026
068
Sapienza University of Rome
University (Italy)
Sapienza says a ransomware incident that began with unauthorized access on Feb 1, 2026 compromised personal data it held, and that "at the end of the incident, the data on the compromised systems was encrypted." It rebuilt systems from available backups after checking them and restored services progressively. Italy's national cybersecurity agency closed the incident on Apr 2.
Cited backups
Not stated (progressive restoration)
January 26, 2026
009
Flare research (no victims)
Databases
Extortion
Bots wipe exposed MongoDB collections and leave a note demanding about $500 in BTC
No outage reported
January 22, 2026
067
Winona County (Minnesota)
County government
Winona County's notice letter says "On January 22, 2026, the County detected ransomware on our computer network" and that personal information it held was involved.
Not stated
January 7, 2026
008
興和江守株式会社 (Kowa Emori)
Chemical, green-tech and electronics businesses
Ransomware
The company said a ransomware infection caused a system failure (ランサムウェア感染によりシステム障害が発生), found 2026-01-07: email unusable and order-taking and shipping delayed. 2nd report (Jan 26): work and email on new PCs resumed in stages from Jan 27. 4th and final report (Apr 27): systems and operations stable; no clear sign of information leaking outside the company.
Upper bound: work and email on new PCs resumed in stages from Jan 27 (about 20 days)
January 6, 2026
048
株式会社カンバス (Canvass)
Software (licensing and authentication service)
Canvass's final report (Jan 29) concerns 「2026年1月6日に発生した弊社サーバへのランサムウェア攻撃」 (the ransomware attack on its server on Jan 6, 2026), which hit its authentication server and caused a system outage that left users unable to reach their My Page portal. The company says a personal-data leak is very unlikely but can't be ruled out.
Not stated
December 20, 2025
007
Apele Romane (Romania's national water authority)
Government
Ransomware
Romania's national cyber directorate (DNSC) says it was notified on Dec 20 of "un atac cibernetic de tip ransomware" (a ransomware cyberattack) on workstations and servers of Apele Romane and 10 of its 11 regional water basin administrations. About 1,000 IT systems were compromised, including GIS, database, email/web and DNS servers. Attackers used Windows BitLocker to encrypt files and left a ransom note asking to be contacted within 7 days. Operational technology was not affected; water infrastructure kept running, coordinated by phone and radio.
Not stated (Dec 24 update: user accounts restored; email, the finance app and the website still being restored)
November 25, 2025
006
YAC Holdings (subsidiary)
Industrial equipment
Ransomware
System failure caused by ransomware infection (ランサムウェア感染によるシステム障害)
Not stated
November 12, 2025
005
Checkout.com
Payments
Extortion
A criminal group "demanded a ransom"; "We will not pay this ransom"
No outage reported
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