Stuxnet, Industroyer, TRITON: ICS Attack Case Studies
Factual case studies of Stuxnet, the 2015 and 2016 Ukraine grid attacks and TRITON: how each attack worked, mapped to ATT&CK for ICS, and the defensive lessons.
A small number of publicly documented incidents shaped how the industry thinks about ICS security. They are worth studying not for the headlines but for the mechanics: how the attackers got in, how they reached the control layer, what they did to the process, and which defenses would have made a difference.
This guide covers four of them, sticking to what primary sources (government alerts, vendor analyses and court documents) state. Each section ends with the lessons that still apply. Technique references use MITRE ATT&CK for ICS.
Stuxnet (discovered 2010)
What it was. Stuxnet was a Windows worm with a PLC payload, first publicly identified in 2010. Detailed analyses by Symantec and others showed it was built to find a very specific configuration: controllers from one vendor's S7-300 family driving frequency converters, a setup widely reported to match centrifuge cascades at Iran's Natanz enrichment facility. MITRE tracks it as software S0603.
How it spread. Stuxnet used several Windows zero-day vulnerabilities, including the LNK shortcut flaw CVE-2010-2568 that executed code when a USB drive's contents were viewed, and a print spooler flaw for network spread. It also abused a hard-coded database password in the vendor's SCADA software (CVE-2010-2772) and infected engineering project files so that opening a project on another workstation spread the infection. Its drivers were signed with stolen code-signing certificates. Removable media and project files mattered because the target network was believed to be isolated from the internet.
What it did to the process. On a matching system, Stuxnet replaced the engineering software's communication library so it could intercept and modify code going to and from the PLC. It injected its own logic into the controller, which periodically changed the frequency of the drives to stress the rotors, while hiding the modified blocks from the engineers who inspected the PLC and, according to the Symantec analysis, replaying recorded normal process values so the monitoring showed nothing unusual.
ATT&CK mapping (selection): Replication Through Removable Media (T0847), Project File Infection (T0873), Modify Program (T0889), Rootkit, Manipulation of View (T0832), Manipulation of Control (T0831), Damage to Property (T0879).
Lessons.
- An air gap is not a security control by itself. Removable media, laptops and project files cross it constantly. Control and scan transient devices, as described in OT vs IT security.
- The engineering workstation is the crown jewel. Whoever controls it can change logic and hide it. Harden, monitor and restrict it.
- Do not trust the HMI as the sole source of truth. Independent measurements and physical protections (mechanical limits, independent safety systems) catch manipulation that screens hide.
- Keep known-good copies of controller logic and compare them regularly with what is running.
Ukraine power grid, December 2015
What happened. On 23 December 2015, three Ukrainian regional electricity distribution companies suffered coordinated cyber attacks that opened breakers and caused outages affecting about 225,000 customers, according to CISA's alert IR-ALERT-H-16-056-01. Power was restored by operators switching to manual operation, and the companies ran in a constrained mode afterwards. CISA's 2021 update attributes the activity to Russian state actors, and MITRE tracks it as campaign C0028.
How it worked, per CISA:
- Initial access through spear-phishing emails with malicious Office attachments that installed BlackEnergy malware on business networks, months before the outage.
- Credential theft and pivoting to the control environment. The attackers likely used stolen legitimate credentials over VPN connections into the ICS network.
- Breaker operations through the companies' own remote administration tools and SCADA client software, so the commands looked like legitimate operator actions.
- Destruction to slow recovery: the KillDisk wiper erased files and master boot records, including on HMIs; malicious firmware was written to serial-to-Ethernet converters at substations, making them inoperable; and the attackers scheduled disconnections of server uninterruptible power supplies through their management interface.
ATT&CK mapping (selection): Spearphishing Attachment (T0865), Valid Accounts (T0859), External Remote Services (T0822), Remote Services (T0886), Graphical User Interface, Modify Firmware: System Firmware (T1693.001), Data Destruction (T0809), Loss of Control (T0827).
Lessons.
- The attackers needed no ICS zero-day. They used the operators' own tools with stolen credentials. Multi-factor authentication on every remote path into OT and strict separation of IT and OT identities would have raised the bar significantly. See secure remote access for OT vendors.
- CISA's recommendations still read like a modern baseline: application allowlisting, isolating ICS networks from untrusted networks, limiting remote access, avoiding persistent vendor connections, and planning for safe manual operation.
- Recovery depends on things nobody inventories: serial-to-Ethernet converters, UPS management cards, switch configurations. Include them in your asset inventory and keep spares and firmware images.
- The ability to run the grid manually is what limited the outage. Practice manual operations as part of OT incident response.
Ukraine transmission substation, December 2016 (Industroyer)
What happened. In December 2016, an attack on Ukraine's transmission network caused a power outage affecting part of Kyiv. In June 2017, ESET published its analysis of the malware, which it named Industroyer; Dragos named it CrashOverride, and CISA published alert TA17-163A. MITRE tracks it as software S0604 and the event as campaign C0025.
How it worked. Industroyer was a modular framework built to speak grid protocols directly instead of driving an HMI:
- payload modules for IEC 60870-5-101 (serial), IEC 60870-5-104 (TCP) and IEC 61850, plus an OPC DA module, used to map the environment and send commands that opened breakers,
- a wiper module that rendered Windows systems unusable, to hinder recovery,
- a tool exploiting a known denial-of-service vulnerability (CVE-2015-5374) in a family of protection relays, which could leave a relay unresponsive until manually reset.
CISA also notes the malware could deny service to local serial COM ports on Windows hosts.
Industroyer2. In April 2022, ESET and CERT-UA reported a new variant, Industroyer2 (S1072), deployed against a Ukrainian energy company's high-voltage substations alongside CaddyWiper and Linux and Solaris wipers. It implemented only IEC 104, with target addresses hard-coded in the binary.
ATT&CK mapping (selection): Remote System Discovery (T0846), Point & Tag Identification (T0861), Unauthorized Message: Command Message (T1692.001), Device Restart/Shutdown (T0816), Denial of Service (T0814), Loss of Protection (T0837), Data Destruction (T0809).
Lessons.
- Attackers can automate attacks that use only legitimate protocol functions. Network monitoring that understands IEC 104, IEC 61850 and similar protocols can spot new masters, unusual command sequences and scanning. See ICS protocol security.
- Protection relays are both targets and safety barriers. Patch or isolate known relay vulnerabilities and know how to restore relays manually.
- CISA's recommendations include authenticating ICS commands where possible, segmenting into enclaves, and keeping offline backups of configurations and golden images.
TRITON (TRISIS, HatMan), 2017
What happened. In 2017, attackers deployed malware against safety instrumented system (SIS) controllers at a petrochemical facility in Saudi Arabia. Some controllers detected an anomaly and moved the process to a safe state, shutting it down, which triggered the investigation. Mandiant (then FireEye) named the malware TRITON, Dragos named it TRISIS, and CISA published malware analysis report MAR-17-352-01 under the name HatMan. MITRE tracks it as software S1009 and campaign C0030.
How it worked. The affected controllers were Triconex Tricon safety controllers with MP 3008 main processors running firmware versions 10.0 to 10.4, per CISA advisory ICSA-18-107-02. The attackers had access to an engineering workstation on the safety network. Their framework, written in Python and compiled into a Windows executable, implemented the proprietary TriStation protocol used to program the controllers. It used that protocol to inject code that modified the controller firmware in memory, giving the attackers the ability to read and write memory and execute code on a safety controller. Analysts noted that such an implant could be used to disable safety functions while the process continued to run.
Attribution. In March 2022 the US Department of Justice unsealed a June 2021 indictment of a programmer at a Russian Ministry of Defense research institute, the Central Scientific Research Institute of Chemistry and Mechanics (TsNIIKhM), charging him in connection with the 2017 campaign that installed TRITON on the safety systems of a foreign refinery.
ATT&CK mapping (selection): Change Operating Mode (T0858), Program Download (T0843), Modify Firmware: System Firmware (T1693.001), Execution through API, Masquerading, Loss of Safety (T0880).
Lessons.
- The safety system is a target. It needs its own zone, with no routable path from the business network and tightly controlled engineering access. See IEC 62443 explained for zone design.
- Physical key switches matter. Keep safety controllers in RUN rather than PROGRAM and alarm on mode changes.
- An unexplained safety trip deserves a cyber hypothesis as well as a process one. Include it in your incident response triage.
Patterns across the incidents
Reading these incidents together shows a consistent picture:
| Pattern | Seen in |
|---|---|
| Entry through IT, removable media or remote access, not through the controller | All four |
| Abuse of legitimate engineering or operator functions | Stuxnet, Ukraine 2015, Industroyer, TRITON |
| Actions designed to hide or slow recovery | Stuxnet (spoofed values), Ukraine 2015 (wipers, firmware), Industroyer (wiper, relay DoS) |
| Months of preparation and reconnaissance | Ukraine 2015, TRITON |
Two further points are worth stating. First, these are rare, well-resourced operations. Most OT disruptions still come from ransomware in IT that forces a shutdown, as when a major US fuel pipeline operator halted pipeline operations in May 2021 after a ransomware attack on its business systems. Second, every one of these incidents produced public guidance that is free to use: CISA alerts, MITRE technique pages and vendor analyses. Use them to build threat scenarios for tabletop exercises and detection engineering.
References
- Symantec: W32.Stuxnet Dossier
- NVD: CVE-2010-2568 (Windows LNK vulnerability used by Stuxnet)
- NVD: CVE-2010-2772 (hard-coded SCADA database password)
- CISA IR-ALERT-H-16-056-01: Cyber-Attack Against Ukrainian Critical Infrastructure
- CISA TA17-163A: CrashOverride Malware
- ESET: Win32/Industroyer technical analysis (PDF)
- ESET: Industroyer2, Industroyer reloaded
- Mandiant: Attackers Deploy New ICS Attack Framework TRITON
- CISA MAR-17-352-01: HatMan, Safety System Targeted Malware (PDF)
- CISA ICSA-18-107-02: Schneider Electric Triconex Tricon
- US Department of Justice: Four Russian Government Employees Charged in Two Historical Hacking Campaigns Targeting Critical Infrastructure
- MITRE ATT&CK for ICS: Triton Safety Instrumented System Attack (C0030)