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
August 31, 2026
071
Jack Henry & Associates
Financial technology (core banking provider)
Jack Henry says a threat actor it identifies as ShinyHunters got into "a limited portion of our internal, non-production corporate environment" through a voice phishing attack. "This incident involved an extortion attempt, and we are not making any payment to the threat actor." No client-facing systems or core platforms were accessed or disrupted, there were no outages, and personal data for fewer than 10 clients was affected.
No outage reported
August 29, 2026
049
株式会社ポータス (Portus, school device management contractor)
IT services (school device management contractor)
Kushiro City's notice (updated Oct 15) says 「令和8年8月29日、委託事業者の社内サーバーがランサムウェアによる攻撃を受けました」 (on Aug 29, 2026, the contractor's internal server was attacked by ransomware). The contractor reported on Oct 13 that a leak couldn't be ruled out. Possibly exposed: names, account names and passwords of about 31,000 student and staff accounts, plus network-equipment and school email admin passwords for 39 schools. No leak or misuse confirmed; city systems and school devices not affected.
Not stated
August 25, 2026
023
Sanko Techno (Vietnam subsidiary)
Construction fasteners
Ransomware
Final report (Nov 10): attackers got in through a misconfigured network device at the Vietnam subsidiary in August 2026. Data on its internal servers was encrypted, taken, and published on a dark-web site, exposing details of about 898 people and 1,348 client companies. The subsidiary’s systems are back to normal.
Not stated
August 24, 2026
037
University of Illinois Chicago (College of Medicine)
Higher education (medical school)
Ransomware
UIC's notice letter (Oct 29) says: 'On August 24, 2026, UIC discovered a ransomware attack that affected parts of the College of Medicine network.' Unauthorized individuals accessed College of Medicine servers; names, dates of birth, addresses, medical record numbers, diagnoses, treatment and billing history may have been exposed. Affected systems were isolated.
Not stated
August 14, 2026
043
株式会社両毛システムズ (Ryomo Systems)
IT services and systems provider (government, water, energy)
Ransomware
The company's 4th report (Oct 30) says the incident was a ransomware attack (「本事案はランサムウェア攻撃であり」), confirmed Aug 19: an attacker entered through a VPN account on Aug 12, took administrator credentials on the authentication server, and was detected Aug 14, when the company cut off its network. Data on business-partner contacts, applicants, and current and former employees may have leaked; affected partners are being told individually. Customer Hiroshima Gas said on Nov 13 that some of its electricity customers' data handled through the company may have leaked.
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 16, 2026
044
The Coca-Cola Company (fairlife)
Food and beverage (dairy)
Ransomware
Coca-Cola's 8-K says it identified unauthorized access by a third party to a portion of its systems, including production-related systems, "in connection with a ransomware event", and that production operations at fairlife in the United States were temporarily suspended; Canada wasn't affected and product quality and safety weren't impacted. The company said on Jul 27 it had resumed the majority of fairlife production.
About 11 days or less (suspended by the Jul 16 8-K; majority of production back Jul 27 per the company, via AJC)
July 6, 2026
033
株式会社ウチコミ (Uchikomi)
Real estate rental platform (ウチコミ!)
Ransomware
The company says a server it manages failed on July 6, 2026, and its investigation found the server had been hit by a third party's ransomware, with some files encrypted and stolen. Up to 142,591 member accounts may be affected (name, email, date of birth, gender, address, and phone); it holds no card data. Systems were isolated, police were informed, and the privacy regulator was notified. No misuse or online publication was confirmed as of Nov 4.
Not stated
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
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