That's not true! THAT'S IMPOSSIBLE!!!

Came for the obvious...leaving happy.

Christopher Lee in 3 . . . 2 . . .

FTFA: "That suggests that the attackers behind Stuxnet either gave that code to the developers of Duqu, allowed it to be stolen, or are the same people who built Duqu, Haley said.
'We believe it is the latter,' he said."

Puzzling. I think most people agree that Stuxnet was made by or for a government, probably Israel. Unless Duqu is an extension of the Stuxnet effort and for similar purposes, I don't immediately see why there should be a connection. Perhaps they contracted with 3rd party black hats for Stuxnet and those guys used or developed their own "kit" - and are now contracting out bits of that kit for more nefarious purposes? Doesn't sound very Israeli to seek the services of outside bad guys, though. They tend to grow their own. As I said, puzzling.

RatOmeter: FTFA: "That suggests that the attackers behind Stuxnet either gave that code to the developers of Duqu, allowed it to be stolen, or are the same people who built Duqu, Haley said.
'We believe it is the latter,' he said."

Puzzling. I think most people agree that Stuxnet was made by or for a government, probably Israel. Unless Duqu is an extension of the Stuxnet effort and for similar purposes, I don't immediately see why there should be a connection. Perhaps they contracted with 3rd party black hats for Stuxnet and those guys used or developed their own "kit" - and are now contracting out bits of that kit for more nefarious purposes? Doesn't sound very Israeli to seek the services of outside bad guys, though. They tend to grow their own. As I said, puzzling.

Consensus is starting to build that Duqu is not Stuxnet 2.0. There is a lot of circumstantial evidence, but Duqu being developed by the same team is not the only, or even necessarily the most likely, explanation for the common features.

RatOmeter: FTFA: "That suggests that the attackers behind Stuxnet either gave that code to the developers of Duqu, allowed it to be stolen, or are the same people who built Duqu, Haley said.
'We believe it is the latter,' he said."

Puzzling. I think most people agree that Stuxnet was made by or for a government, probably Israel. Unless Duqu is an extension of the Stuxnet effort and for similar purposes, I don't immediately see why there should be a connection. Perhaps they contracted with 3rd party black hats for Stuxnet and those guys used or developed their own "kit" - and are now contracting out bits of that kit for more nefarious purposes? Doesn't sound very Israeli to seek the services of outside bad guys, though. They tend to grow their own. As I said, puzzling.

The theory that I've heard that make the most sense is that Iran is behind Duqu. While they wouldn't have the expertise to reverse engineer Stuxnet alone, they certainly wouldn't be above hiring black hats to help them. Imagine the effect if Iran was able to retaliate for an attack on their Nuclear facilities by shutting down or sabotaging critical infrastructure. Theoretically they could attack the electrical grid, gas/oil pipelines, water treatment facilities, air traffic control, etc. etc. The damage could be massive and devastating.

Of course it could also just be Chinese hackers trying to steal WOW accounts. Still, I think we need to Nuke Iran form orbit. It's the only way to be sure.

That suggests that the attackers behind Stuxnet either gave that code to the developers of Duqu, allowed it to be stolen, or are the same people who built Duqu, Haley said. 'We believe it is the latter,' he said.

Maybe there were working on a new version and it escaped of its own voli
(connection closed by remote host)

Daddy?

If you go on Symantec's blog site (http://www.symantec.com/connect/w32-duqu_status-updates_installer-zer o-day-exploit) it shows that Iran is getting hit the most (3 Iranian organizations at least). Duqu is also hitting Sudan, Vietnam, Ukraine, and India.

It's designed to get into secure places were there isn't internet access, and getting those computers to access the internet through a proxy computer in the organization.

I definitely think this is some type of anti-infrastructure virus, maybe this one isn't meant to do anything in particular, more exploratory "see what we can get into" type virus.

I just hope this team is on our side, 2 zero-day exploits in what a year? That is some pretty sophisticated programming and engineering.

We took hard-working European source code and recompiled it using aggressive African object libraries, in an attempt to make docile yet super-producing applications.