Analyst assessment
Saint Paul, Minnesota, detected suspicious activity on July 25, 2025, involving privileged accounts and a backup server at Saint Paul Regional Water Services. The city’s detailed legislative timeline dates restrictions on most employee VPN access to July 27 and an attempted encryption of virtual servers followed by a broader network shutdown to July 28.
Gov. Tim Walz’s July 29 announcement and Emergency Executive Order 25-08 authorized National Guard cyber support after the incident exceeded the city’s response capacity. This was an operational municipal disruption, including effects from protective isolation, rather than proof that all city systems had been compromised.
Operational significance
The legislative timeline documents temporary customer-service phone arrangements, restricted communications, printed payroll statements and a large employee credential-reset and device-check operation. The city said emergency response and payroll continued.
The Sept. 18 city release confirms restoration of public internet, computers and printing at libraries and recreation centers. It also identifies recovery of financial/payment tools, GIS, phones, email, legislative tools and core library systems, alongside the Sept. 17 launch of the PAULIE permitting and licensing platform. Wider recovery was still underway.
Route Fifty’s Nov. 26 report describes continuing recovery and cites an Oct. 22 city milestone of roughly 75% of systems restored. It also reports that some legacy applications could not return and were being replaced. A major public-service milestone therefore did not establish complete technical recovery.
Confidence and uncertainty
Cyber and ransomware confidence are confirmed by the city’s official accounts of attempted encryption and a ransom demand. Actual encryption extent remains uncertain; a defensive shutdown does not establish successful encryption across the network.
The city’s July 2, 2026, investigation report confirms about 43 GB of stolen data from a Parks and Recreation drive and personal information involving 12,484 people, including employees, former employees, interns, volunteers and recreation participants. Identifying data included names, addresses, phone numbers, birth dates and Social Security numbers. The city said core city-service data was not included, the material was exposed Aug. 11, 2025, and ransom was not paid. Its review and notifications establish data impact independently of the actor’s allegation.
An Interlock listing was discovered Aug. 11. Interlock’s claimed responsibility remains qualified because the reviewed city report does not name the group. The listing supports an allegation, not independently confirmed attribution.
Analytic gaps
The initial intrusion method, full access window, exact extent of encryption, complete application-by-application restoration dates and total final cost remain unestablished. The city says it commissioned an independent after-action review; that statement does not substitute for the review’s unreleased findings.
Our July 29 coverage described the initial emergency response. The Feb. 11, 2026, state assistance announcement authorized $1.2 million; a later funding announcement or data-notification milestone does not by itself demonstrate continued operational disruption.
Operations are presumed resolved. The latest precise quantified ongoing-recovery observation reviewed is Oct. 22, 2025; later city reporting describes rebuilt systems and completed data review. No reviewed source provides an exact day when all affected functions recovered. The end date remains unset, and July 2026 breach reporting does not extend the operational-impact clock.