Stuxnet infected Natanz plant via carefully selected targets rather than escape from it

Posted by   Virus Bulletin on   Nov 11, 2014

Five initial victims of infamous worm named.

Today, as Wired journalist Kim Zetter publishes her book Countdown to Zero Day on Stuxnet, researchers from Kaspersky and Symantec published blog posts that shine a light on how the malware spread to its likely target, the Natanz plant in Iran, and to hundreds of thousands of other computers.

Earlier stories had suggested that Stuxnet had somehow escaped from the plant, but because Stuxnet conveniently keeps a breadcrumb log that tracks how the worm has spreaded thus far, Symantec researcher Liam O'Murchu was able to conclude that all infections originated outside the Natanz plant.

Kim Zetter - Countdown to Zero Day

A blog post by Kapsersky researchers explains how it came that the malware still spread so widely.

The infection started at five different companies and organisations in Iran, now named by Kaspersky and all closely linked to the country's nuclear program. This helped Stuxnet reach the systems at its ultimate target, which was no trivial task, given that these systems weren't connected to the Internet.

However, errors and design flaws caused the worm to spread from one of targeted companies, Behpajooh Co, to a large number of computers inside and outside Iran. It was this spreading that led to Stuxnet's discovery in the summer of 2010.

Stuxnet spreading
  The first five victims of Stuxnet. Source: Kaspersky.

Stuxnet famously was the subject of two presentations during VB2010, that saw several global affairs journalists cross the ocean to attend the conference and even led to coverage at the BBC.

Unfortunately, in 2010 we didn't record conference presentations, but Mikko Hyppönen (F-Secure) recorded Liam O'Murchu's demonstration on how Stuxnet's SCADA component was able to make centrifuges spin faster than intended. He demonstrated this by writing a program that blew up a balloon and then writing malicious code that modified the program so that it would continue to pump air into the balloon making it eventually explode.

A review of Countdown to Zero Day will appear on this website later this month.

Posted on 11 November 2014 by Martijn Grooten



Latest posts:

VB2019 paper: APT cases exploiting vulnerabilities in region-specific software

At VB2019, JPCERT/CC's Shusei Tomonaga and Tomoaki Tani presented a paper on attacks that exploit vulnerabilities in software used only in Japan, using malware that is unique to Japan. Today we publish both their paper and the recording of their…

New paper: Detection of vulnerabilities in web applications by validating parameter integrity and data flow graphs

In a follow-up to a paper presented at VB2019, Prismo Systems researchers Abhishek Singh and Ramesh Mani detail algorithms that can be used to detect SQL injection in stored procedures, persistent cross-site scripting (XSS), and server‑side request…

VB2020 programme announced

VB is pleased to reveal the details of an interesting and diverse programme for VB2020, the 30th Virus Bulletin International Conference.

VB2019 paper: Cyber espionage in the Middle East: unravelling OSX.WindTail

At VB2019 in London, Jamf's Patrick Wardle analysed the WindTail macOS malware used by the WindShift APT group, active in the Middle East. Today we publish both Patrick's paper and the recording of his presentation.

VB2019 paper: 2,000 reactions to a malware attack – accidental study

At VB2019 cybercrime journalist and researcher Adam Haertlé presented an analysis of almost 2000 unsolicited responses sent by victims of a malicious email campaign. Today we publish both his paper and the recording of his presentation.

We have placed cookies on your device in order to improve the functionality of this site, as outlined in our cookies policy. However, you may delete and block all cookies from this site and your use of the site will be unaffected. By continuing to browse this site, you are agreeing to Virus Bulletin's use of data as outlined in our privacy policy.