Skip to content

Attack encyclopedia

TRITON (TRISIS) - the malware that attacked systems designed to protect human life

TRITON/TRISIS - analysis of the most dangerous ICS malware in history. Attack on SIS in a Saudi refinery (2017), MITRE ATT&CK S1009 techniques, TEMP.Veles/CNIIHM attribution.

Józef SulwińskiJózef Sulwiński

Published 10 min read

TRITONTRISISHatManS1009SISSafety Instrumented SystemsSchneider ElectricTriconexTEMP.VelesICS malwareMITRE ATT&CK
TRITON (TRISIS) - the malware that attacked systems designed to protect human life
Contents
  1. What is a Safety Instrumented System and why compromising one can kill
  2. Anatomy of the attack - from the corporate network to the safety controller
  3. The bug that saved lives
  4. TRITON in MITRE ATT&CK for ICS
  5. Who is behind TRITON - TEMP.Veles and CNIIHM attribution
  6. Why TRITON changed the perception of industrial cybersecurity
  7. Summary
  8. Sources

August 2017. Somewhere in the Middle East, at one of Saudi Arabia’s largest petrochemical refineries, night-shift operators notice something alarming on their monitors. The safety system - the one that should immediately shut down the plant in an emergency before an explosion occurs - suddenly trips into safe shutdown mode. Production stops. For a while, nobody understands why. Controllers are operating correctly, no process anomaly has been detected. A few hours later the plant returns to operation. The incident is logged as an unexplained fault.

Nobody yet knows that this “fault” has just saved lives. And that in a few months the world will learn of a piece of malware whose goal was neither data theft nor ransom - but stripping a refinery of its last line of defense against an industrial catastrophe.

What is a Safety Instrumented System and why compromising one can kill

To understand what makes TRITON unique, you first need to understand what it attacked.

A Safety Instrumented System (SIS) is an independent safety automation layer whose sole purpose is to protect people, plant equipment, and the environment. The SIS runs in parallel with the basic process control system (DCS/BPCS) but is physically and logically separated from it. When sensors detect conditions that threaten safety - excessive pressure, temperature, or gas concentrations - the SIS takes automatic action: closes valves, shuts down pumps, activates fire suppression systems. It is the last barrier between normal operation and catastrophe.

In a petrochemical refinery processing hydrocarbons, sulfuric acid, and hydrogen sulfide (H2S), a SIS failure at a critical moment can mean:

  • Uncontrolled pressure build-up leading to reactor rupture
  • Release of toxic hydrogen sulfide - a gas lethal at concentrations of 100 ppm
  • Explosion and fire in facilities handling flammable materials

SIS are designed to comply with IEC 61511, with required Safety Integrity Levels (SIL) from 1 to 4. Schneider Electric’s Triconex controllers, deployed at the Saudi refinery, are among the most widely used SIS devices in the world - they operate in thousands of installations across the petrochemical, energy, and gas sectors.

TRITON was the first malware in history deliberately designed to attack systems whose purpose is protecting human life.

Anatomy of the attack - from the corporate network to the safety controller

Phase 1: IT network infiltration and pivot to OT

The attackers gained access to the corporate network at least a year before the attack on the SIS. They likely used spearphishing or compromised remote access services. From the IT network they moved laterally into the OT network, ultimately taking control of an engineering workstation connected to the SIS controllers.

The engineering workstation ran Windows and had TriStation software installed - Schneider Electric’s tool for programming and configuring Triconex controllers. This workstation became the foothold for the attack on the SIS.

Phase 2: Reverse engineering the TriStation protocol

TriStation is a proprietary Schneider Electric communication protocol running on UDP port 1502. It is used to transfer programs, configurations, and diagnostic commands between the engineering workstation and Triconex controllers. The protocol was not publicly documented.

The attackers had to reverse-engineer it - analyze network traffic, understand packet structures, and implement their own communication library. This fact alone speaks to the resources and time at their disposal - this is not the work of a lone hacker, but of a team with access to Triconex hardware and months of research budget.

Phase 3: The TRITON framework

TRITON is not a single file - it is a modular attack framework consisting of several components:

Component Function
trilog.exe Dropper masquerading as a legitimate Triconex log analysis tool (trilog.exe). A Python script compiled into a Windows executable
inject.bin PowerPC shellcode - an injector exploiting a zero-day vulnerability in Triconex firmware to escalate privileges and inject a backdoor
imain.bin Implant (backdoor) - code residing in the controller’s firmware memory, giving attackers the ability to read, write, and execute code on the controller
TriStation library Custom implementation of the TriStation protocol enabling communication with controllers

The framework allowed the attackers to:

  • Read and write controller memory
  • Modify SIS program logic
  • Change the controller’s operating mode (from RUN to PROGRAM)
  • Upload custom code to firmware

Phase 4: Attack on the Triconex controllers

The ultimate objective was to upload the backdoor (imain.bin) into the firmware memory of Triconex controllers managing the Sulfur Recovery Units and combustion management systems. The backdoor was meant to provide persistent, covert access to the controllers - independent of the normal programming process.

The attackers exploited a zero-day vulnerability in the Triconex firmware - a flaw enabling privilege escalation that allowed code to be written not to standard user memory but to the firmware memory region. This is a critical distinction: code in firmware memory survives controller restarts and is far harder to detect.

The bug that saved lives

And here we reach the moment that changed the course of events.

The malware contained a bug in its validation code. During the attempt to inject the backdoor into one of the controllers, the code failed an internal firmware integrity check. The Triconex controller - designed to favor safety over operational continuity in any questionable situation - transitioned to a fail-safe state.

This was the “unexplained” shutdown from August 2017.

Had the malware worked correctly, the attackers would have gained persistent, covert access to the safety controllers. They could then - in coordination with an attack on the DCS - have disabled the safety systems at the moment the plant needed them most. The scenario of a deliberate industrial catastrophe - an explosion, release of toxic gases, fire - would have become real.

As researchers from Mandiant later determined, the malware contained a conditional check that prevented payload persistence. After correcting that code fragment, the backdoor persisted in the controller’s memory as intended. In other words: had the attackers fixed one condition in their code, the controller would not have detected the intruder.

TRITON in MITRE ATT&CK for ICS

MITRE ATT&CK catalogs TRITON as software S1009, and the entire incident as campaign C0030. The table below presents the key ICS techniques used by TRITON.

Tactic Technique ID Application in the TRITON attack
Execution Change Operating Mode T0858 Changing the controller mode from RUN to PROGRAM to enable uploading new code
Execution Native API T0834 Using native Triconex controller API functions for communication
Persistence System Firmware T0857 Injecting the backdoor into the firmware memory region (not user memory)
Persistence Modify Program T0889 Modifying the user program in the SIS controller
Evasion Masquerading T0849 The trilog.exe file masquerading as a legitimate Schneider Electric tool
Inhibit Response Function Block Command Message T0803 Ability to block safety commands to the controller
Inhibit Response Function Modify Parameter T0836 Modifying SIS controller configuration parameters
Lateral Movement Program Download T0843 Downloading (uploading) a new program to the controller via TriStation
Impair Process Control Modify Controller Tasking T0821 Altering control logic in the safety controller

The full list of techniques, including IT techniques used during the corporate network infiltration and lateral movement phases, is available on the C0030 campaign page in MITRE ATT&CK. For more on how to use the ATT&CK framework in practice, see our article MITRE ATT&CK - how to use the framework to protect your organization.

Who is behind TRITON - TEMP.Veles and CNIIHM attribution

FireEye (now Mandiant/Google Cloud) tracked TRITON-related activity under the designation TEMP.Veles. In October 2018, Mandiant published an attribution analysis in which it linked TEMP.Veles activity with high confidence to the Central Scientific Research Institute of Chemistry and Mechanics (CNIIHM, Russian abbreviation TsNIIKhM) - a Russian research institute subordinate to the Ministry of Defense, located in Moscow on Nagatinskaya Street.

Key evidence included:

  • An IP address registered to CNIIHM, used by TEMP.Veles to monitor public reporting on TRITON, conduct network reconnaissance, and support intrusion activity
  • Personnel links - social media profiles connecting CNIIHM researchers to TEMP.Veles activity
  • Institutional capabilities - CNIIHM has declared research capabilities in industrial control systems and critical infrastructure security
  • Testing tools - traces of TRITON tool testing in an environment consistent with a research institute profile

In October 2020, the U.S. Department of the Treasury imposed sanctions on CNIIHM in connection with the institute’s role in developing TRITON malware.

It is worth noting: Mandiant did not conclusively state that CNIIHM developed the TRITON framework itself - the connection related to operational support and intrusion tools. Nevertheless, the level of sophistication of the attack - reverse engineering a proprietary protocol, a zero-day firmware exploit for the controller, a modular framework - clearly points to a state-level actor.

Why TRITON changed the perception of industrial cybersecurity

TRITON crossed a line that previous ICS attacks - even Stuxnet or BlackEnergy - had not breached. Stuxnet destroyed centrifuges but did not disable safety systems protecting people. BlackEnergy caused power outages but did not create a direct threat to operator lives.

TRITON deliberately attacked systems whose sole purpose is to prevent death and catastrophe. This shift in intent - from infrastructure destruction to potential killing - changed the way the OT industry thinks about security.

Implications for industrial organizations

1. SIS separation from DCS is not optional

One of the factors that enabled the attack was the physical or logical connection between the SIS engineering workstation and the network the attackers had accessed. The IEC 62443 standard requires network segmentation into zones and conduits - SIS should reside in a separate zone with a minimal number of connection points.

2. Monitoring communications with SIS controllers

Protocols such as TriStation were not traditionally monitored - they were treated as trusted internal channels. After TRITON, monitoring traffic to and from SIS controllers (particularly Program Download and Change Operating Mode commands) became a critical requirement.

3. Access control for engineering workstations

An engineering workstation connected to the SIS is one of the most valuable targets in an OT network. It requires multi-factor authentication, full activity logging, regular audits, and least-privilege access - principles we describe in more detail in our article on secure remote access to ICS systems.

4. Firmware integrity validation for controllers

TRITON exploited the fact that Triconex controllers did not sufficiently validate code uploaded to firmware. Schneider Electric released security updates, but the problem affects the entire industry - many SIS controller manufacturers do not implement cryptographic firmware signature verification.

5. Exercises assuming SIS compromise

Organizations should regularly test scenarios in which safety systems have been compromised. Red teaming that includes the OT layer - not just IT - is the only way to verify whether an organization can detect and respond to an attack of the TRITON class.

Summary

TRITON remains a warning. Not because the attack succeeded - paradoxically, it did not, thanks to a bug in the malware code and the controller’s correct response to an integrity violation. The warning lies in the very fact that someone invested years of work, millions of dollars, and a research team’s expertise to develop a tool capable of disabling systems that protect people from death in a refinery explosion.

The question is not “whether someone will try again,” but “when.” And whether next time the malware will be free of bugs.

Sources

  1. MITRE ATT&CK - Triton, Software S1009
  2. MITRE ATT&CK - Triton Safety Instrumented System Attack, Campaign C0030
  3. Mandiant/FireEye - TRITON Attribution: Russian Government-Owned Lab Most Likely Built Custom Intrusion Tools
  4. Mandiant - Attackers Deploy New ICS Attack Framework TRITON
  5. Schneider Electric - TRITON/TRISIS Attack Used 0-Day Flaw in Triconex SIS
  6. MIT Technology Review - Triton is the world's most murderous malware, and it's spreading
  7. CISA/FBI - TRITON Malware Remains Threat to Global Critical Infrastructure (2022)
  8. Cisco - How Does Triton Attack Triconex Industrial Safety Systems?

Need help in this area?

Our experts will help you assess the risk and plan next steps.

Talk to an expert

We'll discuss scope, methodology, and timeline.

Book a call