Duqu is a computer worm discovered on 1 September 2011, thought to be related to the Stuxnet worm. The Laboratory of Cryptography and System Security (CrySyS Lab) of the Budapest University of Technology and Economics in Hungary discovered the threat, analysed the malware, and wrote a 60-page report naming the threat Duqu. Duqu got its name from the prefix "~DQ" it gives to the names of files it creates.
The term Duqu is used in a variety of ways:
- Duqu malware is a variety of software components that together provide services to the attackers. Currently this includes information stealing capabilities and in the background, kernel drivers and injection tools. Part of this malware is written in unknown high level programming language, dubbed "Duqu framework". It is not C++, Python, Ada, Lua and many other checked languages. However, recent evidence suggests that Duqu may have been written in Object Oriented C (OO C) and compiled in Microsoft Visual Studio 2008.
- Duqu flaw is the flaw in Microsoft Windows that is used in malicious files to execute malware components of Duqu. Currently one flaw is known, a TTF related problem in win32k.sys.
- Operation Duqu is the process of only using Duqu for unknown goals. The operation might be related to Operation Stuxnet.
 Relationship to Stuxnet
Symantec, based on the CrySyS report, continued the analysis of the threat, which it called "nearly identical to Stuxnet, but with a completely different purpose", and published a detailed technical paper on it with a cut-down version of the original lab report as an appendix. Symantec believes that Duqu was created by the same authors as Stuxnet, or that the authors had access to the source code of Stuxnet. The worm, like Stuxnet, has a valid, but abused digital signature, and collects information to prepare for future attacks. Mikko Hyppönen, Chief Research Officer for F-Secure, said that Duqu's kernel driver, JMINET7.SYS, was so similar to Stuxnet's MRXCLS.SYS that F-Secure's back-end system thought it was Stuxnet. Hyppönen further said that the key used to make Duqu's own digital signature (only observed in one case) was stolen from C-Media, located in Taipei, Taiwan. The certificates were due to expire on 2 August 2012 but were revoked on 14 October 2011 according to Symantec.
Experts compared the similarities and found three of interest:
- The installer exploits zero-day Windows kernel vulnerabilities.
- Components are signed with stolen digital keys.
- Duqu and Stuxnet are both highly targeted and related to the nuclear program of Iran.
 Microsoft Word zero-day exploit
Like Stuxnet, Duqu attacks Microsoft Windows systems using a zero-day vulnerability. The first-known installer (AKA dropper) file recovered and disclosed by CrySyS Lab uses a Microsoft Word (.doc) that exploits the Win32k TrueType font parsing engine and allows execution. The Duqu dropper relates to font embedding, and thus relates to the workaround to restrict access to T2EMBED.DLL, which is a TrueType font parsing engine if the patch released by Microsoft in December, 2011 is not yet installed. Microsoft identifier for the threat is MS11-087 (first advisory issued on 13 November 2011).
Duqu looks for information that could be useful in attacking industrial control systems. Its purpose is not to be destructive, the known components are trying to gather information. However, based on the modular structure of Duqu, special payload could be used to attack any type of computer systems by any means and thus cyber-physical attacks based on Duqu might be possible. However, use on personal computer systems has been found to delete all recent information entered on the system, and in some cases total deletion of the computer's hard drive. Internal communications of Duqu are analysed by Symantec, but the actual and exact method how it replicates inside an attacked network is not yet fully known. According to McAfee, one of Duqu's actions is to steal digital certificates (and corresponding private keys, as used in public-key cryptography) from attacked computers to help future viruses appear as secure software. Duqu uses a 54×54 pixel jpeg file and encrypted dummy files as containers to smuggle data to its command and control center. Security experts are still analyzing the code to determine what information the communications contain. Initial research indicates that the original malware sample automatically removes itself after 36 days (the malware stores this setting in configuration files), which would limit its detection.
Key points are:
- Executables developed after Stuxnet using the Stuxnet source code that have been discovered.
- The executables are designed to capture information such as keystrokes and system information.
- Current analysis shows no code related to industrial control systems, exploits, or self-replication.
- The executables have been found in a limited number of organizations, including those involved in the manufacturing of industrial control systems.
- The exfiltrated data may be used to enable a future Stuxnet-like attack or might already have been used as basis for the Stuxnet attack.
 Command and control servers
Some of the command and control servers of Duqu have been analysed. It seems that the people running the attack had a predilection for CentOS 5.x servers, leading some researchers to believe that they had a zero-day exploit for it. Servers are scattered in many different countries, including Germany, Belgium, Philippines, India and China. Kaspersky published multiple blogposts on the command and control servers.
 See also
- Flame (malware)
- Mahdi (malware)
- Stars virus
- Cyber electronic warfare
- Cyber security standards
- Cyberwarfare in the United States
- List of cyber attack threat trends
- Operation Merlin
- Proactive Cyber Defence
- United States Cyber Command
- Moonlight Maze
- Titan Rain
- Operation High Roller
- "Laboratory of Cryptography and System Security (CrySyS)". Retrieved 4 November 2011.
- "Duqu: A Stuxnet-like malware found in the wild, technical report". Laboratory of Cryptography of Systems Security (CrySyS). 14 October 2011.
- "Statement on Duqu's initial analysis". Laboratory of Cryptography of Systems Security (CrySyS). 21 October 2011. Retrieved 25 October 2011.
- "W32.Duqu – The precursor to the next [[Stuxnet]] (Version 1.4)". Symantec. 23 November 2011. Retrieved 30 December 2011. Wikilink embedded in URL title (help)
- Shawn Knight (2012) Duqu Trojan contains mystery programming language in Payload DLL
- Zetter, Kim (18 October 2011). "Son of Stuxnet Found in the Wild on Systems in Europe". Retrieved 21 October 2011.
- "Virus Duqu alarmiert IT-Sicherheitsexperten". Die Zeit. 19 October 2011. Retrieved 19 October 2011.
- "Spotted in Iran, trojan Duqu may not be "son of Stuxnet" after all". Retrieved 27 October 2011.
- "Microsoft issues temporary 'fix-it' for Duqu zero-day". Retrieved 5 November 2011.
- "Microsoft Security Advisory (2639658)". Vulnerability in TrueType Font Parsing Could Allow Elevation of Privilege. 3 November 2011. Retrieved 5 November 2011.
- "Microsoft Security Bulletin MS11-087 - Critical". Retrieved 13 November 2011.
- Steven Cherry, with Larry Constantine (December 14, 2011). "Sons of Stuxnet". IEEE Spectrum.
- Venere, Guilherme; Szor, Peter (18 October 2011). "The Day of the Golden Jackal – The Next Tale in the Stuxnet Files: Duqu". McAfee. Retrieved 19 October 2011.
- "The mystery of Duqu part six: The command and control servers". 30 November 2011. Retrieved 30 November 2011.