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

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

How the Stuxnet Attack Worked

Stuxnet was malware discovered in 2010 that crossed from Windows systems into Siemens controllers and physically damaged uranium enrichment centrifuges while showing operators normal readings.

Illustration for the cybersecurity term Stuxnet
Home / Blog / Cybersecurity Terms / How the Stuxnet Attack Worked
17 November 2026

How the Stuxnet Attack Worked

How the Stuxnet Attack Worked

In June 2010 a small Belarusian antivirus firm, VirusBlokAda, investigated machines in Iran that kept rebooting. What they found became the most consequential piece of malware ever written. Stuxnet did not steal data or extort money. It reached into an industrial process and broke physical equipment, then lied to the people watching the screens.

Getting In

The target, understood to be the uranium enrichment facility at Natanz, had no internet connection. Stuxnet was built for that constraint. It spread on removable drives, exploiting a vulnerability in how Windows rendered shortcut files, CVE-2010-2568, which executed code as soon as a folder was viewed — no double-click required. Once on a network it moved using a print spooler flaw, CVE-2010-2729, and an SMB vulnerability, and escalated privilege through two further unpatched flaws in keyboard layout handling and the task scheduler. Four zero-days in a single sample was, and remains, extraordinary.

Its drivers were signed with legitimate code-signing certificates stolen from two Taiwanese hardware companies, Realtek Semiconductor and JMicron, whose offices sat in the same business park. Signed drivers loaded without complaint, which is why the rootkit hiding the infection went unnoticed for so long.

Finding the Right Plant

Stuxnet infected an estimated 100,000 hosts worldwide and damaged almost none of them. It was fiercely selective. The payload activated only where it found Siemens Step 7 project software and, beneath it, a specific configuration: Siemens S7-315 and S7-417 controllers driving arrays of frequency converter drives from two particular manufacturers, Fararo Paya in Iran and Vacon in Finland, running at between 807 Hz and 1,210 Hz. Those frequencies have essentially one civilian use: gas centrifuges.

If the fingerprint did not match, the malware remained dormant. That targeting discipline is why the operation stayed hidden for years despite enormous collateral spread.

What It Did to the Process

On a matching system, Stuxnet replaced a Siemens library file, s7otbxdx.dll, used by the engineering software to talk to controllers. From that position it could intercept every exchange between the engineering station and the PLC. It injected new code blocks into the controller and then hid them: when an engineer uploaded the program to inspect it, the malware returned the original, clean version.

The injected logic ran a slow sabotage cycle. For weeks it did nothing but record normal process values. Then it drove the centrifuge drives to around 1,410 Hz, far above their operating speed, before dropping them to 2 Hz and returning to normal. While this happened, the recorded normal readings were replayed to the monitoring systems, so operators saw an untroubled plant. Rotors were stressed to failure. The Institute for Science and International Security estimated that roughly 1,000 of about 9,000 centrifuges at Natanz were replaced during the relevant period, and because the failures looked like poor manufacturing quality, the engineers blamed their suppliers.

Why It Still Shapes OT Security

Stuxnet also set a precedent governments now live with. Once a state demonstrates that code can destroy machinery, the technique belongs to everyone who can afford to study it.

At Privia Security, our OT-SCADA Penetration Test examines exactly the paths Stuxnet used: removable media, engineering workstations, and the integrity of what your controllers are actually running.

FAQ – Frequently Asked Questions

Who Created Stuxnet?

No government has formally claimed it. Reporting by The New York Times and others, drawing on officials familiar with the operation, attributed it to a joint United States and Israeli programme reportedly known as Olympic Games. The technical evidence — four zero-days, stolen certificates, and detailed knowledge of a specific facility — is consistent with state resources.

Could Stuxnet Still Work Today?

The specific exploits are long patched and the payload targeted one configuration that no longer exists. The method remains entirely viable: removable media entering a plant, a compromised engineering workstation, unauthenticated controller programming, and falsified operator displays are all still present in many industrial environments today.

How Was Stuxnet Finally Discovered?

Through a side effect rather than its payload. Machines in Iran were crashing and rebooting, and VirusBlokAda investigated in June 2010. Researchers at Symantec, Kaspersky, and independently Ralph Langner then reverse-engineered the sample, and it was Langner’s team that identified the Siemens controller payload and its centrifuge target.

What Should My Plant Take From Stuxnet?

Three things: control removable media and the laptops that carry it, treat engineering workstations as your most sensitive assets with dedicated hardened builds, and verify independently that controllers are running the logic you approved. Each is achievable without new technology, and together they address the method rather than the specific malware.

Related Terms

You May Be Interested In These

How Do You Collect Cloud Compliance Evidence?

Cybersecurity Terms

17 November 2026

How Do You Collect Cloud Compliance Evidence?

Read More
What Is a MAC Address?

Cybersecurity Terms

30 March 2021

What Is a MAC Address?

Read More
What Is Unconstrained Delegation Abuse?

Cybersecurity Terms

17 November 2026

What Is Unconstrained Delegation Abuse?

Read More