Security researchers discover link between Stuxnet and Flame

Flame module was incorporated in early Stuxnet version, Kaspersky Lab researchers say

Security researchers from antivirus vendor Kaspersky Labs have found evidence that the development teams behind the Flame and Stuxnet cyberespionage threats collaborated with each other.

The Kaspersky researchers determined that Flame, which is believed to have been created in 2008, and a 2009-version of Stuxnet shared one component that served the same purpose and had similar source code.

Back in October 2010, Kaspersky's researchers analyzed a sample that had been automatically classified as a Stuxnet variant by the company's automated systems. At the time, the researchers dismissed the detection as an error because the sample's code looked nothing like the code in Stuxnet.

However, after Flame was discovered at the end of May, the Kaspersky researchers searched their database for malware samples that might be related to the new threat and found that the sample detected as Stuxnet in 2010 was actually a Flame module.

The module uses an autorun.inf trick to infect computers via USB drives and exploits a now-patched elevation of privilege (EoP) vulnerability to execute malicious code with full system privileges.

Upon further research, the Kaspersky analysts determined that Stuxnet.A, which was created in early 2009, uses the same autorun.inf trick and vulnerability to spread via USB drives. In fact, the source code responsible for this is almost identical to the one in the Flame module.

"It looks like the Flame platform was used to kick start the Stuxnet platform," said Roel Schouwenberg, a senior researcher with Kaspersky Lab's global research and analysis team, during a conference call with the press.

The Kaspersky researchers already knew that Stuxnet and Flame leveraged the same EoP vulnerability, but this wasn't conclusive proof that their developers collaborated. The exploit could have been created by a third-party that sold it to both teams, Schouwenberg said.

However, the new discovery suggests that the developers of the two malware threats actually shared source code, which is intellectual property and wouldn't normally be shared between unrelated teams. "We are now 100-percent sure that the Flame and Stuxnet groups worked together," Schouwenberg said.

When Microsoft patched the EoP vulnerability in 2009 -- a few months after the creation of Stuxnet.A -- the Stuxnet developers stopped using the Flame module for propagation and began exploiting a new vulnerability, which relied on malformed LNK (shortcut) files.

The theory put forward by the Kaspersky researchers is that Flame and Stuxnet were created by two separate teams as part of two operations funded by the same nation state. Flame was probably used for espionage and Stuxnet used for sabotage, Schouwenberg said.

According to a recent New York Times report that quotes anonymous sources from the Obama administration, Stuxnet was created by the U.S. and Israeli governments as part of a secret operation called Olympic Games with the goal of crippling Iran's ability to produce weapon-grade nuclear fuel.

Comments are now closed.
CSO Corporate Partners
  • Webroot
  • Trend Micro
  • NetIQ
rhs_login_lockGet exclusive access to CSO, invitation only events, reports & analysis.
CSO Directory

Endpoint Encryption

Robust data protection for PCs, smartphones, and removable media

Security Awareness Tip

Incident handling is a vast topic, but here are a few tips for you to consider in your incident response. I hope you never have to use them, but the odds are at some point you will and I hope being ready saves you pain (or your job!).


  1. Have an incident response plan.

  2. Pre-define your incident response team 

  3. Define your approach: watch and learn or contain and recover.

  4. Pre-distribute call cards.

  5. Forensic and incident response data capture.

  6. Get your users on-side.

  7. Know how to report crimes and engage law enforcement. 

  8. Practice makes perfect.

For the full breakdown on this article

Security ABC Guides

Warning: Tips for secure mobile holiday shopping

I’m dating myself, but I remember when holiday shopping involved pouring through ads in the Sunday paper, placing actual phone calls from tethered land lines to research product stock and availability, and actually driving places to pick things up. Now, holiday shoppers can do all of that from a smartphone or tablet in a few seconds, but there are some security pitfalls to be aware of.