Join our Newsletter — 33% off our NHI Course
Home› Guides› ICS Malware History Guide: Lessons from Stuxnet to…
Guide OT & IoT Security

ICS Malware History Guide: Lessons from Stuxnet to FrostyGoop

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, edited by Lalit Choda Updated 27 October 2026 11 min read
On this page

Only a handful of malware families have ever been built to manipulate industrial processes, and each one exposed a defensive gap that many plants still have today. This guide walks through the ICS-specific families that MITRE ATT&CK for ICS tracks as software objects, from Stuxnet in 2010 to FrostyGoop in 2024, and turns each one into concrete detection and hardening lessons. It deliberately avoids attribution debates and attacker procedures: the point is what defenders of PLCs, safety controllers, substations and engineering workstations should change. It is written for OT security engineers, control system engineers and SOC analysts who cover industrial networks.

Key takeaways

  • Legitimate functions are the weapon. Almost every family abused normal engineering operations: program download (T0843), parameter writes (T0836) or industrial protocol commands, not exotic exploits.
  • The engineering workstation is the pivot. Stuxnet, Triton and INCONTROLLER all depended on a Windows host that was trusted to programme controllers.
  • Safety and view are targets, not side effects. Triton aimed at Loss of Safety (T0880) and Industroyer at Loss of View (T0829) and Loss of Protection (T0837).
  • Protocol-aware monitoring catches what antivirus misses. Unexpected Modbus writes, IEC-104 commands or logic downloads are the most reliable signal across the whole history.
  • Recent families are simpler and more reachable. FrostyGoop, Fuxnet and IOControl worked against internet-reachable or lightly protected devices, so basic exposure reduction still pays the most.

How the attack works

ICS-specific malware differs from IT malware in what it is trying to achieve. Ransomware such as EKANS (S0605) or LockerGoga (S0372) stops production by encrypting Windows hosts; ICS-specific families go one step further and talk to controllers, field devices or safety systems in their own protocols. ATT&CK for ICS describes this as a chain that usually runs through the same stages.

  1. Access to the operational network: via removable media (T0847), supply chain compromise of vendor software (T0862), remote services (T0886), external remote services (T0822) or an internet accessible device (T0883).
  2. Discovery of the process: remote system discovery (T0846), network sniffing (T0842), point and tag identification (T0861) and remote system information discovery (T0888) to learn which controller does what.
  3. Gaining control authority: valid accounts (T0859), hardcoded credentials (T1694.002) or exploitation for privilege escalation (T0890), often on the engineering workstation.
  4. Changing the process: program download (T0843), modify program (T0889), modify controller tasking (T0821), change operating mode (T0858), modify parameter (T0836), or crafted command messages (T1692.001).
  5. Hiding and inhibiting response: manipulation of view (T0832), manipulate I/O image (T0835), rootkit (T0851), indicator removal on host (T0872), service stop (T0881) and data destruction (T0809) to slow recovery.

The lesson for defenders is that stage 4 almost always uses functions the asset owner also uses. Controls must distinguish authorised from unauthorised use of the same function, which is why change management, controller key switches and monitoring of engineering protocol traffic matter so much.

Where it shows up: the families in order

The table lists the families that ATT&CK for ICS v20 records as software with ICS technique mappings. Dates and descriptions come from the ATT&CK software entries.

Family (ATT&CK ID)First publicTargetKey ICS behaviourDefensive lesson
Stuxnet (S0603)2010 (components from 2008)Siemens S7 PLCs via Step 7 project filesInfected project files (T0873.001), modified PLC code (T0889), replayed normal I/O to operators (T0832, T0835)Air gaps fail through removable media; verify controller logic against a known-good copy
Havex / Backdoor.Oldrea (S0093)2013 onwardsEnergy companiesDelivered through trojanised vendor software (T0862); enumerated OPC servers and tags (T0861)Verify hashes and signatures of vendor downloads before they reach OT
BlackEnergy (S0089) with KillDisk (S0607)2015 Ukraine grid attackDistribution operatorsSpearphishing (T0865), valid accounts (T0859), then operators' own remote tools used to open breakers; disks wipedPhishing-resistant MFA on OT remote access; protect HMIs from IT credentials
Industroyer / CRASHOVERRIDE (S0604)2016Electrical substationsSpoke grid protocols directly, including serial COM (T1695.001); denial of view and protection (T0815, T0837); wiped hosts (T0809)Baseline IEC-104 and IEC 61850 traffic; alert on commands from new sources
Triton / TRISIS (S1009)2017Triconex safety instrumented system controllersDetected operating mode (T0868), uploaded and downloaded SIS programs (T0845, T0843), modified firmware (T1693.001), aimed at Loss of Safety (T0880)Keep SIS keys in RUN, isolate SIS engineering, treat any SIS program change as an incident
Industroyer2 (S1072)2022 (sample compiled March 2022)High-voltage substationsHard-coded IEC-104 targets, brute force I/O (T0806), service stop (T0881)Discovered before execution: protocol monitoring and hunting work
INCONTROLLER / PIPEDREAM (S1045)2022Schneider Electric and Omron PLCs, OPC UA servers, CODESYSDevice discovery, logic download, credential brute force, vulnerable driver on Windows hosts (T0890)Harden engineering workstations; OPC UA application authentication and trust lists
Fuxnet (S1157)2024Sensor gateways for Moscow utility infrastructureExternal remote services (T0822), internet accessible devices (T0883), data destruction and loss of view (T0809, T0829)Remove internet exposure; keep spare devices and firmware images
FrostyGoop (S1165)2024District heating controllers in UkraineRead and wrote Modbus TCP holding registers on port 502 (T0836, T0885)Modbus has no authentication: block port 502 at boundaries and monitor writes
IOControlRecent (ATT&CK v20)Linux ARM IoT and OT devices, including PLC/HMIs and fuel management systemsPort scanning (T0846.001), MQTT style publish/subscribe and DNS based command channels (T0869.002, T0869.001)Inventory embedded Linux devices and restrict their outbound traffic

PLC-Blaster (S1006) is a proof-of-concept worm that runs on Siemens S7 PLCs. It is not an in-the-wild family but it showed that controller-resident code can spread from PLC to PLC, which is why controller integrity checking matters even without a compromised workstation.

Impact

The impacts in ATT&CK for ICS describe consequences for the physical process, not for data. Mapping each family to its impact helps prioritise which controls protect which outcome.

Impact (ATT&CK)FamiliesWhat it means for the plantPrimary mitigation
Manipulation of View (T0832)Stuxnet, IndustroyerOperators see normal values while the process is not normalIndependent process measurements, controller logic integrity checks
Loss of View (T0829), Denial of View (T0815)Industroyer, FuxnetHMI or SCADA cannot show state, so operators lose situational awarenessData Backup (M0953), manual operation procedures, spare HMIs
Loss of Protection (T0837)IndustroyerProtective relays may not act on a faultNetwork Allowlists (M0807) on relay networks, relay setting audits
Loss of Safety (T0880)TritonThe safety system may not trip when a hazard developsPhysical key in RUN, separate SIS network, Audit (M0947) of SIS logic
Denial of Control (T0813), Manipulation of Control (T0831)Industroyer, StuxnetOperators cannot command, or commands do the wrong thingAuthorization Enforcement (M0800), Software Process and Device Authentication (M0813)
Data Destruction (T0809)Industroyer, INCONTROLLER, Fuxnet, KillDiskHosts and devices must be rebuilt before recovery can startOffline golden images and controller backups

The 2015 and 2016 Ukrainian grid attacks are instructive: power was restored by operators switching manually, which only worked because staff still knew how. CISA lists the ability to operate OT systems manually as one of its five primary OT mitigations.

Detection

Signature detection has a poor record against these families because most are bespoke. Behavioural detection on the network and on engineering hosts works far better.

  • Engineering protocol use from unexpected hosts: alert on program download, upload, mode change or firmware update commands (S7comm, TriStation, CODESYS, FINS, Modbus function codes 5, 6, 15, 16) from any host not on the approved engineering workstation list.
  • Write commands outside change windows: Modbus register writes, IEC-104 control commands or DNP3 operate commands outside an approved work order are high-fidelity events.
  • New talkers and new protocols: a baseline of who talks to whom (zones and conduits) makes Industroyer-style scanning and port scans (T0846.001) visible.
  • Controller state changes: poll controllers for operating mode, key switch position and program checksum; a change without a ticket is an incident. Triton's need to detect operating mode (T0868) is exactly what a monitored RUN key defeats.
  • Engineering workstation telemetry: unusual driver loads (CISA's PIPEDREAM advisory calls out the ASRock driver AsrDrv103.sys), new Python interpreters, modified project files and removable media use.
  • Outbound connections from embedded devices: MQTT, DNS tunnelling or any direct internet traffic from PLCs, HMIs, cameras or gateways.

Metrics that show coverage is working: percentage of controllers with monitored program checksums; percentage of OT zones with passive protocol monitoring; mean time to review an unauthorised write or download alert; number of engineering workstations outside the allowlist; and count of OT devices reachable from the internet (target zero). See the OT Network Security Monitoring Guide.

Prevention and hardening

Each family maps to a small set of ATT&CK for ICS mitigations. The table is ordered by how many families each control would have disrupted.

ControlATT&CK mitigationFamilies disruptedPractical form
Segmentation and boundary filteringNetwork Segmentation (M0930), Filter Network Traffic (M0937)AllZones and conduits, IT/OT DMZ, block port 502 and engineering protocols across boundaries
Only approved hosts may programme controllersNetwork Allowlists (M0807), Authorization Enforcement (M0800)Stuxnet, Triton, INCONTROLLER, Industroyer2Controller access lists, CPU protection levels, key switches in RUN
Hardened engineering workstationsExecution Prevention (M0938), Exploit Protection (M0950), Antivirus/Antimalware (M0949)Stuxnet, Triton, INCONTROLLERApplication allowlisting, vulnerable driver blocklist, HVCI, no email or web
Strong, unique credentials and MFA for remote accessHuman User Authentication (M0804), Privileged Account Management (M0926)BlackEnergy, Fuxnet, INCONTROLLERPhishing-resistant MFA, no shared vendor accounts, default passwords changed
Signed software and verified downloadsCode Signing (M0945)Havex, StuxnetHash checks against vendor publications, signed firmware where supported
Integrity audit of logic and firmwareAudit (M0947)Stuxnet, Triton, PLC-BlasterScheduled comparison of controller programs with the master copy
Offline backups and rebuild capabilityData Backup (M0953)Industroyer, Fuxnet, KillDisk, INCONTROLLERGolden images for HMIs and workstations, controller project archives offline

Lessons from incidents

  • Stuxnet: an isolated network is still reachable by people, laptops and USB drives. Removable media control and project file integrity are not optional.
  • 2015 Ukraine grid: the intruders used the operators' own remote access and HMI tools. Identity controls on OT remote access are process safety controls.
  • Triton: the attack was discovered when safety controllers tripped the process to a safe state. Investigating every unexplained SIS trip is a detection control.
  • Industroyer2: a scheduled grid attack was found before it executed, which shows that hunting on IEC-104 activity and incident readiness can change outcomes.
  • FrostyGoop: ordinary Modbus commands were enough to disrupt heating for civilians. Protocols without authentication need network-level authorisation.
  • IT ransomware reaches OT too: plants shut down when shared IT services fail, as the Colonial Pipeline Ransomware Attack showed with a single unused VPN account.

Practitioner checklist

  • Confirm no PLC, HMI, gateway or safety controller is reachable from the internet, and re-check monthly.
  • Publish an allowlist of engineering workstations and enforce it on controllers and at conduits.
  • Keep safety controller keys in RUN and log every change of key position or mode.
  • Compare controller logic and firmware with master copies on a schedule and after every intervention.
  • Deploy passive protocol monitoring with alerts on downloads, mode changes and writes outside work orders.
  • Harden engineering workstations with application allowlisting and a vulnerable driver blocklist.
  • Replace default and shared credentials on controllers, OPC UA servers and remote access tools.
  • Hold offline golden images and controller backups, and rehearse manual operation of critical processes.

Standards and references

Related NHI Mgmt Group resources: Top 10 OT Security Risks · MITRE ATT&CK for ICS Guide · PLC Security Guide · OT Incident Response Guide

PDF for subscribers

Take this guide with you

Every section, table and checklist in one PDF, with links to the sources and related guides. Subscribe to our weekly NHI & AI Identity Journal and we’ll email you a download link.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Researched and written by the NHI Mgmt Group editorial team using AI tools, under the editorial direction of Lalit Choda. Facts are drawn from the sources listed on this page and checked by our automated quality process. Last updated 27 October 2026. Spotted an error? Use our contact page.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM and Agentic AI security. nhimg.org

PDF Downloads for Newsletter Subscribers

Get the guide

Enter your details and we’ll email you a download link.

The full guide is free to read online. The PDF is a thank you for subscribing.

Fill in all fields marked * and tick the PDF box to continue.