Skip to content
Post Mortem

Biggest cases ยท Discovered mid-2010; active from about 2009

Stuxnet: the worm built to break machines

A computer worm that quietly made uranium-enrichment machines in Iran spin wrongly while telling operators all was normal. It showed software could damage physical equipment.

CRITICALnationindustrialmalwareusb

Details may change as reporting changes. Information comes from the linked sources, and we do not guarantee it is complete or current.

Why it is on the listIt was the first widely known piece of malware designed to cause physical damage, and the template for every attack on industrial systems since.

In plain English

Most malware steals or locks data. Stuxnet was different. It looked for one very specific setup: Siemens controllers running machines that enrich uranium. If it found that setup, it changed how fast the machines spun, then replayed normal-looking readings so the operators saw nothing wrong.

It travelled on USB sticks and between Windows computers, which is how it crossed the gap into a site that was not connected to the internet. It used several Windows flaws that nobody had fixed yet, because nobody knew about them.

Everyone who studied it agrees on how it worked. Who built it has never been officially confirmed.

Words used here

PLC
A small industrial computer that runs a machine, such as a pump or a centrifuge.
Air gap
Keeping a system physically unplugged from the internet. Stuxnet showed it is not a complete defence: a USB stick can cross it.
Zero-day
A flaw the software maker does not know about yet, so there is no fix.

What happened

Symantec's detailed analysis found that the worm checked for a precise configuration that matches the Natanz enrichment plant, including the number of centrifuges in each group.

An independent institute estimated in December 2010 that around 1,000 centrifuges at Natanz may have been destroyed in late 2009 or early 2010. Iran has not confirmed that number, so treat it as an estimate.

Attribution is widely reported to be a joint US and Israeli effort, but neither government has officially confirmed it. We describe it as widely reported, not established.

How it unfolded

  1. 2009 to early 2010

    Earlier versions are active, according to later analysis.

  2. June 2010

    A security firm finds unusual malware on computers in Iran.

  3. Summer and autumn 2010

    Researchers publish how it works and what it targets.

  4. February 2011

    Symantec publishes its detailed dossier (version 1.4).

Who was affected

Mainly Iran's nuclear programme. The worm also spread to many other computers worldwide, but only did damage when it found its exact target.

What the response was

  • Antivirus companies added detection and Microsoft fixed the flaws used.
  • Industrial-control vendors and national agencies began treating cyber-physical security as its own field.

What went wrong

  • A site that relied on being unplugged did not plan for removable drives.
  • Controllers trusted software instructions without checking where they came from.
  • Operators saw fake normal readings and had no independent way to check.

What worked

  • Researchers around the world shared analysis openly, so the defence community learned fast.

What organisations should do differently

  • Treat USB drives and contractor laptops as untrusted until scanned.
  • Keep an independent measurement (a gauge or alarm that does not rely on the same software) for anything dangerous.
  • Patch known flaws. Stuxnet also used older ones that already had fixes.

What you can do today

  • Turn off autorun for removable drives on your computers.
  • Never plug in a drive you found or were handed without scanning it.
  • If you run equipment on a network, ask who can reach it and from where.

The lesson that still holds

Disconnected does not mean safe, and trusted readings can lie. Check important things a second way.

Sources

Finished this one?

Add it to What I learned and earn 40 Trust. You can open your list from the badge at the bottom of the page.