Attack encyclopedia
Stuxnet - the first cyberattack on industrial infrastructure
Stuxnet - analysis of the first cyber weapon targeting ICS systems. Timeline, attack mechanism on Natanz centrifuges, MITRE ATT&CK ICS mapping (S0603).
Józef SulwińskiPublished 11 min read

Contents
Imagine an underground hall in Iran’s Natanz facility, 2010. Thousands of gas centrifuges spin at over a thousand revolutions per second, enriching uranium. On the SCADA operator screens everything looks normal - temperature within range, rotation stable, vibrations within acceptable limits. Except it is all a lie. The data the engineers see is a carefully crafted illusion. In reality, the centrifuges are accelerating beyond permitted parameters, then decelerating sharply. Bearings fail. Rotors warp. One by one, centrifuges break down - and nobody understands why.
This was no accident. This was Stuxnet - the first cyber weapon in history aimed at physical industrial infrastructure. A weapon that changed the rules of the game forever.
Origins - an operation without a name
The story of Stuxnet begins not in Iran, but in the offices of the White House and NSA headquarters at Fort Meade. According to reporting by the New York Times and David Sanger, the program codenamed “Olympic Games” was launched during the George W. Bush administration in 2006. The United States and Israel - specifically NSA and Unit 8200 of Israeli military intelligence - began joint work on a tool capable of sabotaging the Iranian nuclear program without declaring war.
Why a cyberattack? Because the alternatives were worse. An airstrike on the underground facilities at Natanz risked escalating the conflict to a regional scale. Economic sanctions were too slow. Diplomacy had reached a dead end. What was needed was a surgically precise tool - one that would destroy centrifuges but leave no trace.
At least, that was the plan.
Timeline of events
| Date | Event |
|---|---|
| 2005 | Development of the worm begins; Iran launches the uranium enrichment facility at Natanz |
| 2006 | The Bush administration formally launches Operation Olympic Games |
| 2007 (November) | The first known version of Stuxnet (Stuxnet 0.5) is deployed in the target environment |
| 2008-2009 | Centrifuges at Natanz begin failing en masse; Iranian engineers search for causes in mechanical defects |
| 2009 (June) | Variant 1.0 appears with expanded propagation mechanisms |
| 2010 (March) | Variant 1.1 - an even more aggressive version, likely in response to overly slow propagation |
| 2010 (June 17) | Sergey Ulasen of the Belarusian firm VirusBlokAda identifies an unknown worm on an Iranian client’s computer |
| 2010 (July 15) | Brian Krebs publishes the first widely discussed article about Stuxnet |
| 2010 (July-September) | Symantec, Kaspersky Lab, and other researchers decode the worm’s structure |
| 2010 (November) | Iran confirms that “malicious software” affected a limited number of centrifuges |
| 2012 (June) | The New York Times reveals details of Operation Olympic Games based on sources in the Obama administration |
Anatomy of the attack - how Stuxnet took control of the centrifuges
Entry vector - supply chain, not a random flash drive
The Natanz facility was isolated from the internet - a classic air-gapped network. A popular simplification says Stuxnet arrived “on a flash drive.” The reality was more sophisticated. Analysis by Kaspersky Lab and Symantec (over 2,000 samples) showed that the worm was deliberately introduced into the supply chain of five Iranian companies servicing the nuclear program:
| Company | Profile | Role in the supply chain |
|---|---|---|
| Foolad Technic Engineering (Isfahan) | Automation systems for industry | Likely the first target - infected in 2009 |
| Behpajooh (Isfahan) | Industrial automation | Infected in March 2010 - widest spread |
| Neda Industrial Group | Automation for energy and oil sectors | On the US sanctions list for illegal exports |
| Control-Gostar Jahed | Automation, metallurgy, energy | Connections to the oil sector |
| Fifth company | Automation | Details partially classified |
When engineers from these companies connected laptops or USB drives to systems at Natanz - as part of routine maintenance work - the worm transferred to stations running Step 7 software. The technical infection mechanism exploited a vulnerability in Windows .LNK (shortcut) file handling - simply viewing the contents of the drive in Windows Explorer was enough to execute code. No clicking was required.
This makes Stuxnet one of the first documented supply chain attacks on ICS infrastructure - a model later repeated with NotPetya (backdoor in Ukrainian M.E.Doc software) and SolarWinds (trojanized Orion update).
Four zero-days - an unprecedented arsenal
Stuxnet simultaneously exploited four zero-day vulnerabilities in Windows - something the industry had never seen before:
- CVE-2010-2568 - vulnerability in .LNK file processing, enabling code execution by merely displaying the icon
- CVE-2010-2729 - remote code execution via the Print Spooler service
- CVE-2010-3338 - privilege escalation through Windows Task Scheduler
- CVE-2010-3888 - privilege escalation in the Windows kernel
On top of these, there was a vulnerability in Siemens S7 controller security and an exploit known from the Conficker worm (MS08-067). In total - six attack vectors. Each one alone would have been a valuable tool. Using all of them at once pointed to an entity with nation-state resources.
Target - Siemens S7-315 and S7-417 PLCs
After taking over a workstation running WinCC/Step 7, Stuxnet did not attack every PLC it encountered. It searched for a very specific configuration - Siemens S7-315 and S7-417 PLCs connected via PROFIBUS to frequency converters manufactured by the Finnish company Vacon and the Iranian company Fararo Paya. These frequency converters drove IR-1 gas centrifuges.
When Stuxnet recognized the target configuration, it injected malicious code into the PLC’s organizational blocks (OB1 and OB35). It modified the control logic so that centrifuges operated in cycles: periodically accelerating to 1,410 Hz (above the normal 1,064 Hz), then decelerating to 2 Hz. These sudden changes in rotational speed generated mechanical stresses that led to the physical destruction of rotors.
The invisible rootkit - an illusion of normalcy
The most sophisticated element of Stuxnet was its industrial rootkit. The worm replaced the s7otbxdx.dll communication library, which handled data exchange between Step 7 software and PLCs. When an engineer tried to read the program from the controller, the rootkit intercepted the request and returned “clean” code - the original, unmodified version of the program. Operators saw correct working parameters on their screens while the centrifuges were operating in destruction mode.
Siemens made a design decision to make the process input image in the PLC read-write rather than read-only. Stuxnet exploited this - it recorded legitimate process data, then “replayed” it in a loop on the control interface, creating a perfect illusion of normal operation.
Impact - a thousand centrifuges and a new era
The Institute for Science and International Security estimated that Stuxnet may have destroyed up to 1,000 centrifuges - about 10% of those installed at Natanz - in the period from November 2009 to the end of January 2010. Iran never officially confirmed the scale of losses, although in November 2010 it admitted that “malicious software” had caused “limited problems” with centrifuges.
Stuxnet proved one fundamental thing: a cyberattack can cause physical destruction of industrial infrastructure. What had been a theoretical scenario at academic conferences until 2010 became a documented fact.
Barack Obama continued and expanded the program after taking office in 2009.
In 2010, the worm escaped beyond the controlled supply chain and began spreading globally - reaching computers in Indonesia, India, and many other countries.
Discovery - from Minsk to Hamburg
Before the world learned about Stuxnet, Iranian engineers had been appearing on Siemens technical forums reporting strange problems - instability of S7-300 controllers, unexplained WinCC software failures, computers entering restart loops. At the time, nobody suspected that these seemingly unrelated faults shared a common cause.
On June 17, 2010, Sergey Ulasen, an analyst at the Belarusian antivirus firm VirusBlokAda in Minsk, received a set of suspicious files from an Iranian client. The client’s computers were entering an infinite restart loop. Ulasen and his colleague Oleg Kupreev quickly discovered this was no ordinary virus - the code was enormous (500 KB compressed, 1.2 MB unpacked, while typical malware is 10-15 KB) and exploited an unknown zero-day vulnerability in the Windows LNK file handling mechanism. VirusBlokAda published the first warning on July 12, 2010, naming the worm “Rootkit.Tmphider.” Symantec renamed it “W32.Stuxnet.”
The discovery triggered a global race among security researchers. Dozens of teams worldwide analyzed the code, but it was Ralph Langner - an independent ICS security researcher from Hamburg - who first publicly put forward the thesis that shifted the perspective. In September 2010, Langner announced that Stuxnet was not an ordinary espionage worm - it was a cyber weapon deliberately designed to destroy Iranian uranium centrifuges. Langner identified that the malware intercepted the s7otbxdx.dll library in Siemens Step 7 software, masking PLC program modifications from operators. His analysis - conducted practically single-handedly from a small office in Hamburg - echoed around the world and earned him an invitation to speak at TED.
Langner also identified two separate payloads: one targeting S7-315 controllers managing centrifuge rotational speed (frequency converter manipulation), the other targeting S7-417 controllers managing valves in the enrichment cascades. Both operated simultaneously but independently.
MITRE ATT&CK for ICS mapping (S0603)
Stuxnet is one of the best-documented cases in the MITRE ATT&CK for ICS database. The table below presents the key techniques assigned to identifier S0603.
| Technique | ID | Description in the context of Stuxnet |
|---|---|---|
| Supply Chain Compromise | T0862 | Infection via infected USB drives and Step 7 project files |
| Exploitation of Remote Services | T0866 | Exploitation of Windows service vulnerabilities (Print Spooler, SMB) for network propagation |
| Hooking | T0874 | Interception of the s7otbxdx.dll library to mask changes in PLC code |
| Rootkit | T0851 | Rootkit hiding the worm’s presence at both the Windows OS and PLC level |
| Native API | T0834 | Use of native Siemens Step 7 API interfaces for communication with controllers |
| Modify Controller Tasking | T0821 | Modification of the PLC work cycle - changes to OB1 and OB35 blocks |
| Modify Program | T0889 | Injection of malicious code into the PLC program |
| Program Download | T0843 | Loading the modified program into the PLC |
| System Firmware | T0857 | Modification of controller firmware for persistent embedding of malicious code |
| Unauthorized Command Message | T0855 | Sending unauthorized commands to change centrifuge rotational speed |
| Data Destruction | T0809 | Physical destruction of centrifuges through manipulation of operating parameters |
The full list of techniques, including Windows-focused techniques (ATT&CK Enterprise), is available in the official MITRE documentation.
Lessons for modern OT security
Stuxnet happened over fifteen years ago, but the lessons it left behind are just as relevant today - perhaps even more so, given the ever closer connections between IT and OT networks.
1. An air gap is not a defense - it is an illusion
Natanz was isolated from the internet. It did not help - Stuxnet arrived through the supply chain. Companies servicing the facility became unwitting carriers of the attack. Every newly installed device, every maintenance engineer’s laptop, and every drive carrying a firmware update can be a potential patient zero. Supply chain control, removable media integrity verification, and application whitelisting are the absolute minimum for air-gapped networks.
2. OT network segmentation is critical
Stuxnet spread laterally through networks with flat architecture. Proper OT network segmentation - with zones and conduits defined in accordance with IEC 62443 - significantly hinders lateral movement and limits the scope of a potential breach.
3. PLC program integrity monitoring
Stuxnet was able to operate undetected because nobody verified whether the program loaded into the PLC matched the version approved by the engineer. Modern PLC code integrity monitoring solutions can detect unauthorized modifications in real time.
4. The supply chain as an attack vector
Stuxnet exploited a trusted channel - USB drives and Step 7 project files - to bypass security controls. Today’s supply chain attacks (SolarWinds, Kaseya, 3CX) follow the same pattern. Verifying the integrity of software and updates at every stage of the supply chain is a requirement, not an option.
5. OT security requires continuous monitoring
Passive monitoring of network traffic in OT networks, detection of anomalies in PLC communication, analysis of device configuration changes - these are the tools that allow detecting an attack before it causes physical damage. Stuxnet operated for months because nobody was watching.
Summary
Stuxnet is not merely a fascinating chapter in the history of cybersecurity. It is a turning point that proved computer code can destroy physical infrastructure. Since 2010, the arsenal of threats to industrial systems has continued to grow - Industroyer, Triton/TRISIS, PIPEDREAM - and each of these tools draws on the lessons that Stuxnet provided.
For organizations operating industrial infrastructure, the question is not “if” they will be attacked, but “when” - and whether their defenses will be ready.
Sources
- Stuxnet - Wikipedia
- The Real Story of Stuxnet - IEEE Spectrum
- Stuxnet explained: The first known cyberweapon - CSO Online
- Stuxnet, Software S0603 - MITRE ATT&CK
- Operation Olympic Games - Wikipedia
- Did Stuxnet Take Out 1,000 Centrifuges at the Natanz Enrichment Plant? - ISIS Reports
- Stuxnet PLC Code Injection Analysis - Industrial Monitor Direct
- Interview with Sergey Ulasen - Eugene Kaspersky's Blog
- Stuxnet Facts Report - CCDCOE
Need help in this area?
Our experts will help you assess the risk and plan next steps.