No government has admitted building Stuxnet, but the code itself shows it was made to wreck Iran's uranium centrifuges. Stuxnet was sabotage dressed as a glitch. A piece of malware spread through Windows machines, hunted for one specific kind of industrial controller, and then quietly changed the speed of motors spinning uranium centrifuges at Iran's Natanz plant while showing operators that all was normal. Iranian technicians replaced failing machines without knowing why. When security researchers took the code apart in 2010, they found a weapon with a single target. The operation was hidden by design: stolen certificates, unknown software flaws, and faked sensor readings kept it invisible for a year or more, and its makers have never claimed it.
The crack in Windows
On 2 August 2010 Microsoft issued an out-of-band security bulletin, MS10-046, for a critical vulnerability in the Windows Shell. The flaw let an attacker run code on a machine when a user simply viewed the icon of a specially crafted shortcut file, for example on a USB drive or network share. Microsoft rated it critical for every supported version of Windows and said it was aware of attacks already exploiting it. That shortcut flaw was how Stuxnet jumped onto machines that were never connected to the internet.
Microsoft Security Bulletin MS10-046, "Vulnerability in Windows Shell Could Allow Remote Code Execution" (2 August 2010): https://learn.microsoft.com/en-us/security-updates/securitybulletins/2010/ms10-046
Taking it apart
Symantec's W32.Stuxnet Dossier, by Nicolas Falliere, Liam O Murchu, and Eric Chien, is the fullest public dissection of the code. It calls Stuxnet a large, complex threat aimed at industrial control systems, built to reprogram programmable logic controllers and hide the changes. It describes four zero-day exploits, two stolen digital certificates used to sign its drivers, a Windows rootkit, and what the authors call the first known rootkit for a PLC. The dossier counts about 100,000 infected hosts by late September 2010, roughly 60 percent of them in Iran.
The payload was precise. Stuxnet looked for Siemens Step 7 systems controlling frequency converter drives from two specific vendors, one in Finland and one in Iran, running at very high frequencies. When it found them it altered the output frequency, raising it to 1,410 Hz, dropping it to 2 Hz, then returning it to 1,064 Hz, over a period of weeks, changing the speed of whatever motors they drove. Symantec wrote that the complexity, the zero-days, and the targeting implied a well-funded team with access to the target's equipment for testing.
Symantec (Broadcom), "W32.Stuxnet Dossier" (version 1.4, February 2011): https://docs.broadcom.com/doc/security-response-w32-stuxnet-dossier-11-en
What the inspectors counted
The International Atomic Energy Agency's report to its Board of Governors on 23 November 2010 recorded the state of Natanz in plain numbers. On 5 November 2010, 54 cascades had been installed in three of the eight planned units in Production Hall A, and 29 of them were being fed with uranium hexafluoride. Each cascade had initially held 164 centrifuges. The agency verified that 3,135 kg of low enriched uranium had been produced by 17 October 2010. The report does not mention malware; it records an enrichment plant with many installed cascades not being fed, against Security Council demands that Iran suspend enrichment.
IAEA, "Implementation of the NPT Safeguards Agreement and relevant provisions of Security Council resolutions in the Islamic Republic of Iran," GOV/2010/62 (23 November 2010): https://www.iaea.org/sites/default/files/documents/gov2010-62.pdf
Matching code to machines
In December 2010 the Institute for Science and International Security, a Washington research group led by David Albright, asked whether Stuxnet took out 1,000 centrifuges at Natanz. Using IAEA data, it reported that Iran decommissioned and replaced about 1,000 IR-1 centrifuges in late 2009 or early 2010. It compared the drive frequencies in Symantec's analysis with the IR-1's known operating speed and found that 1,064 Hz matched the machine's nominal frequency, and that the attack frequencies were likely to stress the rotors. Its authors judged the attack plausible as the cause, while noting that Iran's own problems with the IR-1 were also part of the story.
ISIS, "Did Stuxnet Take Out 1,000 Centrifuges at the Natanz Enrichment Plant?" (22 December 2010): https://isis-online.org/uploads/isis-reports/documents/stuxnet_FEP_22Dec2010.pdf
Two attacks, one goal
Ralph Langner, a control system engineer whose team was among the first to identify the target, published "To Kill a Centrifuge" in November 2013. He describes two separate attack routines. An earlier, more complex one manipulated the cascade protection system, closing valves to raise pressure inside centrifuges. A later one changed rotor speeds. He wrote that the attackers took care to avoid catastrophic damage that would reveal the attack, preferring to wear the machines down, and that operators saw recorded normal readings while the sabotage ran. In his reading the aim was to set the program back while keeping the cause hidden.
Ralph Langner, "To Kill a Centrifuge: A Technical Analysis of What Stuxnet's Creators Tried to Achieve" (November 2013), Wayback copy: https://web.archive.org/web/20250608203551/https://www.langner.com/wp-content/uploads/2017/03/to-kill-a-centrifuge.pdf
The story behind the code
In a 2014 book excerpt in WIRED, reporter Kim Zetter told how it came to light. In January 2010, IAEA inspectors at Natanz noticed centrifuges failing at an unprecedented rate, a cause unknown to the inspectors and apparently to the Iranian technicians replacing them. Five months later a security firm in Belarus was called in to troubleshoot computers in Iran that kept crashing and rebooting, found malicious files, and uncovered what Zetter calls the world's first digital weapon. The excerpt describes an early version that manipulated valves to raise pressure inside centrifuges, and cascades of 164 machines each.
WIRED, Kim Zetter, "An Unprecedented Look at Stuxnet, the World's First Digital Weapon" (3 November 2014): https://www.wired.com/2014/11/countdown-to-zero-day-stuxnet/
What was hidden, and why
What was hidden was an act of sabotage made to look like engineering failure. Its makers hid it with zero-day flaws, stolen certificates, and false readings fed to operators. Why, as the analysts read it: to slow Iran's enrichment without leaving a fingerprint.