- Date
- March 15, 2026
- Location
- United States
- Industry
- Oil & Gas
- Access vector
- Internet Accessible Device
- OT targeting
- Direct (sophisticated)
- Primary peril
- None
- Impact duration
- Within days
Sage Water Resources Utah PLC intrusion, March 2026

The incident path, stage by stage
Each stage of the attack, from intent to financial loss, with this incident’s path highlighted. Solid cells are confirmed, dashed cells are reported by a source but not confirmed, dotted cells are implied by the facts, and Unknown marks what is not publicly known. Click a stage title or a highlighted cell to read that part of the analysis.
Scroll sideways to see every stage.
On this page
Highlights
What happened. On March 15, 2026, Sage Water Resources (SWR) detected unauthorized activity on the programmable logic controller (PLC) at its oilfield saltwater disposal facility near Duchesne, Utah[1]. According to the company’s chief financial officer, the intruder’s changes bypassed shutdown protections, and the pumps kept running dry while the control system showed them operating normally[2].
Why it matters. The control system was made to show operators a false picture, and the person who caught it was a truck driver who saw that the pumps did not match the screen[2]. The company says the changes were mitigated before any physical or environmental damage[1].
About this analysis. This analysis sets out what is known, stage by stage. Nearly everything known comes from the company itself, through a press release and its CFO’s account to one outlet; no independent source corroborates it. This account reflects the best available information as of October 22, 2026; new information could confirm, change or discredit parts of it.
Highlights
- The intruder’s changes bypassed the PLC’s shutdown protections and made the control system show normal operation while the pumps ran dry, the CFO said[2].
- A truck driver noticed the mismatch during an early-morning unloading. Workers shut down the automated system and switched to manual operation[2].
- Sage calls the actor “an advanced nation-state threat actor”, but no federal agency has attributed the incident, and the CFO said Sage’s systems could not determine who did it[1][2].
- How the intruder reached the PLC is not established. Afterwards, Sage moved the controller behind a VPN “to eliminate direct internet exposure”[2].
Attack flow
- Updated: 2026-10-22
- Intent: Malicious [confirmed | per SWR]
- Threat actors: Nation-State [reported | per SWR; no agency attribution]
- Access vector: Internet Accessible Device [reported | T0883, route not established]
- IT impact: Not disclosed [unknown | No IT system described]
- OT targeting: Direct OT Compromise [confirmed]
- OT sophistication: Sophisticated [confirmed | deception-based]
- OT impact: Manipulate Control [confirmed | T0831]; Manipulate View / Spoof Reporting [confirmed | T0832]; Loss of Safety [confirmed | T0880]
- Perils: No Perils [confirmed | No physical damage reported]
- Financial losses: Assets & Equipment [confirmed | restart validation]; Data Loss [confirmed | logic rebuilt]; Cyber Incident Response [confirmed]
What happened
SWR, a subsidiary of Sage Energy Partners, detected the activity on March 15, 2026[1]. DysruptionHub names the site as the Blue Bench 13-1 facility, which injects oil and gas wastewater underground and does not provide drinking water to the public. CFO Steve Crower, who said he led the company’s cybersecurity response, gave the outlet the detail by email in August[2].
The intruder’s changes bypassed shutdown protections, and the pumps kept running dry while the control system showed them operating normally. A truck driver noticed during a routine unloading that the pumps did not match the control system and alerted the facility manager early that morning. Workers shut down the automated system and switched to manual operation. “Facility operations transitioned smoothly to manual override,” Crower said[2]. SWR’s press release says the unauthorized logic changes “were detected and mitigated before causing physical or environmental damage”[1].
Sage’s automation contractor reconstructed and verified the controller’s safety logic, and the site returned to continuous operation within days. Sage worked with CISA, the FBI, the National Security Agency, the Energy Department and Rockwell Automation, and CISA staff carried out a network assessment in late July[2]. About two weeks after the intrusion, the well failed a state-required mechanical integrity test and disposal was suspended; crews replaced a compromised packer. Sage has not linked that failure to the cyber incident[2].
Intent: malicious
SWR’s press release says forensic analysis confirmed “a malicious logic manipulation”[1]. Changes that bypassed shutdown protections and hid the result behind a normal display are not an error. What the intruder wanted is not stated in any source. Both the finding of malice and the description of the changes come from the company.
Threat actors: a nation-state, per the company only
SWR describes the actor as “an advanced nation-state threat actor”, in an attack “consistent with a broader, sophisticated campaign targeting critical infrastructure operators across the United States energy and water sectors”[1]. Its CFO later said Sage’s systems “were not configured to collect enough forensic data to independently determine who conducted the intrusion”[2].
He said the tactics in federal advisory AA26-097A, which describes Iranian-affiliated actors targeting internet-facing PLCs, “are consistent with what we experienced”[2]. That advisory names no victim[3], and no federal agency has publicly attributed this incident[2]. Nation-State is shown as reported.
Access vector: not established
No authority has said how the intruder reached the PLC, and Sage declined to say how long the access lasted or to name the controller’s maker or model[2]. After the incident, Sage moved the controller to a network reachable only through a VPN “to eliminate direct internet exposure”, which indicates it was reachable from the internet before[2]. AA26-097A describes actors exploiting internet-facing PLCs[3]. Neither the company nor any agency says the attacker came in that way, so Internet Accessible Device is shown as reported, not confirmed. Rockwell Automation appears only as a party Sage worked with; the reporting does not say the controller is a Rockwell product[2].
IT impact: not disclosed
No source describes any IT system being involved. The false “normal” pump status came from the manipulated PLC logic, not from a compromised display host, and no operator console, engineering workstation or field laptop is described as compromised[2][1]. Whether the route to the PLC crossed an IT network is unknown. This stage is marked Not disclosed.
OT targeting: a direct compromise
The PLC’s own logic was altered[1]. The controller that runs the disposal pumps was the system the intruder changed, which makes this a direct OT compromise. SWR speaks of “unauthorized logic changes”[1]; in MITRE ATT&CK for ICS terms that is Modify Program, T0889.
OT sophistication: sophisticated
The intruder did not merely deny control, which an operator would notice at once. The changes bypassed shutdown protections and left the control system showing normal while the pumps ran dry[2]. That is deception, the pattern of falsified normal readings associated with Stuxnet, and on that basis the stage is graded Sophisticated. The grade rests on the company’s description of the effect; the controller’s maker, model and altered logic have not been disclosed[2].
OT impact: control manipulated, view spoofed, safety lost
Three effects are confirmed by the company. The changes caused the pumps to keep running dry: Manipulation of Control, T0831. The control system showed the pumps as operating normally: Manipulation of View, T0832. And the changes bypassed shutdown protections: Loss of Safety, T0880[2]. These technique readings are this analysis’s, from the CFO’s account; SWR’s press release speaks of altered logic without naming the safety function[1]. What ended the hazard was a person: workers took the site to manual operation[2].
Perils: no physical damage reported
No physical damage is reported. The CFO said running the pumps dry “could have caused cavitation and pump failure”, but SWR states the changes were mitigated before causing physical or environmental damage[2][1]. No source reports a tank overflow, a release or a pressure event. The well’s failed mechanical integrity test about two weeks later is not linked to the incident by Sage or any other source, so it is not carried as a peril[2].
A screen that says normal is only as trustworthy as the controller behind it.
Financial losses: none disclosed
Sage has not disclosed its response costs, and no source gives a figure for the logic rebuild, the hardening or any operational consequence[2]. What is confirmed is the work: the safety logic reconstructed and verified, forensic analysis with federal agencies, an on-site security server, and a move “from a legacy configuration (‘Chevy’) to one of the most advanced PLC / VPN configurations in the oilfield (‘Cadillac’)”[2][1]. Smart Water Magazine describes an “upgraded setup with an advanced PLC system”[4]; that is its paraphrase, and no source says the PLC hardware was replaced.
Loss evidence
- Confirmed: Startup and return-to-service validation; Production data integrity (falsified pump status); Control logic recovery; Network event response and recovery; Voluntary improvements
- Not supported: Equipment repair and replacement; Spills and cleanup; Environmental regulation liability; Network device replacement; Embedded device replacement; Server replacement; Computer and laptop replacement; Regulatory action or liability
No regulator action tied to the cyber incident is documented, and SWR’s disclosure was a voluntary press release.
What this incident shows
The PLC’s own shutdown protections were bypassed by changes in the same controller that drove the display, and no independent engineered protection is reported[2]. The facility’s monitoring showed false normal readings; detection depended on a truck driver’s physical observation[2].
The site also lacked the data to say who had been inside: the CFO said its systems were not configured to collect enough forensic data[2]. The fixes Sage describes, a VPN-only network and an on-site security server, address exposure and visibility[2]. Whether the attacker used that exposure is still not established.
References
- Sage Energy Partners. “Sage Energy Partners Wholly Owned Subsidiary Sage Water Resources Announces Successful Recovery and Enhanced Cybersecurity Hardening of Uinta Basin Infrastructure Following Targeted Geopolitical Cyber Incident.” PR Newswire, 10 June 2026, as carried by Mining Stock Education. miningstockeducation.com/2026/06/sage-energy-partners-wholly-owned-subsidiary-sage-water-resources-announces-successful-recovery-and-enhanced-cybersecurity-hardening-of-uinta-basin-infrastructure-following-targeted-geopolitical-cyber/
- Topping, Joseph. “Sage Water Resources Says Utah Saltwater Disposal Controller Intrusion Bypassed Pump Safeguards.” DysruptionHub, 4 Aug. 2026. dysruptionhub.com/sage-utah-controller-intrusion/
- FBI, CISA, NSA, EPA, DOE and U.S. Cyber Command Cyber National Mission Force. “Iranian-Affiliated Cyber Actors Exploit Programmable Logic Controllers Across US Critical Infrastructure.” Joint Cybersecurity Advisory AA26-097A, 7 Apr. 2026. ic3.gov/CSA/2026/260407.pdf
- Tempest, Olivia. “Cyberattack Hits Utah Water Facility.” Smart Water Magazine, 11 June 2026. smartwatermagazine.com/news/smart-water-magazine/cyberattack-hits-utah-water-facility


