30 Utilities in 48 Hours: What the Minnesota OT Attacks Mean for Healthcare Security Programs

AI Security Series #64

On July 26 and 27, more than 30 community water systems across Minnesota were disrupted in a coordinated cyberattack targeting operational technology systems. Minnesota IT Services activated statewide cybersecurity incident response. CISA, the FBI, the EPA, and the Minnesota Department of Health are all investigating. Maple Plain declared a state of emergency. Braham issued a lawn-watering ban. Plymouth disconnected affected equipment from the network and began reconfiguring it. No water quality disruptions have been reported — the disruptions hit the automated control systems that manage treatment and distribution, not the water itself.

Attribution has not been finalized. Tenable's researchers suspect the Iran-linked group CyberAv3ngers, also tracked as IRGC-CEC, based on operational patterns consistent with the group's targeting history. The timing is notable: CISA updated Advisory AA26-097A on July 22 — four days before the attacks began — warning of Iranian-affiliated cyber actors exploiting programmable logic controllers across US critical infrastructure.

For healthcare security programs, this incident is not a water utility story. It is a resource-constrained OT story, and healthcare is one of the most resource-constrained OT environments in the country.

CyberAv3ngers: Who They Are and How They Got Here

CyberAv3ngers began as a propaganda persona, claiming disruptive attacks on Israeli infrastructure that were later debunked as fabrications. Their first confirmed, sustained campaign came in November 2023, when they compromised PLCs at the Municipal Water Authority of Aliquippa, Pennsylvania, defacing them with anti-Israel messages. Tenable documented at least 75 Unitronics Vision Series PLCs compromised across the United States, Israel, the United Kingdom, and Ireland during that campaign. The entry method: default passwords.

Between 2024 and 2025, the group matured significantly. They developed IOCONTROL — a purpose-built malware kit designed specifically for attacks on OT and IoT devices. OpenAI disclosed in 2024 that the group's members used ChatGPT in IOCONTROL's development process. The group has stepped up activity in 2026, with the Minnesota attacks representing the largest coordinated US water utility campaign they have been associated with.

The IOCONTROL detail matters beyond the novelty of an Iran-linked group using a commercial AI tool. It signals that AI-assisted malware development for OT environments is not a theoretical future risk. It is documented, attributed, and operational. The ThreatDown report we covered earlier this week noted that Google's Threat Intelligence Group identified what it believes to be the first known zero-day exploit developed by criminals using AI in May 2026. CyberAv3ngers used AI in IOCONTROL development at least two years before that. OT-targeted malware is already on the AI-assisted development curve.

The Attack Pattern: Why Small Utilities Are the Target

MNIT confirmed that investigators identified similarities in how the systems were accessed across the affected communities — the agency is not sharing specific technical details while the investigation continues, but the coordination across 30+ systems in a 48-hour window implies either a common access method or a common vulnerability class.

Tenable's analysis points to a targeting pattern that has been consistent across CyberAv3ngers' prior campaigns: small and rural utilities that lack dedicated cybersecurity resources. The specific conditions that make these facilities vulnerable are well documented and have not materially changed despite years of federal advisories. Some operators manage OT systems through remote-access software such as TeamViewer and AnyDesk — consumer-grade remote access tools that were not designed for industrial control system security. In some cases PLCs are exposed directly to the internet without any protective controls in front of them.

Plymouth's response illustrates the specific architecture that got targeted: the attack was limited to equipment connected via cellular communications at two city water towers and multiple lift stations. Cellular-connected OT is a common architecture in distributed water system deployments — it is cost-effective for geographically dispersed infrastructure. It is also an attack surface that sits outside the perimeter controls most IT security programs are built around.

The CISA Advisory Timing and What It Signals

The four-day gap between the July 22 CISA advisory update and the July 26 attacks is worth examining carefully. CISA Advisory AA26-097A warned that Iranian-affiliated cyber actors were exploiting PLCs across US critical infrastructure using tactics previously associated with CyberAv3ngers. The advisory was updated July 22. The attacks began July 26.

Two readings of that timing are possible. The first is coincidence — the attacks were already planned and the advisory timing is unrelated. The second is that the advisory itself, by signaling increased federal attention and impending detection capability improvements, created a use-it-before-detection-improves incentive. Neither reading is confirmed, and MNIT has explicitly not linked the Minnesota attacks to the CISA advisory's specific indicators. But the pattern is worth noting for healthcare security programs that track federal advisories as their primary threat intelligence input: advisories describe threats that are already operational, and the window between advisory publication and hardening completion is itself an exposure window.

What This Means for Healthcare

The structural conditions that made 30+ Minnesota water utilities vulnerable to a coordinated OT attack in 48 hours exist in healthcare environments today — in many cases in more acute form.

The resource-constrained OT profile is a healthcare problem

Small and rural water utilities share a defining characteristic with rural and critical access hospitals, federally qualified health centers, and small specialty practices: they operate OT or OT-adjacent systems with limited dedicated security resources. The biomedical device fleet in a 25-bed critical access hospital — infusion pumps, patient monitors, imaging equipment, building automation systems — is an OT environment. Most critical access hospitals have no dedicated OT security program. Many have no dedicated security staff at all.

The Minnesota attacks targeted utilities that, in the words of Tenable's researchers, lacked dedicated cybersecurity resources. That description fits a substantial portion of the US healthcare delivery system. The attack surface is different — patient data and clinical workflow rather than water treatment and distribution — but the resource profile and the legacy control system architecture are directly comparable.

Remote access software on OT is a healthcare exposure too

The TeamViewer and AnyDesk detail in the Minnesota attacks is not specific to water utilities. Remote access software is pervasive in healthcare OT environments. Biomedical device vendors routinely use consumer-grade remote access tools for device maintenance and troubleshooting. Building automation systems — HVAC, access control, power management — are frequently managed through remote access software by third-party facilities vendors. Laboratory instrument vendors connect remotely for calibration and service.

Healthcare security programs that have not inventoried remote access software on OT-adjacent systems and assessed whether those connections are controlled, monitored, and appropriately authenticated are operating with an attack surface they cannot see. The Minnesota attacks make the operational consequence of that gap concrete: 30+ facilities disrupted in 48 hours through access methods that have been documented in federal advisories for years.

Cellular-connected medical devices are the healthcare analog to Plymouth's water towers

Plymouth's specifically affected equipment was connected via cellular communications — outside the wired network perimeter. Healthcare has a direct analog in cellular-connected medical devices: remote patient monitoring equipment, implantable device management systems, portable diagnostic tools, and telemedicine endpoints that connect over cellular rather than the hospital network.

Cellular-connected medical devices typically sit outside the perimeter controls that healthcare IT security programs are built around, for the same cost and deployment flexibility reasons that make cellular attractive for distributed water system infrastructure. If your healthcare organization's asset inventory and network security controls don't explicitly account for cellular-connected medical devices, the Plymouth case study is the argument for closing that gap.

The coordinated multi-site pattern is the threat model shift

The most significant aspect of the Minnesota attacks from a healthcare perspective is the coordination: 30+ facilities in 48 hours. Prior OT attacks on US critical infrastructure — including CyberAv3ngers' own 2023 Aliquippa campaign — were largely single-facility incidents. A coordinated multi-site campaign against a common vulnerability class simultaneously is a different operational model. It implies either automation of the attack execution or pre-positioned access across multiple facilities that was activated simultaneously.

For healthcare, the equivalent scenario is a coordinated attack across multiple facilities in a health system, or across multiple health systems sharing a common vendor with a common vulnerability. Healthcare's increasing consolidation — more facilities operating under shared IT infrastructure, shared EHR platforms, shared biomedical device management systems — creates the same coordinated attack surface that made 30+ water utilities vulnerable simultaneously.

The AI-assisted malware development trajectory applies to healthcare OT

IOCONTROL, developed with AI assistance and purpose-built for OT and IoT devices, is already operational and attributed. Healthcare OT environments run a large population of IoT-adjacent devices — the same device categories IOCONTROL was designed to target. The ThreatDown report's six-month window estimate for Mythos-class capability reaching criminal markets applies here: the sophistication of OT-targeted malware is on the same AI-assisted development curve as every other category of offensive tooling.

Healthcare security programs that have deferred OT security investment on the assumption that their device fleet is too niche or too obscure to be targeted should be reassessing that assumption. IOCONTROL was purpose-built for exactly the device categories that populate healthcare OT environments. The group that built it has now demonstrated the capacity to execute coordinated multi-site attacks.

The Response Model: What Plymouth Got Right

Plymouth's immediate response — disconnecting affected equipment from the network to stop the attack and prevent retargeting while equipment was reconfigured — is the correct OT incident response pattern. It prioritizes containment over continuity, accepts a defined operational impact in exchange for stopping the spread, and gives responders a clean environment to investigate and recover from.

Healthcare OT incident response planning should have the equivalent decision documented before an incident forces it: what is the threshold for disconnecting biomedical devices or building systems from the network, who is authorized to make that call, and what manual procedures exist to maintain safe clinical operations during a controlled disconnection? These are not questions that should be answered for the first time during an active incident.

MNIT's whole-of-government response model — state CISO, CISA, FBI, EPA, Department of Health all activated simultaneously — is also worth noting. Healthcare organizations that have not pre-established the federal coordination pathway (specifically HC3 and CISA's healthcare-specific resources) for OT incidents should do so now, before an incident. The response coordination framework exists. Using it effectively requires having the relationships and notification procedures in place before you need them.

The Bigger Picture

The Minnesota water utility attacks are the largest coordinated OT attack on US critical infrastructure since the Colonial Pipeline incident, measured by number of affected facilities. They happened over a weekend, against facilities that had been identified as vulnerable in federal advisories for years, using access methods that have been documented and warned about repeatedly. The coordinating factor — shared OT architecture, common remote access tools, inadequate perimeter controls — is the same factor that will coordinate the next multi-site healthcare OT incident.

The investigation is ongoing and attribution has not been finalized. What is finalized is the pattern: resource-constrained OT environments, consumer-grade remote access software, internet-exposed control systems, and no dedicated security resources add up to the same outcome regardless of whether the facility treats water or patients. Healthcare security programs that read the Minnesota attacks as a water utility story are misreading it. It is a preview of what a coordinated OT campaign looks like against the infrastructure profile that healthcare shares.

This is entry #64 in the AI Security series. For related coverage, see Agent Skills, Shadow AI, and MCP Connections: The Attack Surface Healthcare Can't See and CISA Considers Three-Day KEV Deadline as Mythos Accelerates Exploit Timelines.