Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Vulnerabilities / Threats

3/19/2012
05:24 PM
Connect Directly
Google+
Twitter
RSS
E-Mail
50%
50%

Duqu Code Written By Seasoned Programmers, Researchers Find

Another clue about Duqu solved that further confirms a highly sophisticated and well-backed operation, but the attackers are still not unmasked

The mystery of who's really behind the sophisticated Stuxnet and Duqu attacks remains unsolved, but new evidence shows that the masterminds behind Duqu relied on professional programmers in their code development.

Kaspersky Lab researchers today announced that, with the help of the security community, they were able to unravel the origins of a well-masked programming language used to write the communications module in Duqu, the information-stealing malware that researchers at Kaspersky and other firms say is connected to Stuxnet. They also said that the same group of actors is behind both malware attacks.

Turns out the attackers used object-oriented C language compiled with Microsoft Visual Studio 2008 -- which indicates that it wasn't your typical malware writer behind it, but more of an "old school" programmer, according to Kaspersky researchers. "This is not common for malware writers, that's for sure," Vitaly Kamluk, chief malware analyst, said in a press briefing today. "This looks like a normal style for coding enterprise-wide applications."

Kamluk says the language used is very commonly a tool for professional software developers, which suggests that the Duqu writers were not a typical cybercriminal outfit. Kaspersky earlier this month asked the security community for assistance in identifying the programming language, which didn't appear to one they had ever seen before.

Most researchers agree that Duqu and Stuxnet came from the same code base, but there is still some debate over whether the two attacks are related. Kaspersky earlier this year found that there were at least three other unrelated exploits written from the so-called "Tilded" platform. But no one has yet confirmed who is behind the attack campaigns, even amid heavy speculation that it was the handiwork of Israel and the U.S. in an attempt to halt Iran's nuclear enrichment program.

"We are not closer to the answer of which country might be behind it," Kamluk said. "We have some guesses, and we are still aggressively researching it."

[ Researchers remain at odds over whether this latest highly targeted threat with several parallels to Stuxnet is actually related to Stuxnet. See What Is Duqu Up To?. ]

Other researchers, including Dell SecureWorks, have disputed any connection between the Duqu and Stuxnet attacks. Just because they were generated from the same toolkit, SecureWorks' Don Jackson has argued, doesn't mean they are part of the same attack.

One theory posed by Kaspersky and other research firms is that Duqu was the reconnaissance piece of the Stuxnet attack on the Siemens equipment. But SecureWorks says that's not the case.

Meanwhile, when Kaspersky researchers were unable to decipher the programming language with Duqu, they asked for outside help. "We thought it was one of two options, either C or a new programming language. That's why we asked the community" for help, Kamluk said.

The creators of Duqu and Stuxnet have been careful not to leave behind clues that might give away their native spoken language or country of origin, he said.

Why the OOC language versus C++? Kaspersky says programmers who use OOC say it's likely that these "old-school" programmers don't trust C++ compilers and like the portability of OOC. "Both reasons appear to indicate the code was written by a team of experienced, 'old-school' developers," blogged Igor Soumenkov, a security expert for Kaspersky Lab.

Screen shots and additional technical details of this latest Duqu finding are here.

Have a comment on this story? Please click "Add Your Comment" below. If you'd like to contact Dark Reading's editors directly, send us a message.

Kelly Jackson Higgins is the Executive Editor of Dark Reading. She is an award-winning veteran technology and business journalist with more than two decades of experience in reporting and editing for various publications, including Network Computing, Secure Enterprise ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 9/25/2020
Google Cloud Debuts Threat-Detection Service
Robert Lemos, Contributing Writer,  9/23/2020
Shopify's Employee Data Theft Underscores Risk of Rogue Insiders
Kelly Sheridan, Staff Editor, Dark Reading,  9/23/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-26120
PUBLISHED: 2020-09-27
XSS exists in the MobileFrontend extension for MediaWiki before 1.34.4 because section.line is mishandled during regex section line replacement from PageGateway. Using crafted HTML, an attacker can elicit an XSS attack via jQuery's parseHTML method, which can cause image callbacks to fire even witho...
CVE-2020-26121
PUBLISHED: 2020-09-27
An issue was discovered in the FileImporter extension for MediaWiki before 1.34.4. An attacker can import a file even when the target page is protected against "page creation" and the attacker should not be able to create it. This occurs because of a mishandled distinction between an uploa...
CVE-2020-25812
PUBLISHED: 2020-09-27
An issue was discovered in MediaWiki 1.34.x before 1.34.4. On Special:Contributions, the NS filter uses unescaped messages as keys in the option key for an HTMLForm specifier. This is vulnerable to a mild XSS if one of those messages is changed to include raw HTML.
CVE-2020-25813
PUBLISHED: 2020-09-27
In MediaWiki before 1.31.10 and 1.32.x through 1.34.x before 1.34.4, Special:UserRights exposes the existence of hidden users.
CVE-2020-25814
PUBLISHED: 2020-09-27
In MediaWiki before 1.31.10 and 1.32.x through 1.34.x before 1.34.4, XSS related to jQuery can occur. The attacker creates a message with [javascript:payload xss] and turns it into a jQuery object with mw.message().parse(). The expected result is that the jQuery object does not contain an <a> ...