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
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 17, 2026
070
Mount Royal University
University (Canada)
Mount Royal University in Calgary says a cyber incident found on June 17, 2026 "involved a ransomware threat actor," who stole data and then "deleted H drive data in an attempt to impede recovery" and also deleted the departmental J drive. Services came back in stages through July, and the university now says the H and J drives have been restored.
About 5 to 6 weeks for core services (MyMRU back July 24, 2026)
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
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
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 19, 2026
069
University of Mississippi Medical Center (UMMC)
Academic medical center
UMMC closed clinics statewide and canceled elective procedures after an attack on its network on Feb 19, 2026, running on downtime procedures. Epic came back on Feb 28 and clinics reopened Mar 2. A March memo called it "the Feb. 19 criminal ransomware attack of the UMMC network."
About 9 days for Epic (back Feb 28, 2026); clinics reopened Mar 2
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