2024 · United States · D - Electricity, gas, steam and air conditioning supply · Ransomware attack disrupting business systems
Analysed 2026-11-06 by Hermes
Open this case in the tool →Ransomware attack disrupting business systems
No DV evidenced
Alternative: none defensible
(1) The expectation at MPW, a municipal electric, water and fibre utility serving ~50,000 residents, was a cyber programme that both separates the OT environment from the corporate IT network and protects customer data: its February 12, 2024 update stated that at no time were critical controls systems at the power plant or in the field at risk, and its 2024 annual report presents the utility's cyber-security measures as tested but responsive. (2) In practice, a ransomware incident identified on the evening of Friday, January 26, 2024 took customer internet service offline for about eight hours, left business systems inoperative for several days, and - as only a later forensic investigation revealed - exposed the names, Social Security numbers, driver's licence numbers and telephone CPNI of 36,955 current and former customers; the data exposure was not noticed while it happened. (3) That is where the evidence stops being a mechanism: no source documents how the intruder entered, no ransomware gang has claimed the incident, and no source states why the exfiltration went undetected - so no documented gap can be placed on either the origin axis (doctrinal vs material) or the break axis (leadership vs execution). Every stage that is documented by primary sources instead shows functioning controls - self-detection the same evening, internet restored within 8 hours via newly deployed equipment, business systems back within days, voluntary disclosure on January 29 and notification letters plus credit monitoring from March 1 - which evidences response competence but says nothing about why the one stage that failed failed, and alignment elsewhere does not by itself license 'No DV evidenced' for a case in which customer data was stolen. The class action alleging failure to implement reasonable safeguards (Cox v. Muscatine Power and Water, Iowa District Court, Muscatine County) was denied by MPW and settled for $525,000 without admission or any judicial finding of fault, so it is not treated as evidence of a gap. The entry vector is unknown and not load-bearing; the classification rests on no stage because none yields a defensible victim-side mechanism, hence Unknown (insufficient evidence).
RM35 — Egress / exfiltration monitoring gapEuRepoC metadata conflict: the Global sheet records intelligence_impact as no data breach or exfiltration, but MPW's breach notification letters (reported by The Record and WaterISAC, March 2024) confirmed names, SSNs, driver's licence numbers and CPNI of 36,955 people were potentially exposed; the row's disruption description itself matches the archived January 29, 2024 customer update. The case file's source_url (mpw.org customer update) now returns 404; the archived Wayback snapshots opened during this analysis are cited instead, plus the live 2024 annual report PDF and settlement page. Timeline wrinkle: MPW's own releases say the ransomware incident was identified January 26, while a law-firm summary of the notification letter dates discovery of suspicious activity to about January 31; the letter itself (state notification portal) was not opened, so the point is left unresolved and does not change the outcome. No attribution: no ransomware group has claimed credit and the investigation involved law enforcement (dataset legal_response_type). RM35 records the one documented adverse condition (customer data left unnoticed, found only after the forensic investigation concluded); no source states why egress went undetected, so it cannot be placed on the origin/break axes and the DV-Type stays Unknown. No consent-restricted action was required in this run.