We use cookies to provide you with a better experience. If you continue to use this site, we'll assume you're happy with this. Alternatively, click here to find out how to manage these cookies

hide cookie message
 
75,052 News Articles

Stuxnet cyberweapon dates back to 2005, Symantec researchers find

Timed to hit Natanz nuclear facility in 2007

The Stuxnet cyber-weapon discovered slamming into Iran's Natanz nuclear enrichment facility in the summer of 2010 was probably in development for up to five years before that date, a new analysis by Symantec has suggested.

The evidence for this extraordinary conclusion is the discovery of an early version 0.5 development cycle that the company said ran from November 2005 to mid-2009 when the more advanced version 1.0 eventually detected by security companies took over the heavy lifting.

Domains associated with Stuxnet 0.5's command and control (C&C) network had been traced to this early date, with the same software submitted to a public scanning service two years later in November 2007.

After 4 July 2009 (is that date pure coincidence?) Stuxnet 0.5 was not used for new infections, a period that overlapped with the emergence of the more potent Stuxnet 1.0.

The dates are important because it suggests that Stuxnet's creators started work on the weapon before the Natanz facility started operation in 2007, a degree of foresight that identifies the sofwtare as surely the earliest cyberweapon yet discovered.

Intriguingly, the early Stuxnet was partly based on the 'Flame' platform, the later version on the 'Tilded' platform, which reinforces the sense researchers have been given since 2010 that there were two development teams working on different families of cyber-weapon.

These two teams produced not only Struxnet's two incarnations but a number of other cyberweapons that included Duqu, Gauss and the remarkable Flame, all discovered since Stuxnet.

Symantec's detective work confirms the fascinating extent to which Stuxnet 0.5 had been designed to reach Iranian networks not even connected to the Internet.

"To allow updates to reach these machines, Stuxnet 0.5 also used a peer-to-peer mechanism [Windows mailslot]," said Symantec.

"As long as one updated version was introduced into this network- for example through an infected USB key - all the other infected machines on the network could receive updates or new code modules."

The precise origins of Stuxnet might never be confirmed but in Symantec's view all doubt that this was a weapon designed to cause damage to nuclear centrifuges should now be discounted.

Its designers thought through how to mis-control the equipment in minute detail, according to the security firm, to the extent of trying to hide the fact that it was being made to malfunction.

"It is really mind blowing that they were thinking about creating a project like that in 2005," Symantec researcher Liam O'Murchu told Reuters in advance of the report's publication.

Feature: Iran v USA - the world's first cyberwar has started


IDG UK Sites

Samsung Gear 2 review: Classy Tizen smartwatch is too expensive

IDG UK Sites

Eight possible names for the next version of Mac OS X: What will Apple call the follow-up to Maveri?......

IDG UK Sites

Why our gadgets will kill us all: bleating notifications, too many chargers and the proliferation...

IDG UK Sites

Inside Twitter's new design and ad offerings