Kettering Health’s Cyber Siege: Unraveling the Silent Attack on Hospitals
Summary
- Kettering Health, a hospital system based in Dayton, Ohio, was hit by a cyberattack that disrupted its operations.
- The attack was identified as ransomware, affecting patient care and putting data at risk.
- The FBI and outside security firms were brought in to help respond.
- The outage shows how exposed hospitals remain to determined attackers.
A hospital system goes offline
Kettering Health, which runs hospitals and clinics across the Dayton area, suffered a system-wide technology outage on May 20, 2025 after a cyberattack that reached its medical centers across southwest Ohio and forced staff back to paper. Phones went down too. Other hospital systems are watching closely, because most of them run on the same kind of connected records and scheduling systems.
Ransomware inside the network
The attack was identified as ransomware. Attackers got into the hospital system’s network and encrypted data. Services that staff rely on every day stopped working. Hospital leaders had to switch from running patient care to running an incident response.
Local authorities and the FBI worked with security specialists on the response. The biggest worry was patient data: whether it had been stolen, and whether it might be misused.
Start your morning with the signal that matters.
Weekday mornings. Five minutes. What changed in security, why it matters.
By subscribing you agree to our Privacy Policy.
Free. Weekday mornings. 5 minutes or less.
Care on paper
The damage went beyond Kettering’s own systems. Elective procedures were canceled, emergency services faced delays, and staff fell back on manual processes while key technology was down. Every extra step on paper slows care.
Hospitals now run on interconnected systems. When those systems fail, the clinical side feels it within minutes.
Lessons for other hospitals
Other hospital systems will use Kettering’s experience to check their own plans. Many have never tested what happens if records and phones fail at the same moment.
Hospital leaders are putting more money into security, but tools alone do not solve it. Staff need training to spot phishing, report problems quickly and keep working when systems go dark.
Working with outside agencies
Hospitals are sharing more information with security firms and government agencies after attacks like this one. The aim is to spot similar intrusions sooner and respond faster.
Start your morning with the signal that matters.
Weekday mornings. Five minutes. What changed in security, why it matters.
By subscribing you agree to our Privacy Policy.
Free. Weekday mornings. 5 minutes or less.
Kettering has said it is working with authorities and outside cybersecurity consultants to restore systems and protect patient information.
What hospital boards should take from it
Kettering Health’s outage shows that a hospital’s cyber defenses are part of patient safety. Records and imaging depend on systems that attackers know how to break. So does the schedule.
Boards should ask three questions this quarter. How long can we run on paper? When did we last test restoring from backups? Who calls the FBI, and when?
Newer CyberExperts coverage on this topic
This article still works as background. If you want the current picture, start with the freshest related coverage below and today's brief.
Citrix NetScaler CVE-2026-19490: The Auth Bypass That Went From PoC to Probes in a Day
CVE-2026-19490 is a CVSS 9.3 NetScaler Gateway/AAA auth bypass. A public PoC on Sept 2 was followed by live probes within a...
PaperCut NG/MF: The Print Server That Learned Remote Code Execution Again
CVE-2026-81578 and CVE-2026-82078 chain to pre-auth RCE on PaperCut Application Server. Confirm Emergency Patch Release 2, restrict admin exposure, and hunt like...
JFrog Artifactory CVE-2026-82329: Empty Join Key, Full Admin Token, Busy Scanners
CVE-2026-82329 lets attackers forge Artifactory admin tokens via a deterministic empty join key. Mass scanning peaked near 406,000 attempts; patch fixed builds...
Friday’s brief: Apache’s HTTP/2 fix, then Check Point break-ins, a ScreenConnect add-on and a GitHub secret stealer
The fastest way to catch up on what changed after this article was published.
Start your morning with the signal that matters.
Get the biggest cybersecurity developments, why they matter, and where to go deeper on CyberExperts.
By subscribing you agree to our Privacy Policy.
Free. Weekdays. Built for operators.