Security researchers from Broadcom's Symantec and Carbon Black have uncovered a new, stealthy Windows backdoor dubbed "Mistic" (also known as MLTBackdoor). The malware has been deployed in targeted attacks against organizations in the insurance, education, and IT sectors since at least April 2026. The campaign is attributed with low-to-moderate confidence to KongTuke (also tracked as Woodgnat), a prolific initial access broker (IAB). This threat actor specializes in compromising corporate networks, establishing persistent access using custom tools like Mistic, and then selling that access to the highest bidder on the cybercrime marketplace. The buyers are often affiliates of major ransomware gangs, including Qilin, Akira, and Black Basta. The discovery of Mistic highlights the increasing specialization and professionalism within the ransomware ecosystem.
KongTuke operates as a crucial link in the ransomware supply chain. Their business model is to gain and maintain access, not to deploy the ransomware themselves. The Mistic backdoor is a key tool in this operation.
MpExtMs.exe, a Microsoft binary) is placed in a directory alongside a malicious DLL named to appear legitimate (e.g., EndpointDlp.dll). When the executable is run, it loads the malicious DLL, which contains the Mistic backdoor.The Mistic backdoor employs several techniques to evade detection and analysis.
T1574.002 - Hijack Execution Flow: DLL Side-Loading. By using a legitimate, signed executable to load the malware, it can bypass simple application allowlisting and reputation-based security controls.EndpointDlp.dll to masquerade as a component of Microsoft's endpoint security suite, a form of T1036.005 - Masquerading: Match Legitimate Name or Location.T1070.004 - Indicator Removal: File Deletion.T1071.001 - Application Layer Protocol: Web Protocols) to receive commands and exfiltrate data, blending in with normal network traffic.The direct impact of the Mistic backdoor itself is limited to reconnaissance and maintaining access. However, its role as a precursor to ransomware makes it an extremely high-threat indicator.
The presence of an IAB's tool like Mistic on a network is akin to finding a burglar has already picked your locks and is just waiting for the right time to enter.
Security teams can hunt for signs of Mistic and KongTuke activity:
file_nameEndpointDlp.dllprocess_nameMpExtMs.exeC:\ProgramData\) is highly suspicious.registry_keyHKCU\Software\Microsoft\Windows\CurrentVersion\RunMpExtMs.exe).command_line_patternregsvr32 /s /n /i:<url> scrobj.dllD3-PA - Process Analysis)MpExtMs.exe from loading DLLs that are not in the protected System32 directory. (D3FEND: D3-EAL - Executable Allowlisting)Implementing rules to prevent processes from loading DLLs from non-standard directories can defeat side-loading attacks.
Using an EDR to monitor for suspicious process behaviors, like side-loading, is key to detecting stealthy threats.
Mapped D3FEND Techniques:
Application allowlisting can prevent the execution of the initial dropper or the abused legitimate executable from an unauthorized location.
Mapped D3FEND Techniques:
To detect the Mistic backdoor's core DLL side-loading technique, organizations must leverage an EDR solution with advanced process analysis capabilities. The key detection logic is to monitor for a legitimate, signed Microsoft executable (like MpExtMs.exe) being executed from an unusual file path (e.g., C:\ProgramData\, C:\Users\Public\) and subsequently loading a DLL from that same unusual path, rather than from a trusted system directory like C:\Windows\System32. This behavioral anomaly is a very high-fidelity indicator of a side-loading attack. The EDR rule should generate a high-priority alert, as this TTP is almost always malicious and is a hallmark of sophisticated actors like KongTuke.
A powerful preventative control against Mistic is application allowlisting, specifically rules that govern library loading. Using a tool like Windows Defender Application Control (WDAC), administrators can create rules that specify which DLLs a process is allowed to load. A more targeted approach is to create a rule that prevents a known-good process like MpExtMs.exe from loading any DLLs that are not signed by Microsoft or are not located in a protected system directory. This effectively breaks the side-loading attack chain, as the operating system will block the legitimate process from loading the malicious EndpointDlp.dll, preventing the backdoor from ever being activated.
Since Mistic is a tool used by an Initial Access Broker, its presence implies that the attacker's goal is to establish persistence. Security teams should proactively hunt for common persistence mechanisms used by KongTuke and other IABs. This includes continuously monitoring registry run keys (HKCU\...\Run, HKLM\...\Run), scheduled tasks, and new services for any suspicious entries. For this specific campaign, a hunt query should look for any persistence mechanism that points to MpExtMs.exe running from a non-standard directory. Automating this check with a tool like Autoruns and comparing snapshots over time can quickly reveal newly established persistence, which is often the first solid indicator of a successful compromise by a stealthy backdoor.
First observed use of the Mistic backdoor in the wild.
Symantec and Carbon Black publish research on the Mistic backdoor and its link to KongTuke.

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.
Help others stay informed about cybersecurity threats
Every tactic, technique, and sub-technique used in this threat has been identified and mapped to the MITRE ATT&CK framework for consistent, actionable threat language.
Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.
Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.
Structured threat data is packaged as a STIX 2.1 bundle and can be visualized as an interactive graph — relationships between actors, malware, techniques, and indicators.
Sigma detection rules are derived from the threat techniques in this article and can be converted for deployment across any major SIEM or EDR platform.