Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Are Industroyer and Triton?

Industroyer and Triton are the two malware families that proved purpose-built industrial attack tooling exists: one spoke grid protocols to cut electricity in Kyiv, the other reached into a plant’s safety system.

Illustration for the cybersecurity term Industroyer and Triton
Home / Blog / Cybersecurity Terms / What Are Industroyer and Triton?
17 November 2026

What Are Industroyer and Triton?

What Are Industroyer and Triton?

Only a handful of malware families have been written to manipulate industrial equipment directly rather than simply to disrupt the computers around it. Two of them appeared within a year of each other, and between them they changed how the sector thinks about the problem. Industroyer attacked electricity transmission by speaking the grid’s own protocols. Triton attacked a petrochemical plant’s safety instrumented system, the last line of defence between a process and a catastrophe.

Industroyer

On 17 December 2016, a transmission substation north of Kyiv opened its breakers and roughly a fifth of the city lost power for about an hour. Six months later, researchers at ESET published the analysis of the malware responsible, naming it Industroyer; a parallel analysis from Dragos called it CrashOverride.

What made it notable was its architecture. Rather than scripting an operator workstation, it carried four payload modules implementing industrial protocols natively: IEC 60870-5-101 for serial links, IEC 60870-5-104 for its network equivalent, IEC 61850 for substation devices, and OPC Data Access. Each module could enumerate the devices it found and issue control commands in the correct syntax, meaning the malware understood the grid rather than merely running on a computer connected to it. A data wiper destroyed system state afterwards to slow recovery, and a denial of service module exploited a known vulnerability in a family of protection relays to make them unresponsive.

Industroyer was attributed to the Sandworm group, associated with Russian military intelligence. On 8 April 2022, Ukraine’s computer emergency response team and ESET disclosed Industroyer2, a stripped-down successor with IEC 60870-5-104 configuration hardcoded rather than read from the environment, aimed at a Ukrainian energy provider and scheduled to execute at a specific time. It was found and blocked before it operated. In 2024, a further Sandworm operation against a Ukrainian heating utility used different tooling again, confirming that the capability is maintained rather than historical.

Triton

In August 2017, a petrochemical plant in Saudi Arabia shut down unexpectedly. Twice. The engineering investigation found that the plant’s safety instrumented system, a Schneider Electric Triconex controller, had tripped, and tracing why led to malware that was published in December 2017 as Triton, also called Trisis and HatMan.

The attack chain is instructive. The intruders had been inside the plant’s networks for a long period, moved from the business network to the process control network, and compromised an engineering workstation with access to the safety system. From there they used the proprietary TriStation protocol to communicate with the safety controller, exploited a previously unknown flaw to escalate privilege, and wrote an implant into the controller’s firmware memory that would let them change the safety logic at will.

The plant shut down because the attackers’ code failed a validation check inside the controller, which did exactly what a safety system should do and tripped the process. The incident was discovered because the attack was imperfect, which is an uncomfortable thing to build a defence on. The US Treasury attributed the operation in October 2020 to a Russian government research institute and imposed sanctions; the same actor was subsequently found at another critical infrastructure facility, and the FBI has warned of continued interest in safety systems.

What the Two Cases Teach

  1. Protocol-level attacks need no operator workstation. Detection that watches only Windows endpoints misses an adversary that speaks IEC 104 or TriStation. Protocol-aware anomaly detection on the wire is the control that would have seen both.
  2. The safety system is a target, not a backstop. It must sit in its own zone with its own target security level, with the controller key switch physically in the run position, and alerting on any attempt to move it to program mode.
  3. The engineering workstation is the pivot. Both operations ran through a machine that had legitimate rights to reprogram controllers. Hardening, allow-listing, separate accounts, and alerting on program downloads matter more here than anywhere else.
  4. Dwell time was long. Neither was a smash and grab. Months of reconnaissance inside the environment preceded the action, which means detection had many opportunities and took none of them.
  5. Attribution does not change the engineering. Whether the actor is a state service or a criminal group, the zone boundary, the monitoring, and the manual fallback are the same.

For UK operators, these cases sit behind the expectations of the NCSC Cyber Assessment Framework and the NIS Regulations 2018, which ask for demonstrable detection and response capability in the systems supporting an essential function rather than in the corporate estate alone. The engineering counter-measures belong in the zone and conduit model of IEC 62443, and the broader context is covered under critical infrastructure security.

At Privia Security, we test control and safety system boundaries through our OT-SCADA Penetration Test.

FAQ – Frequently Asked Questions

Did Industroyer Cause the 2015 Ukraine Blackout?

No. The December 2015 attack on regional distribution companies used BlackEnergy malware and hands-on-keyboard operation of the utilities’ own control systems, cutting supply to roughly 225,000 customers. Industroyer was used in the separate December 2016 attack on a transmission substation near Kyiv, and differed by implementing grid protocols natively rather than driving operator workstations.

Why Is Triton Considered So Serious?

Because it targeted a safety instrumented system, the independent layer that takes a process to a safe state when something goes wrong. Manipulating safety logic while the process runs normally creates the possibility of physical harm rather than only disruption. It was the first publicly documented malware designed to interfere with a safety system in a live plant.

How Was Triton Discovered?

By accident, in effect. The attackers’ code failed a validation check inside the Triconex controller, which responded by tripping the process and shutting the plant down. The engineering investigation into the unexplained trips led to the implant. Had the code been written correctly, it could have remained in place indefinitely, which is the uncomfortable part of the case.

What Single Control Addresses Both Cases?

Protocol-aware passive monitoring on the control network. Both operations produced traffic that no legitimate process would generate: enumeration and control commands in industrial protocols from unexpected sources, and engineering-mode communication with a safety controller. Endpoint tooling on Windows machines would not have seen it; a sensor parsing the industrial protocols would have.

Related Terms

You May Be Interested In These

What Are Linux Audit Logs?

Cybersecurity Terms

17 November 2026

What Are Linux Audit Logs?

Read More
What Is ARP Spoofing?

Cybersecurity Terms

17 November 2026

What Is ARP Spoofing?

Read More
What Is an IDN Homograph Attack?

Cybersecurity Terms

17 November 2026

What Is an IDN Homograph Attack?

Read More