Feeds

Israel and US fingered for Stuxnet attack on Iran

Worm tested in secret desert nuclear complex, NYT claims

Using blade systems to cut costs and sharpen efficiencies

The US and Israel jointly developed the infamous Stuxnet worm before using the sophisticated malware to sabotage key components of Iran's controversial nuclear program, according to an investigation by the New York Times.

Stuxnet selectively infects industrial control (SCADA) systems from Siemens, establishing a backdoor that creates a means to reprogram compromised systems. The worm initially spread using a battery of four zero-day Windows vulnerabilities before using insecure network shares and USB sticks to spread across networks. Windows machines can carry the infection but malware only comes into play if infected systems are used to operate certain industrial control systems.

The malware is finely tuned so that it can alter the speed of high-speed frequency converter drives, such as those used in uranium enrichment, as explained in a blog post by Symantec here. It doesn't do anything for mainstream industrial control set-ups, even after they are connected to industrial control systems.

Stuxnet began spreading in June 2009 but its sophistication, including elaborate steps to disguise its presence on infected systems, meant it was not detected until June 2010. The malware infected hundreds of thousands of systems, with most infections appearing in Iran and Indonesia.

After months of confusing and occasionally conflicting statements, Iranian president Mahmoud Ahmadinejad recently confirmed that the worm had sabotaged uranium-enrichment centrifuges at Natanz. Production at the facility reportedly dropped by 30 per cent, setting Iran's nuclear programme back by months as a result.

The consensus among anti-virus analysts, who have spent months poring over the details of the 1.5MB malware code, was that the malware would have taken weeks to develop by a skilled team – with access to industrial control systems, for testing.

The absence of any clear financial motive, and the obvious time and trouble needed to develop the malware, point to the likely involvement of a state-sponsored intelligence agency.

Either Israel or the US have long been fingered as the most likely suspects in creating the worm. The New York Times investigation fleshes out this theory, a little, by saying both Israel and the US created the worm.

Unnamed sources at Israel's Dimona Complex said the malware was developed there over the last two years as part of a joint US-Israeli operation designed to sabotage Iran's nuclear programme. The foundations of this work were reportedly laid by American intelligence agencies, who identified the type of controllers Iran intended to use and their vulnerabilities back in 2008. Testing of the Siemens controllers took place at the Idaho National Laboratory as part of a larger exercise in cybersecurity testing, according to the sources.

The NYT story doesn't explain how the malware was delivered, though it has been previously speculatively suggested that the malware was introduced by Russian sub-contractors at the Bushehr Nuclear Power Plan, either accidentally or deliberately.

While fleshing out the Mossad-created-Stuxnet theory somewhat, the NYT piece is unlikely to convince anyone who disagrees with this version of events. Alternative explanations exist, such as one theory that the malware originated in China. ®

The smart choice: opportunity from uncertainty

More from The Register

next story
Yorkshire cops fail to grasp principle behind BT Fon Wi-Fi network
'Prevent people that are passing by to hook up to your network', pleads plod
HIDDEN packet sniffer spy tech in MILLIONS of iPhones, iPads – expert
Don't panic though – Apple's backdoor is not wide open to all, guru tells us
NEW, SINISTER web tracking tech fingerprints your computer by making it draw
Have you been on YouPorn lately, perhaps? White House website?
LibreSSL RNG bug fix: What's all the forking fuss about, ask devs
Blow to bit-spitter 'tis but a flesh wound, claim team
Black Hat anti-Tor talk smashed by lawyers' wrecking ball
Unmasking hidden users is too hot for Carnegie-Mellon
Manic malware Mayhem spreads through Linux, FreeBSD web servers
And how Google could cripple infection rate in a second
Don't look, Snowden: Security biz chases Tails with zero-day flaws alert
Exodus vows not to sell secrets of whistleblower's favorite OS
Own a Cisco modem or wireless gateway? It might be owned by someone else, too
Remote code exec in HTTP server hands kit to bad guys
prev story

Whitepapers

Seven Steps to Software Security
Seven practical steps you can begin to take today to secure your applications and prevent the damages a successful cyber-attack can cause.
Consolidation: The Foundation for IT Business Transformation
In this whitepaper learn how effective consolidation of IT and business resources can enable multiple, meaningful business benefits.
Designing a Defense for Mobile Applications
Learn about the various considerations for defending mobile applications - from the application architecture itself to the myriad testing technologies.
Build a business case: developing custom apps
Learn how to maximize the value of custom applications by accelerating and simplifying their development.
Consolidation: the foundation for IT and business transformation
In this whitepaper learn how effective consolidation of IT and business resources can enable multiple, meaningful business benefits.