Lastest 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

29

incidents logged

The 29 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 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)
September 20, 2026
024
エスケーロジ株式会社 (SK Logi)
Logistics
Ransomware
Company's 2nd report (Oct 3): 「2026年9月20日に発生したランサムウェアのサイバー攻撃によるシステム障害」 (system failure from a ransomware cyberattack on Sep 20). It cut affected systems off, stopped network order processing, confirmed some internal information leaked, and expected to resume network orders after finishing EDR rollout and scans on Sep 30.
Not stated (network orders expected to resume after Sep 30)
August 25, 2026
023
Sanko Techno (Vietnam subsidiary)
Construction fasteners
Ransomware
Ransomware attack, some servers encrypted
Not stated
August 9, 2026
022
REXT Holdings
Retail
Ransomware
Confirmed unauthorized access involving ransomware (ランサムウェアによる不正アクセス)
Expected: all stores reopening Aug 16, 2026 (2nd report); some services still restricted
August 5, 2026
021
CEC Co.
IT services and data center
Ransomware
「不正アクセスに起因する障害は、ランサムウェアによる攻撃であることを確認いたしました」 (confirmed the failure caused by unauthorized access was a ransomware attack). The attacked area was separate from customer systems and data.
Bound: service restored by the Aug 6 notice (about 1 day)
July 1, 2026
020
JADEPUFFER (Sysdig research, no victims named)
Databases
Extortion
Researchers describe agent-driven extortion against production databases: tables and databases dropped, ransom demanded.
No outage reported
June 19, 2026
019
River Financial Corporation
Banking
Ransomware
"determined that ransomware had been deployed across portions of its server environment"; "Certain operations have been impacted."
Not stated (no restoration stated as of Oct 3)
June 8, 2026
018
Navient (ransomware at its outside law firm)
Student loan servicing
Ransomware
"The incident involved a ransomware attack affecting certain of the Firm's information systems." Navient says it had no disruption to its own operations or customer services.
No outage reported
June 8, 2026
017
iRhythm Holdings
Medical devices (cardiac monitoring)
Extortion
"The communications from the threat actor demanded payment in exchange for not publicly disclosing this information." Data was on third-party-hosted business applications.
No outage reported
May 4, 2026
016
West Pharmaceutical Services
Pharma packaging and devices
Encryption
"certain data was exfiltrated by an unauthorized party and certain systems were encrypted". The May 20 amendment says it is "fully operational across its manufacturing, supply chain and commercial sites globally."
16 days or less (fully operational as of the May 20 8-K/A)
April 29, 2026
015
Instructure (Canvas)
EdTech
Extortion
"Instructure reached an agreement with the unauthorized actor"; it says "no Instructure customers will be extorted as a result of this incident."
Bound: offline May 7, fully back May 9 (about 2 days)
April 7, 2026
014
Systemsoft (subsidiary)
IT and real estate services
Ransomware
Confirmed encryption damage by ransomware (ランサムウェアにより暗号化される被害)
Not stated
March 27, 2026
013
Kota Co.
Cosmetics
Ransomware
3rd report (Apr 15): 「本システム障害はランサムウェア感染が原因であることが判明いたしました」 (the system failure was found to be caused by a ransomware infection). Production, orders and shipping continued.
Not stated
March 11, 2026
012
Trio-Tech International
Semiconductor testing
Ransomware
"The subsidiary experienced a ransomware incident that resulted in encryption of certain files within the Company's network." Singapore subsidiary; network taken offline to contain it; company data disclosed Mar 18.
Not stated in the 8-K
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)
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 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)
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
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 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 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

"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