President Trump used a televised Cabinet meeting to blame Minnesota and Gov. Tim Walz for a wave of cyberattacks on the state's water systems, rejecting the suggestion that Iran was behind the breach and pointing instead to what he called gross state-level incompetence.
Speaking from Camp David on Friday, Trump dismissed preliminary suspicions of Iranian involvement and redirected accountability squarely at Walz, the Democratic governor who served as Kamala Harris's running mate in the 2024 presidential election. The attacks struck at least 30 water system sites across Minnesota alone, part of a broader wave that hit remotely controlled water infrastructure in at least seven states, the Washington Examiner reported.
The breach forced some utility providers to abandon automated controls and switch to manual operations. Several states issued boil notices for affected communities. Minnesota officials said the state's water remained safe to drink, though the scope of the intrusion, 30 sites in a single state, raised immediate questions about how well the state had secured its critical infrastructure.
Trump's comments arrived against a specific backdrop: just days before the Minnesota attacks, the FBI, the Cybersecurity and Infrastructure Security Agency, and other federal and state agencies issued a joint advisory warning that Iranian-affiliated hackers had been targeting water and wastewater systems. The advisory flagged so-called programmable logic controllers, the computerized devices that regulate water treatment operations, as a primary vulnerability, particularly when those controllers are connected to the internet.
That warning gave early speculation about Iran a foothold. But Trump pushed back hard.
At the Cabinet meeting, described as the first time the press had been permitted to the presidential retreat to cover such a session, Trump laid out his view plainly:
"I just want to mention that we heard in Minnesota there was a cyber attack, and they blame it on Iran. I don't think so. I think I blame it on Minnesota because they're grossly incompetent. There was a cyber attack of dirty water plants, and I would blame it on Minnesota and the governor, the corrupt governor of Minnesota. They like to say, 'Oh, it's Iran.' Iran should be so lucky. Iran's got bigger problems than worrying about Minnesota."
The line "Iran should be so lucky" was a pointed dismissal, not of the broader Iranian cyber threat, which the federal advisory documented, but of the instinct to look overseas for blame when state-level negligence may have left the door wide open.
Walz responded through public comments. Fox News reported the governor fired back, saying Trump "knows exactly who is responsible for this attack, and knows that other states were hit too," adding, "This is what modern warfare looks like."
Minnesota IT Services, the state agency responsible for technology infrastructure, issued a cautious statement that neither confirmed nor denied Iranian involvement, and did not defend the state's cybersecurity posture.
"We are not attributing this activity to a specific threat actor at this time. Federal partners are best positioned to assess this incident alongside broader national and international threat intelligence and determine whether it may be linked to a particular actor."
The agency added that it was supporting the investigation and did not want to "speculate while that work remains underway." Attribution questions, the agency said, should go to federal partners.
That deferral itself is telling. If Minnesota's own technology officials cannot say who breached 30 water systems on their watch, the question of whether the state had adequate defenses in place becomes harder to wave away. Whether the attacker turns out to be Iranian, another foreign actor, or something else entirely, the fact remains: the systems were vulnerable, and the state was responsible for protecting them.
The FBI and CISA advisory was not speculative. Iranian hackers have a documented history of targeting American infrastructure. In 2016, the Justice Department charged a group of Iranian hackers for a cyberattack on a small dam in the New York City area, a case that established the precedent for treating Iranian cyber operations against U.S. physical infrastructure as a federal criminal matter.
The attacks on water systems in multiple states fit the pattern the advisory described. But Trump's argument was not that Iran poses no cyber threat. It was that Minnesota's own failures, in oversight, in competence, in basic infrastructure security, made the state an easy target, and that blaming a foreign adversary lets state leaders off the hook for their own negligence.
That argument gains force when set against the broader record of the Walz administration. The Justice Department alleged last December that half or more of $18 billion in federal funds spent on 14 Minnesota-run programs since 2018 may have been stolen. The programs spanned child nutrition, housing services, and autism services, core safety-net functions that the state was entrusted to manage with federal dollars.
Vice President Vance has since referred Walz and Minnesota Attorney General Keith Ellison to the Justice Department for a criminal fraud investigation tied to those allegations.
A state oversight report found that the Walz administration shielded fraud suspects by branding auditors as racists, a tactic that effectively shut down internal accountability mechanisms at the moment they were needed most.
The pattern is consistent: a state government that failed to safeguard billions in federal funds now faces questions about whether it also failed to safeguard the computer systems that control its residents' drinking water.
Trump's characterization of Walz as "corrupt" is a political judgment, not a legal finding. But the governor's record gives the charge more weight than a casual insult. Beyond the staggering fraud allegations in federal programs, Walz has drawn national scrutiny for decisions that suggest a pattern of prioritizing political considerations over public safety and the rule of law.
Walz pardoned an illegal immigrant convicted of sexually assaulting a child in what critics said was an effort to block the man's deportation. After federal authorities deported the man anyway, Walz continued to defend the pardon, a stance that put him further at odds with both federal law enforcement and public sentiment.
None of that history directly caused a cyberattack. But it speaks to a governing philosophy that Trump and his allies have identified as a liability: a willingness to deflect blame, resist oversight, and treat accountability as an attack rather than a responsibility. When 30 water systems go down on your watch and your first instinct is to point at a foreign government, the deflection fits a pattern.
State and federal authorities are still investigating the cyberattacks. No formal attribution has been issued. The FBI and CISA advisory warned broadly about Iranian targeting of water infrastructure, but the advisory was a general threat warning, not a specific finding tied to the Minnesota breach.
Minnesota IT Services' refusal to name a threat actor is procedurally defensible, investigations take time, and premature attribution can be counterproductive. But Trump's point was not about intelligence analysis. It was about accountability. Whoever pressed the button, the systems were exposed. The state that was supposed to protect them did not.
The cyberattacks hit operational technology at more than 30 community water systems across Minnesota on Sunday and Monday, according to reporting on the timeline. Some providers had to fall back on manual operations, a functional admission that the automated systems they relied on were compromised. In other states, residents received boil notices, a step that signals regulators could not guarantee water safety through normal treatment processes.
These are not abstract policy failures. They are failures that land in kitchens and bathrooms, in the water people give their children. When the systems that keep drinking water clean are breached, regardless of who did it, the people responsible for securing those systems owe the public more than a referral to "federal partners."
Trump framed the issue as one of competence, not espionage. Whether Iran was involved or not, the question he posed is straightforward: Why were Minnesota's water systems vulnerable in the first place? And why should taxpayers trust the same state government that may have lost $9 billion or more in federal fraud to protect something as basic as clean water?
When a governor's administration cannot account for billions in federal funds and cannot secure the systems that deliver drinking water, blaming a foreign adversary starts to look less like intelligence analysis and more like a reflex.
