The 2026 attacks on U.S. water utilities show what happens when systems accept commands without confirming who is sending them. Attackers reached internet-exposed industrial controllers at more than 30 Minnesota water systems and reconfigured them. The same gap exists in every organization: access is granted to whoever holds a device or credential, not to a verified person.
Key takeaways
- In July 2026, a coordinated cyberattack hit operational technology at more than 30 Minnesota community water systems, and utilities in at least seven states reported similar incidents.
- Attackers reached internet-exposed industrial controllers that accepted commands without confirming who was sending them.
- Utilities share integrators with remote access, which gives attackers an easy story when they impersonate a vendor engineer.
- The same gap exists in every organization: identity tools confirm the account and device, not the person.
- Verifying the real human at high-risk moments, like account recovery and helpdesk requests, closes it.
A Monday morning in late July 2026. Minnesota. Water utility operators across the state find that their automated controls have stopped responding. In Plymouth, two water towers and several lift stations lose communications and have to be run by hand. More than 30 community water systems have been hit. The city of Maple Plain declares a local emergency. Days later, the FBI and EPA warn that water utilities in at least seven states have reported similar incidents, some of which degraded water operations.
This sequence of events really happened. Most of the coverage afterward focused on exposure: Operational Technology (OT) devices, including Programmable Logic Controllers (PLCs), reachable on the open internet with basic or no protections. That’s true, but it skips the identity lesson underneath. The controllers accepted commands from whoever could reach them. Being able to connect was treated as permission to reconfigure. Nothing asked the question that matters at every high-risk moment: is the person doing this really who they claim to be?
The system never asked the one question that would have stopped everything: Is the person doing this really who they claim to be?
Why are utilities especially vulnerable to cyberattacks?
The most important part of these water utility attacks has very little to do with water.
Every day, across every organization, credentials change hands on the strength of what device a person is holding. A request comes in, an MFA prompt is answered, and an approval goes through. Nowhere in that sequence does anyone actually confirm who is behind the request.
Utilities carry a sharper version of that same exposure because so much of their access runs through shared hands.
Three things make utilities especially exposed:
- Shared integrators. Many utilities rely on the same outside integrators, who hold remote access to their systems.
- Internet-exposed equipment. PLCs reachable from the open internet can be reconfigured by anyone who can connect.
- Pressure to act fast. A helpdesk agent fielding a call from a “locked-out vendor engineer” has to decide on the spot, and generative AI makes the impersonation easy.
The FBI specifically notes that utilities share integrators, and integrators hold remote access. That creates an opportunity for clever attackers.
For example, an IT employee may take a call from someone claiming to be an engineer at your SCADA vendor who is locked out mid-maintenance-window. That help desk agent has to decide in real time, under pressure, whether the request is legitimate. But in the age of generative AI and $30 deepfake kits, it’s beyond trivial to convincingly fake an identity.
This problem isn’t unique to water utilities. CISA, the NSA, and the FBI have confirmed that Volt Typhoon (a state-sponsored group) successfully breached IT networks across numerous critical infrastructure domains, including communications, energy, transportation, and water, by stealing access to valid accounts. In some environments, they went unnoticed for at least five years because every system along the way saw a valid account and treated that as enough proof.
The basics often aren’t in place either. The EPA has found that more than 70 percent of water systems were failing to meet a 2018 legal requirement to maintain risk assessments and emergency response plans.
What do the Minnesota water attacks reveal about identity?
The gap that let all of this happen doesn't close until you know, with certainty, who is actually acting in a particular moment.
Today's identity tools do a good job of getting part of the way there. An identity provider like Okta or Microsoft Entra ID confirms that valid credentials and a trusted device are in play. That's critical, of course, but it only tells you which account is acting, not which person. The account is an artifact; the device is an artifact. Neither is a human, and both can be presented by someone who isn't who they claim to be.
That is the gap Nametag closes. Our workforce identity assurance engine confirms the real human behind high-risk actions, based on who they actually are:
- Self-service account recovery: an employee locked out mid-shift proves it’s really them and gets back to work.
- Helpdesk verification: agents replace security questions and gut calls with a definitive result inside their ITSM workflow.
- An audit trail: every verification ties a confirmed human to the action they took.
The attackers in Minnesota didn't break a lock, they simply walked through a door that never checked for the right person. And that door is propped open in a lot more places than water plants.
Frequently asked questions
What happened in the Minnesota water utility attacks?
On July 26 and 27, 2026, a coordinated cyberattack hit operational technology at more than 30 Minnesota community water systems. Several cities, including Plymouth, South St. Paul, and Maple Plain, switched to manual operations, and Maple Plain declared a local emergency. No boil-water notices were issued.
Who was behind the water utility attacks?
The FBI and EPA haven’t publicly attributed the attacks. Federal and state agencies are still investigating how the attackers got in.
What is Volt Typhoon?
Volt Typhoon is a state-sponsored hacking group that CISA, the NSA, and the FBI say compromised IT networks across U.S. critical infrastructure, including communications, energy, transportation, and water, in some cases staying hidden for at least five years.
See how Nametag closes and locks that door by confirming the real human behind every high-risk action: request a live demo.
.png)




