Skip to main content
Mallory
MalwareUsed by 1 actorExploits 1 CVE

Duqu

Duqu is a highly sophisticated modular malware platform used in targeted espionage attacks. Multiple sources in the provided content describe it as an information-stealing Trojan closely related to Stuxnet, with researchers early on connecting it to Stuxnet development through shared code and developmental links, while also noting that some technical evidence for direct authorship overlap was considered inconclusive at the time by some analysts. Unlike Stuxnet, Duqu did not include PLC functionality; instead, it was described as gathering information about industrial systems and other high-value targets, and as a possible precursor to a future Stuxnet-like attack.

The malware was delivered through exploitation and installed kernel drivers plus encrypted DLL payloads. Its driver-based injection component was reported as very similar to Stuxnet’s, using a kernel driver to decrypt and load encrypted DLLs into processes. McAfee reported associated driver filenames cmi4432.sys and jminet7.sys, with one sample digitally signed using a certificate belonging to C-Media Electronics in Taipei; VeriSign later revoked that certificate. Duqu used encrypted configuration and payload files, remote command-and-control, and could receive additional modules after compromise. Reported capabilities included remote installation of new code, keylogging, monitoring running processes and window messages, hiding files with a user-mode rootkit, copying data to a staging area, compressing it, XOR-encrypting it, and executing pushed modules.

The content also states that adversaries could instruct Duqu to spread laterally by using compromised credentials to schedule a task on remote machines that executed the malware. Kaspersky reported that a key part of the Payload DLL framework was written in an unknown programming language rather than standard C++, describing it as object-oriented and highly event-driven; this unusual framework was presented as a major distinguishing feature from Stuxnet and as evidence of substantial resources, possibly a nation-state or similarly well-funded organization.

Targeting described in the content includes Certificate Authorities, small CAs, industry systems, and other key sites. Reported Duqu attacks were noted in Iran and Sudan, and only a small number of victim sites were known at the time in some reporting. The malware communicated with at least one command server in India, which was later blacklisted by the ISP. Additional indicators and artifacts explicitly mentioned in the content include the filenames cmi4432.sys and jminet7.sys, encrypted PNF payload files, sortXXXX.nls modules, and the broader 'tilded platform' naming convention associated with Duqu and Stuxnet. The content also references a temporary file ~DEB93D.tmp in related investigative context and notes that Duqu has been widely discussed alongside Stuxnet, Flame, and later variants such as Duqu 2.0 and an intermediate Duqu 1.5.

Share:
For your environment

Hunt this family in your stack

Mallory pivots from this family to the IOCs, detections, and named campaigns that touch your stack, and pages you when something new lands.

EXPLOITED CVES

Vulnerabilities exploited

1 CVE Mallory has correlated with this family across public research and vendor advisories. Each row links to the full Mallory page for that vulnerability.

1 CVES
CVE-2011-3402TrueType Font Parsing Vulnerability in Microsoft Windows win32k.sysExploited in the wild

CVE-2011-3402 (Windows TrueType Font Parsing RCE) Vulnerability in the Windows kernel’s TrueType font parsing engine (win32k.sys)... Used in attacks linked to targeted threats (e.g., Duqu malware family). ... patched in December 2011. | Used in attacks linked to targeted threats (e.g., Duqu malware family).

via cyberthronethecyberthrone.in
THREAT ACTORS

Groups observed using it

1 distinct threat actor attributed by public researchers. Open in Mallory to see the full evidence chain and overlapping campaigns.

View more details
GOSSIPGIRL

Researchers connected Duqu to the development of Stuxnet early on.

via web archiveweb.archive.org
MITRE ATT&CK

Techniques & procedures

33 distinct techniques documented for this family, organized by ATT&CK tactic.

T1587.001MalwareEvidence1

The discoveries of the Stuxnet virus – and then the Duqu and Flame viruses – herald a new era of highly complex weaponised software made by powerful states to attack weaker states.

Initial Access

1 technique
T1078Valid AccountsEvidence2

"actors leverage legitimate credentials to log into external remote services"; "used legitimate credentials to gain initial access, maintain access, and exfiltrate data"; "used valid accounts for initial access and privilege escalation"

Execution

3 techniques
T1053Scheduled Task/JobEvidence2

"used a valid account to maintain persistence via scheduled task"; "schedule a task on remote machines that executes the malware"

T1053.005Scheduled TaskEvidence3

During the 2022 Ukraine Electric Power Attack, Sandworm Team leveraged Scheduled Tasks through a Group Policy Object (GPO) to execute CaddyWiper at a predetermined time.

T1203Exploitation for Client ExecutionEvidence2
TacticExecution

Instead, the code, delivered via exploitation, installs drivers and encrypted DLLs that function very similarly to the original Stuxnet code.

Persistence

4 techniques
T1053Scheduled Task/JobEvidence2

"used a valid account to maintain persistence via scheduled task"; "schedule a task on remote machines that executes the malware"

T1053.005Scheduled TaskEvidence3

During the 2022 Ukraine Electric Power Attack, Sandworm Team leveraged Scheduled Tasks through a Group Policy Object (GPO) to execute CaddyWiper at a predetermined time.

T1078Valid AccountsEvidence2

"actors leverage legitimate credentials to log into external remote services"; "used legitimate credentials to gain initial access, maintain access, and exfiltrate data"; "used valid accounts for initial access and privilege escalation"

T1543.003Windows ServiceEvidence2

“Sandworm Team used an arbitrary system service to load at system boot for persistence for Industroyer… replaced the ImagePath registry value of a Windows service with a new backdoor binary… [multiple groups/malware] creating a service / installing as a service / modifying service configurations for persistence.”

T1053Scheduled Task/JobEvidence2

"used a valid account to maintain persistence via scheduled task"; "schedule a task on remote machines that executes the malware"

T1053.005Scheduled TaskEvidence3

During the 2022 Ukraine Electric Power Attack, Sandworm Team leveraged Scheduled Tasks through a Group Policy Object (GPO) to execute CaddyWiper at a predetermined time.

T1055Process InjectionEvidence1

The PNF file is an encrypted DLL that is decrypted and injected into arbitrary system processes.

T1055.001Dynamic-link Library InjectionEvidence1

Duqu and Stuxnet both use a kernel driver to decrypt and load encrypted DLL (Dynamic Load Library) files. The kernel drivers serve as an “injection” engine to load these DLLs into a specific process.

T1055.012Process HollowingEvidence1

"Agent Tesla has used process hollowing to create and manipulate processes through sections of unmapped memory by reallocating that space with its malicious code." / "Astaroth can create a new process in a suspended state... unmap its memory and replace it with malicious code." / "Emotet uses a copy of certutil.exe stored in a temporary directory for process hollowing, starting the program in a suspended state before loading malicious code."

T1078Valid AccountsEvidence2

"actors leverage legitimate credentials to log into external remote services"; "used legitimate credentials to gain initial access, maintain access, and exfiltrate data"; "used valid accounts for initial access and privilege escalation"

T1543.003Windows ServiceEvidence2

“Sandworm Team used an arbitrary system service to load at system boot for persistence for Industroyer… replaced the ImagePath registry value of a Windows service with a new backdoor binary… [multiple groups/malware] creating a service / installing as a service / modifying service configurations for persistence.”

Stealth

10 techniques
T1014RootkitEvidence2
TacticStealth

The kernel drivers for both Stuxnet and Duqu use many similar techniques for encryption and stealth, such as a rootkit for hiding files.

T1027Obfuscated Files or InformationEvidence1
TacticStealth

“Duqu… a PROPERTY=VALUE pair containing a 56-bit encryption key has been used to decrypt the main payload from the installer packages.”

T1027.013Encrypted/Encoded FileEvidence1
TacticStealth

installs drivers and encrypted DLLs... The PNF file is an encrypted DLL that is decrypted and injected into arbitrary system processes.

T1036MasqueradingEvidence1
TacticStealth

temporary Windows files generated by Wiper begin with a tilde character (~), followed by the letter d (either capital or lower case), followed by other letters or numbers. This “tilded platform,” as researchers have come to call the convention, is also found in both Stuxnet and Duqu.

T1055Process InjectionEvidence1

The PNF file is an encrypted DLL that is decrypted and injected into arbitrary system processes.

T1055.001Dynamic-link Library InjectionEvidence1

Duqu and Stuxnet both use a kernel driver to decrypt and load encrypted DLL (Dynamic Load Library) files. The kernel drivers serve as an “injection” engine to load these DLLs into a specific process.

T1055.012Process HollowingEvidence1

"Agent Tesla has used process hollowing to create and manipulate processes through sections of unmapped memory by reallocating that space with its malicious code." / "Astaroth can create a new process in a suspended state... unmap its memory and replace it with malicious code." / "Emotet uses a copy of certutil.exe stored in a temporary directory for process hollowing, starting the program in a suspended state before loading malicious code."

T1078Valid AccountsEvidence2

"actors leverage legitimate credentials to log into external remote services"; "used legitimate credentials to gain initial access, maintain access, and exfiltrate data"; "used valid accounts for initial access and privilege escalation"

T1218.007MsiexecEvidence1
TacticStealth

“AppleJeus delivered components using a Windows Installer package (.msi)… executed the 3CXDesktopApp.exe…”, “APT38 has used msiexec.exe to execute malicious files.”, “Rancor has used msiexec to download and execute malicious installer files over HTTP.”, “TA505 has used msiexec to download and execute malicious Windows Installer files.”

T1564.001Hidden Files and DirectoriesEvidence1
TacticStealth

This file is hidden using the same method as the other modules.

T1553.002Code SigningEvidence2

And while Stuxnet and Duqu each “have variants where the kernel driver file is digitally signed using a software signing certificate,” Dell says this commonality is insufficient evidence of a connection “because compromised signing certificates can be obtained from a number of sources.”

T1056.001KeyloggingEvidence2

These include keyloggers, which can monitor all actions on systems: running processes, window messages, and so on.

Discovery

6 techniques
T1010Application Window DiscoveryEvidence2
TacticDiscovery

Multiple malware families are described as identifying/enumerating open windows or capturing foreground window titles (e.g., via EnumWindows, GetForegroundWindow, GetWindowText) to understand user activity and provide context for keylogging/screencapture.

T1016System Network Configuration DiscoveryEvidence2
TacticDiscovery

The content repeatedly describes actors and malware using commands and APIs such as ipconfig /all, ifconfig, arp -a, route print, netsh interface show, GetAdaptersInfo, and GetIpNetTable to gather IP addresses, MAC addresses, DNS, DHCP, gateways, routing tables, ARP cache, proxy settings, and network adapter/interface details.

T1049System Network Connections DiscoveryEvidence1
TacticDiscovery
T1057Process DiscoveryEvidence3
TacticDiscovery

The content repeatedly describes malware and threat actors obtaining lists of running processes, using utilities such as tasklist, ps, WMI, Get-Process, CreateToolhelp32Snapshot, EnumProcesses, and similar APIs/commands to enumerate active processes on victim systems.

T1087Account DiscoveryEvidence1
TacticDiscovery

“actors used the following commands… to enumerate user accounts: net user >> %temp%\download; net user /domain >> %temp%\download … APT1 used the commands net localgroup, net user, and net group to find accounts… APT32 enumerated administrative users using the commands net localgroup administrators … OilRig has run net user, net user /domain, net group "domain admins" /domain …”

T1135Network Share DiscoveryEvidence1
TacticDiscovery

"spread laterally by copying itself to shares it has enumerated"

Lateral Movement

2 techniques
T1021.002SMB/Windows Admin SharesEvidence2

"spread laterally by copying itself to shares... for which it has obtained legitimate credentials"; "hard-coded credentials to gain access to a network share"

T1570Lateral Tool TransferEvidence2

Duqu ... spread laterally by copying itself to shares it has enumerated ... The remote host is then infected by using the compromised credentials to schedule a task on remote machines that executes the malware.

Collection

3 techniques
T1056.001KeyloggingEvidence2

These include keyloggers, which can monitor all actions on systems: running processes, window messages, and so on.

T1074Data StagedEvidence1

The content repeatedly describes adversaries and malware storing collected data, command output, credentials, archives, or files in local temporary folders, working directories, hidden directories, registry locations, recycle bins, or specific files prior to exfiltration.

T1074.001Local Data StagingEvidence1
T1071Application Layer ProtocolEvidence2

It communicates with a command server in India... Both groups above also contain another module, sortXXXX.nls... It seems to be responsible for the malware’s malicious activities, such as command and control communications.

T1105Ingress Tool TransferEvidence1

The code in question is part of the Payload DLL, a section of the trojan that sends and receives instructions from an outside source once it has infiltrated a system.

T1219Remote Access ToolsEvidence2

Duqu provides attackers with remote access to compromised computers with the ability to run arbitrary programs, and can theoretically be used to target any organization, Dell said.

T1572Protocol TunnelingEvidence1
T1573.001Symmetric CryptographyEvidence1

"3PARA RAT command and control commands are encrypted within the HTTP C2 channel using the DES algorithm in CBC mode..."; "APT33 has used AES for encryption of command and control traffic."; "Carbanak encrypts the message body of HTTP traffic with RC2 (in CBC mode)."; "Duqu ... data stream can be encrypted with AES-CBC."; "PoisonIvy uses the Camellia cipher to encrypt communications."

Other

1 technique
T1562Impair DefensesEvidence1

The strings indicate these modules have the capability to disable security tools, targeting some specific antivirus products.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets match these IOCs, which detections are missing, which campaigns to expect next, and what to do in the next 30 minutes.
IOC matching

Match every observed IP, domain, and hash against your live telemetry.

Threat actor attribution1

Named campaigns wielding this family, with evidence pinned to each claim.

Exploited vulnerabilities1

CVEs this family uses for access and lateral movement.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

MITRE ATT&CK mapping33

Every documented technique, ranked by evidence weight.

Researcher chatter

Reddit, Mastodon, and CTI community discussion around this family.