- Date
- May – Aug 2017
- Location
- Saudi Arabia
- Industry
- Chemicals
- Access vector
- Internet Accessible Device
- OT targeting
- Direct (sophisticated)
- Primary peril
- None
- Impact duration
- 10 days
Triton safety system malware at Petro Rabigh, 2017

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. Between May and August 2017, attackers worked their way from the IT network of Petro Rabigh, a Saudi Aramco and Sumitomo Chemical refining and petrochemical joint venture, to the Triconex safety instrumented system (SIS) controllers on its burner management system[1]. The malware they planted tripped the plant to a safe shutdown twice: for seven days from June 2, and for ten days from August 4[1].
Why it matters. The attack reached the safety layer that forces a plant to a safe state when the process turns hazardous. What ended it was that layer’s own redundancy check, not the defenders, and no physical harm followed[1].
About this analysis. This analysis sets out what is known, stage by stage. Much of the site-specific detail comes from one reconstruction, the Idaho National Laboratory’s 2022 case study, and the 2017 technical reports did not name the victim. This account reflects the best available information as of October 22, 2026; new information could confirm, change or discredit parts of it.
Highlights
- The attackers entered through a poorly configured, internet-exposed firewall and a compromised perimeter VPN, stole administrator credentials and reached the SIS engineering workstations. From there they loaded their own code onto Triconex controllers[1][2].
- On August 4, 2017, the controllers’ redundant processing units failed a validation check, and six controllers took the plant to a safe shutdown. No source reports fire, release, injury or equipment damage[1].
- FireEye assessed with high confidence that a Russian government-owned institute, TsNIIKhM, supported the intrusion. The US Treasury sanctioned the institute, and the US Department of Justice charged a programmer at an institute affiliated with Russia’s Ministry of Defense[3][4][5].
- The only disclosed loss is about $938,000 in revenue for the August shutdown, a figure INL cites to Petro Rabigh’s own financial information[1].
Attack flow
- Updated: 2026-10-22
- Intent: Malicious [confirmed]
- Threat actors: Nation-State [confirmed | TsNIIKhM, Russia]
- Access vector: Internet Accessible Device [confirmed | T0883]; External Remote Services [confirmed | T0822, perimeter VPN]; Credential Theft [confirmed | T1003.001, T0859]
- IT impact: Malware [confirmed | Backdoors, Mimikatz, SecHack]
- OT targeting: Direct OT Compromise [confirmed]
- OT sophistication: Sophisticated [confirmed]
- OT impact: Inhibit Response [confirmed | T0881]; Loss of Safety [reported | T0880, designed capability]
- Perils: No Perils [confirmed | Safe shutdown, no physical event]
- Financial losses: Business Interruption [confirmed | $938K]; Hardware Bricking [confirmed | Compromised SIS controllers]; Assets & Equipment [implied]; Health, Safety, Casualty [implied]; Data Loss [implied]; Cyber Incident Response [implied]
What happened
The most detailed account is a 2022 case study by Idaho National Laboratory (INL) under the US Department of Energy’s CyOTE program. It says the attackers had remote access to Petro Rabigh’s IT network no later than May 2017, through a poorly configured, internet-exposed firewall, and separately that the perimeter VPN was compromised during off-hours, followed by the poorly configured DMZ. They stole administrator credentials with Mimikatz and SecHack. Around May 29 they used a historian server and those credentials to reach an engineering workstation, and they reached the SIS engineering workstations over RDP, where they installed a backdoor[1]. From there the TRITON framework spoke TriStation, Schneider Electric’s proprietary protocol, which Mandiant says the adversary appears to have reverse-engineered, and downloaded attacker code to the Triconex controllers[2].
On June 2, 2017, the implanted malware accidentally shut down one SIS controller, which halted refinery operations. Schneider Electric engineers attributed the event to a mechanical failure, and the refinery resumed after seven days. The attackers then had another two months of access[1]. At 7:43 PM on August 4, the controllers started a safe shutdown after “the application code between redundant processing units failed a validation check.” Six Triconex controllers initiated it, part of the complex went offline, and Petro Rabigh officials announced the outage resolved on August 14[1][6].
Dragos and FireEye disclosed the malware in December 2017 without naming the victim[7][2]. E&E News named Petro Rabigh in March 2019, drawing on documents and interviews, many with anonymous sources[6]. INL reports Dragos’s view that the way the six controllers were targeted could have caused major physical damage and loss of human life[1]. Mandiant assessed with moderate confidence that the attacker shut the plant down by mistake while developing the ability to cause physical damage[2].
Intent: malicious
The intrusion was deliberate and staged over months[1]. The US Department of Justice says the conspirators designed Triton to prevent the refinery’s safety systems from functioning[5], and Mandiant assessed with moderate confidence that the attacker was developing the ability to cause physical damage[2]. No source documents a ransom demand or an extortion attempt.
What is not established is what the final stage was meant to do. The shutdowns that did occur appear to have been accidental: the malware tripped the safety controllers before any further manipulation ran[1][2].
Threat actors: a Russian state institute
Attribution matured over several years and first pointed elsewhere. In December 2017, CyberX said the malware was likely built by Iran[8]. In October 2018, FireEye assessed with high confidence that the intrusion activity was supported by Russia’s Central Scientific Research Institute of Chemistry and Mechanics (TsNIIKhM), a government-owned institute in Moscow, while saying it had no specific evidence on whether the institute developed the malware itself[3].
The US Treasury, which had designated TsNIIKhM in October 2020, said in March 2022 that it “developed the Triton malware”[4]. On March 24, 2022, the Department of Justice unsealed a June 2021 indictment of Evgeny Viktorovich Gladkikh, a programmer at an institute affiliated with Russia’s Ministry of Defense[5]. A joint advisory by CISA, the FBI and the NSA said a TsNIIKhM employee was a co-conspirator in the 2017 deployment[9]. MITRE tracks the actor as TEMP.Veles and lists XENOTIME, Dragos’s name for it, as an associated group[10].
Access vector: an exposed firewall and a VPN
INL says the attackers gained remote access to the IT network no later than May 2017 through a poorly configured, internet-exposed firewall; E&E News also says a poorly configured firewall gave them a foothold[1][6]. INL separately says the perimeter VPN was compromised during off-hours, and the poorly configured DMZ after it[1]. Both routes are shown as confirmed.
Stolen administrator credentials then carried the attackers toward the plant. INL and Mandiant both name Mimikatz and SecHack as the tools used to harvest them, and INL says the attackers used them with a historian server to reach an engineering workstation[1][11]. No source says which flaw or setting in the firewall was abused, or when the VPN was compromised.
IT impact: footholds and tools on the IT network
The IT network was a route, not a target. INL describes credential-harvesting tools, Cryptcat-based and PLINK-based backdoors and a webshell[1]. Mandiant, describing the actor across its intrusions rather than this site alone, says a Cryptcat-based backdoor established the initial foothold, webshells were planted on Outlook Exchange servers, and the actor made heavy use of RDP, PsExec, WinRM and SSH-based tunnels[11]. Malware is shown as confirmed for that reason.
No source describes data being encrypted, destroyed or stolen, or IT systems being taken down. How the Outlook Exchange servers were reached is not known.
OT targeting: a direct compromise of the safety system
The attackers reached the safety layer itself. From the SIS engineering workstation, the TRITON framework, in a file named trilog.exe to masquerade as a Triconex application, used the TriStation protocol to reprogram the controllers and deployed two payload files, inject.bin and imain.bin[2]. On the controllers, the injector used a firmware vulnerability to gain supervisor privileges[1].
Schneider Electric said this was a zero-day in the Tricon firmware and that the victim ran version 10.3[12]. CISA’s advisory ICSA-18-107-02 lists two flaws, CVE-2018-8872 and CVE-2018-7522, in firmware versions 10.0 to 10.4[13]. Dragos’s first report had said the malware used no inherent vulnerability in Schneider Electric products; the vendor’s later finding supersedes it[7]. INL’s account of a route from a historian server to the safety engineering workstations suggests little effective separation between the process control network and the safety network[1].
OT sophistication: sophisticated
The adversary appears to have reverse-engineered an undocumented, proprietary safety protocol[2], used a firmware flaw in the safety controllers that the vendor called a zero-day, and injected a remote access trojan into the controllers’ memory[12]. MITRE lists Loss of Safety among the malware’s designed capabilities[14]. That is deep, specific engineering knowledge aimed at the most safety-critical asset in the plant.
Sophistication is judged here on demonstrated technique and intent, not on whether the final payload ran. It did not: in Mandiant’s assessment, the August shutdown was a mistake[2]. Sophisticated capability and successful sabotage are different findings, and in this incident they part ways.
OT impact: safety trips, and a capability not carried out
What happened on the controllers is confirmed. INL lists a service stop under Inhibit Response Function: on August 4, an updated version of Triton installed on one controller spread to other SIS controllers and caused the fault behind the second shutdown. INL does not say which service was stopped[1]. Mandiant says some controllers entered a failed safe state, which automatically shut down the industrial process[2].
Loss of Safety is shown as reported. MITRE lists it as a capability of the malware, and the Department of Justice says Triton was designed to stop the safety systems working[14][5]. INL lists no safety-logic manipulation as observed, and no source establishes whether the safety logic was ever changed to disable a trip[1].
Perils: none
No physical event occurred. Both trips took the process to a safe state. INL says the August shutdown took part of the complex offline to prevent a gas release, and no source reports fire, explosion, release, injury or equipment damage[1]. The map shows No Perils.
The potential was far larger. INL reports Dragos’s view that the targeting could have caused major physical damage and loss of human life, and Dragos’s own report lists equipment damage, system downtime and potentially loss of life among potential impacts[1][7]. The loss that did occur is business interruption, not a peril.
The attacker reached the plant’s last line of defense, and that line’s own redundancy check is what took the plant to safety.
Financial losses: what it cost
The only disclosed figure is about $938,000 in lost revenue for the 10-day August shutdown. INL gives it, citing Petro Rabigh’s unaudited 2017 financial information, which has not been retrieved for this analysis, and shows no method[1]. No source costs the June shutdown, the response, the restart or the safety review, so $938,000 is a partial floor, not a total.
At least six controllers were compromised, and Schneider Electric said it planned to “re-burn and re-flash” affected controllers once updated firmware was ready. No source gives that cost[6][12].
Loss evidence
- Confirmed: Lost revenue during the August shutdown; Lost revenue during the June shutdown (unpriced by any source); Embedded device replacement (compromised Triconex controllers)
- Reported amounts: $938,000 Lost revenue during the 10-day August 2017 shutdown, according to INL citing Petro Rabigh’s financial information[1]
- Estimated: $657,000 Lost revenue during the seven-day June 2017 shutdown (low confidence)
- Estimate note: Our own derivation from INL’s figures[1]: $93,800 a day for August, times the seven days INL gives for June, assuming June cost revenue at the same daily rate; it is not added to the $938,000.
- Implied: Startup and return-to-service validation; Process safety engineering; Restoring control logic that carried attacker code; Server replacement; Computer and laptop replacement; Network event response and recovery; Voluntary improvements
- Not supported: Equipment repair or replacement; Loss of life; Network device replacement; Regulatory action or liability; Cyber-physical event response; Ransom extortion; Environmental damage
What this incident shows
Triton’s financial signature is the inverse of its significance: a disclosed loss under $1 million for an attack that, in Dragos’s view as INL reports it, could have cost lives[1]. The outcome turned on the safety system’s own design. Its redundant processing units caught an inconsistency and defaulted to a safe shutdown, even with attacker code on the controllers. The small loss reflects how the attack failed, not how small the risk was.
The gaps the sources describe are ordinary ones: a poorly configured firewall exposed to the internet, a compromised VPN, stolen administrator credentials, and a route from a historian server to the safety engineering workstations[1]. The June trip was diagnosed as a mechanical failure, and INL says full understanding of the attack came only in November 2017, with Dragos’s analysis. The first, physically disruptive warning went unrecognized, and the attackers kept their access for two more months[1].
References
- Idaho National Laboratory / DOE CESER CyOTE Program. “Case Study: TRITON Malware Attack Against Petro Rabigh.” CyOTE Case Study, INL/RPT-22-67981, 30 June 2022. cyote.inl.gov/content/uploads/24/2025/12/CyOTE-Case-Study_TRITON.pdf
- FireEye/Mandiant. “Attackers Deploy New ICS Attack Framework ‘TRITON’ and Cause Operational Disruption to Critical Infrastructure.” Google Cloud Blog (Threat Intelligence), 14 Dec. 2017. cloud.google.com/blog/topics/threat-intelligence/attackers-deploy-new-ics-attack-framework-triton
- FireEye/Mandiant. “TRITON Attribution: Russian Government-Owned Lab Most Likely Built Custom Intrusion Tools for TRITON Attackers.” Google Cloud Blog (Threat Intelligence), 23 Oct. 2018. cloud.google.com/blog/topics/threat-intelligence/triton-attribution-russian-government-owned-lab-most-likely-built-tools/
- US Department of the Treasury. “Treasury Targets Sanctions Evasion Networks and Russian Technology Companies Enabling Putin’s War.” Press release, 31 Mar. 2022. home.treasury.gov/news/press-releases/jy0692
- US Department of Justice, Office of Public Affairs. “Four Russian Government Employees Charged in Two Historical Hacking Campaigns Targeting Critical Infrastructure Worldwide.” Press release, 24 Mar. 2022. justice.gov/archives/opa/pr/four-russian-government-employees-charged-two-historical-hacking-campaigns-targeting-critical
- Sobczak, Blake. “The Inside Story of the World’s Most Dangerous Malware.” E&E News (POLITICO), 7 Mar. 2019. eenews.net/articles/the-inside-story-of-the-worlds-most-dangerous-malware/
- Dragos. “TRISIS Malware: Analysis of Safety System Targeted Malware.” 13 Dec. 2017, mirror hosted by the US Senate Committee on Energy and Natural Resources. energy.senate.gov/services/files/40B2ED59-D34E-47C3-B9E2-1E8D030C5748
- Kovacs, Eduard. “Iran Used ‘Triton’ Malware to Target Saudi Arabia: Researchers.” SecurityWeek, 15 Dec. 2017. securityweek.com/iran-used-triton-malware-target-saudi-arabia-researchers
- CISA, FBI and NSA. “Tactics, Techniques, and Procedures of Indicted State-Sponsored Russian Cyber Actors Targeting the Energy Sector.” Joint Cybersecurity Advisory AA22-083A (PDF), 24 Mar. 2022. cisa.gov/uscert/sites/default/files/publications/AA22-083A_TTPs_of_Indicted_State-Sponsored_Russian_Cyber_Actors_Targeting_the_Energy_Sector.pdf
- MITRE. “TEMP.Veles, Group G0088.” MITRE ATT&CK. attack.mitre.org/groups/G0088/
- FireEye/Mandiant. “TRITON Actor TTP Profile, Custom Attack Tools, Detections, and ATT&CK Mapping.” Google Cloud Blog (Threat Intelligence), 10 Apr. 2019. cloud.google.com/blog/topics/threat-intelligence/triton-actor-ttp-profile-custom-attack-tools-detections
- Higgins, Kelly Jackson. “Schneider Electric: TRITON/TRISIS Attack Used 0-Day Flaw in its Safety Controller System, and a RAT.” Dark Reading, 18 Jan. 2018. darkreading.com/vulnerabilities-threats/schneider-electric-triton-trisis-attack-used-0-day-flaw-in-its-safety-controller-system-and-a-rat
- CISA (NCCIC/ICS-CERT). “Schneider Electric Triconex Tricon (Update B).” ICS Advisory ICSA-18-107-02. ics-cert.us-cert.gov/advisories/ICSA-18-107-02
- MITRE. “Triton, Software S1009.” MITRE ATT&CK. attack.mitre.org/software/S1009/


