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
November 5, 2026
036
株式会社技研製作所 (GIKEN LTD.)
Construction machinery (press-in piling)
Ransomware
The company said one of its business servers suffered unauthorized external access including ransomware (「ランサムウェアを含む外部からの不正アクセスを受けた」) and personal data of about 3,200 people may have leaked; it cut external connections on Nov 6.
No outage reported
November 4, 2026
034
Queens Public Library
Public library system (New York City)
Ransomware
The library's outage page says: "This disruption, the result of a ransomware attack, impacts the following services": the website, mobile app, on-site computers, and digital media services. Wi-Fi and check-out and return machines are back. Branches are open, but the library reports "a significant network outage affecting all locations" and says it "will take some time before the Library's network and systems are restored." The outage was first reported Wed Nov 4 (NY1, The Register).
Ongoing
October 20, 2026
032
お名前.com デスクトップクラウド (Onamae.com Desktop Cloud)
Domain and cloud hosting service
Extortion
The service said malware was found on 2026-10-20 and about 26,739 servers were stopped from 04:00 on 2026-10-21. GMO's 2026-10-24 disclosure confirmed customer information was taken out. Its 2026-10-28 disclosure says 「当社グループは、攻撃者からの要求には永久に応じません。」 (the group will never comply with the attacker's demands), calls the attacker's use of customers' assets and information 「脅迫の手段」 (a means of extortion), and confirms that information apparently related to customers was published by a person believed to be the attacker. A ransomware attack was not confirmed as of the 10th report (2026-10-27 13:55).
Ongoing
October 20, 2026
031
City of Columbia (South Carolina)
Municipal government
Ransomware
"As the ongoing criminal investigation continues, the City of Columbia can confirm it is a victim of a ransomware attack." Impacted: MyColaSC and online services related to Animal Services, reservations for Parks and Recreation, and GIS; Police, Fire, 911, Columbia Water and the Payment Center unaffected.
Not stated
October 18, 2026
030
Kamalnayan Bajaj Hospital
Hospital (healthcare)
Ransomware
Per the police FIR filed on the hospital's complaint (Times of India, 2026-10-27), "the hospital alleged that all nine of its servers were hacked, data was encrypted and a ransom was demanded for its release." The FIR states patient care, billing, insurance processing and reporting were affected. Hospital executive committee member Dr Milind Vaishnav: "The services have not stopped, they have just slowed down."
Not stated
October 13, 2026
029
エンタッチ株式会社 (Entouch, subsidiary of Toho Holdings)
Healthcare services (pharma wholesale group)
Ransomware
Toho Holdings says the unauthorized access was 「ランサムウェア攻撃を行う第三者による不正アクセスが原因であり」 (caused by a third party that carries out ransomware attacks) and that data leaked. It says Entouch's business continuity was not affected.
No outage reported
October 7, 2026
028
IDC Frontier (IDCF Cloud)
Cloud provider
Ransomware
Cause: unauthorized access by a third party (ransomware attack) (第三者からの不正アクセス(ランサムウェア攻撃))
Cited backups
Ongoing; no timeline
October 2, 2026
027
Osaka Metropolitan University
Public university
Ransomware
University says: 「本事案についてはサイバー攻撃、いわゆるランサムウェア攻撃によるものと判断しており」 (it has judged the incident to be a cyberattack, a so-called ransomware attack). Its virtualization infrastructure failed early Oct 2, taking down the campus network, email, websites, and academic, finance, HR/payroll and library systems.
Partial: in-person classes back Oct 9 (7 days), email Oct 13 (11 days); full restoration not stated
September 26, 2026
026
Keio Corp
Rail and transport group
Ransomware
Title: system failure caused by a ransomware attack
Not stated
September 24, 2026
025
Saga University
Education
Ransomware
Damage that appears to have been caused by ransomware (ランサムウェアによると思われる被害) on a NAS used by administrative departments, found Sep 24 at 08:42. Oct 30 update: personal data of about 80,000 students, staff, former students and staff, and related parties (including passwords), plus patient data such as departments, diagnoses and visit dates (count under investigation), may have leaked; police consulted.
Exact: admin terminals back in use Sep 27 at 11:03 (about 3 days)
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, or extortion attacks confirmed by the organization that was hit, disclosed since October 1, 2025. That includes public companies, universities, government bodies, and private companies whose attacks got reputable coverage. A statement from a national cybersecurity agency counts as confirmation. We also list database ransomware campaigns documented by security researchers, tagged Database campaign. Those reports don’t name victims.

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. Incidents don’t count if the organization never says ransomware, encryption, or extortion. 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: SEC 8-K filings, stock exchange disclosures, company and university notices, and government statements, plus their follow-ups. When those words only reach us through news coverage, the source label says Press. How long they were down is in their words too, not our estimate. We review and approve every row.

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