DragonForce Ransomware Deploys 'Backdoor.Turn', a Go-Based Backdoor that Hides C&C Traffic Using Microsoft Teams TURN Relay Servers

Microsoft Teams Relay Servers Abused in DragonForce Ransomware Attack

HIGH
June 17, 2026
June 18, 2026
7m read
RansomwareMalwareThreat Actor

Related Entities(initial)

Threat Actors

DragonForceHackledorb

Organizations

Microsoft BroadcomSymantecCarbon BlackPraetorian

Products & Tech

Microsoft Teams GoQUICSQL Server

Other

Backdoor.TurnABYSSWORKER

CVE Identifiers

Full Report(when first published)

Executive Summary

The DragonForce ransomware group (also tracked as Hackledorb) has deployed a highly sophisticated, custom-built backdoor dubbed Backdoor.Turn that leverages Microsoft Teams infrastructure for command-and-control (C&C) communications. According to researchers from Broadcom’s Symantec and Carbon Black, this is the first known malware to abuse Microsoft's Traversal Using Relays around NAT (TURN) servers in this manner. The Go-based malware tunnels its C&C traffic through legitimate Microsoft servers, effectively camouflaging it as standard Teams activity. This advanced technique, observed in an attack against a U.S. services firm where attackers dwelled for one to two months, highlights the group's significant resource allocation and growing technical maturity, moving beyond off-the-shelf tools to develop highly evasive custom malware.

Threat Actor Profile

Active since at least 2023, DragonForce (aka Hackledorb) operates with a cartel-like structure. The group has demonstrated a significant increase in sophistication, employing advanced cyber tradecraft and custom tooling that indicates organizational maturity and a high level of skill. Reporting indicates Hackledorb has pivoted from a conventional ransomware-as-a-service (RaaS) model to a more formalized and organized cartel structure, focusing on high-impact targeted attacks. The operational timeline reveals a pattern of continuous capability development, with the adoption of highly advanced techniques becoming a hallmark of their post-2025 activity. The deployment of Backdoor.Turn, combined with their multi-vector BYOVD evasion, marks them as one of the most capable and persistent ransomware groups operating today.

Technical Analysis

Attack Chain

The attack, which began in December 2025, followed a multi-stage intrusion pattern:

  1. Initial Access: The attackers gained initial access to the victim, a U.S. services firm, likely by exploiting an unknown vulnerability in a public-facing SQL or MSSQL server. It is also possible they purchased initial access from a third-party broker.
  2. Execution and Persistence: Once inside, the operators used a PowerShell command to drop a ZIP archive disguised as a tech support hotfix. This initiated a DLL sideloading attack to execute code, download additional malware, and establish persistence.
  3. Defense Evasion and Privilege Escalation: The group employed a Bring-Your-Own-Vulnerable-Driver (BYOVD) strategy, exploiting known flaws in multiple signed drivers to gain kernel-level access. This allowed them to terminate security processes on the compromised systems. Known drivers used include HWAuidoOs2Ec.sys (a Huawei driver also seen in separate malvertising campaigns), wsftprm.sys (CVE-2023-52271), GameDriverX64.sys (CVE-2025-61155), K7RKScan.sys (CVE-2025-1055), and a custom malicious driver named ABYSSWORKER.
  4. Discovery and Lateral Movement: The attackers conducted network reconnaissance, including LDAP/AD mapping, and used stolen credentials to move laterally across the network.
  5. Impact: After mapping the network and exfiltrating sensitive data, the attackers deployed the DragonForce ransomware to encrypt files across the environment.
  6. Post-Exploitation Persistence: The Backdoor.Turn malware was deployed after the ransomware event, injected into the legitimate DbgView64.exe process. This suggests a strategy to maintain stealthy, long-term access for future attacks or to sell access to other threat actors.

C&C Mechanism: Abusing Microsoft Teams

The most innovative feature of Backdoor.Turn is its C&C mechanism, which is based on a technique dubbed "Ghost Calls" by security firm Praetorian. This makes malicious traffic exceptionally difficult to detect:

  1. Token Acquisition: The backdoor first communicates with Microsoft's Skype-backed identity services to obtain an anonymous Teams visitor token.
  2. TURN Relay Authentication: It then uses this token to authenticate to a legitimate Microsoft TURN relay server, which is normally used to facilitate real-time voice and video calls.
  3. QUIC Tunnel: Finally, it establishes a QUIC session through the TURN server to the actual attacker-controlled C&C server.

Because all outbound traffic from the infected host is directed to trusted Microsoft IP addresses using standard protocols (TURN/QUIC), it bypasses traditional firewalls and network security tools that rely on IP reputation.

Malware Capabilities

Backdoor.Turn is a full-featured remote access trojan (RAT) with capabilities including:

  • Executing arbitrary commands and creating new processes.
  • Performing network scanning and mapping Active Directory via LDAP.
  • Moving laterally within the network using stolen credentials.
  • Exfiltrating credentials from installed web browsers.

Impact Assessment

This novel technique has serious implications for network defenders:

  • Extreme Detection Evasion: By masquerading as legitimate Teams traffic, the C&C communication can evade detection by NIDS, proxies, and other tools that trust traffic to major cloud providers.
  • Increased Attacker Sophistication: It demonstrates that ransomware groups like DragonForce are investing heavily in R&D to create custom tools that are far more effective than generic malware.
  • Attribution Challenges: Abusing legitimate services makes it harder to identify attacker infrastructure, as the initial network indicators point to Microsoft's legitimate servers.

IOCs — Directly from Articles

  • Backdoor.Turn: The name of the custom Go-based backdoor used for C&C and post-exploitation persistence.
  • HWAuidoOs2Ec.sys: A vulnerable Huawei driver used in a BYOVD attack to disable security software. It has also been observed in separate malvertising campaigns.
  • wsftprm.sys: A vulnerable driver associated with CVE-2023-52271, used in BYOVD attacks.
  • GameDriverX64.sys: A vulnerable driver associated with CVE-2025-61155, used in BYOVD attacks.
  • K7RKScan.sys: A vulnerable driver associated with CVE-2025-1055, used in BYOVD attacks.
  • ABYSSWORKER: A custom-built malicious driver used for defense evasion, previously seen in Medusa ransomware attacks.
  • DbgView64.exe: A legitimate Sysinternals tool into which Backdoor.Turn is injected to evade detection.

Cyber Observables — Hunting Hints

Defenders can hunt for this activity using the following behavioral and network-based indicators:

Type
Network Behavior
Value
Anomalous TURN/QUIC Traffic
Description
Monitor for traffic using TURN (UDP 3478-3481) or QUIC (UDP 443) originating from servers or non-user workstations, particularly to Microsoft IP ranges.
Type
Process
Value
Unsigned Go Binaries
Description
Hunt for execution of unknown, unsigned Go executables making outbound network connections, especially from a server environment.
Type
Driver Load
Value
HWAuidoOs2Ec.sys
Description
Monitor for the loading of this known-vulnerable driver, often followed by security process termination.
Type
Driver Load
Value
wsftprm.sys
Description
Monitor for the loading of this known-vulnerable driver (CVE-2023-52271), often followed by security process termination.
Type
Driver Load
Value
GameDriverX64.sys
Description
Monitor for the loading of this known-vulnerable driver (CVE-2025-61155), often followed by security process termination.
Type
Driver Load
Value
K7RKScan.sys
Description
Monitor for the loading of this known-vulnerable driver (CVE-2025-1055), often followed by security process termination.
Type
Driver Load
Value
ABYSSWORKER
Description
Monitor for the loading of this custom malicious driver.
Type
TTP
Value
DLL Sideloading
Description
Monitor for legitimate, signed applications loading a malicious DLL from a non-standard directory.
Type
TTP
Value
Process Injection
Description
Hunt for code injection into legitimate diagnostic tools like DbgView64.exe, especially if the process then initiates outbound network connections.

Detection & Response

  • Egress Traffic Analysis: Monitor for anomalous traffic patterns. A server in a data center should not be initiating TURN/STUN (UDP ports 3478-3481) or QUIC (UDP 443) traffic. Contextual analysis of the source of this traffic is critical.
  • Endpoint Detection and Response (EDR): Deploy EDR to detect suspicious process chains, such as DLL sideloading, process injection into tools like DbgView64.exe, and the loading of known vulnerable drivers.
  • Behavioral Hunting: Actively hunt for the TTPs outlined in the Cyber Observables section, such as the loading of specific vulnerable drivers followed by the termination of security processes.

Remediation Steps

  • Vulnerability Management: Maintain a robust patch management program to address vulnerabilities in public-facing applications like SQL servers, which are common initial access vectors.
  • Application Control: Use application allowlisting (e.g., AppLocker) to prevent the execution of unauthorized or unsigned binaries, which would block the custom Go-based backdoor.
  • Kernel Protection: Implement security features like Hypervisor-Protected Code Integrity (HVCI) and driver blocklists to mitigate BYOVD attacks. Block known vulnerable drivers like HWAuidoOs2Ec.sys, wsftprm.sys, and others.

Timeline of Events

1
August 1, 2024
Praetorian documents the "Ghost Calls" C2 technique, which forms the basis for Backdoor.Turn's communication method.
2
December 1, 2025
DragonForce operators gain initial access to the victim's network, likely via a compromised SQL server.
3
June 17, 2026
This article was published
4
June 18, 2026
Symantec, Carbon Black, and The Hacker News publish findings on the 'Backdoor.Turn' malware, its abuse of Microsoft Teams, and the specific drivers used in its BYOVD attacks.

Article Updates

June 18, 2026

New details on privilege escalation via Huawei driver vulnerability and extended 1-2 month dwell time for DragonForce's Backdoor.Turn.

June 18, 2026

Updated the report with new context on the HWAuidoOs2Ec.sys driver's use in other campaigns, corrected an erroneously associated CVE, and reformatted key sections for clarity.

MITRE ATT&CK Mitigations

Patching vulnerabilities in public-facing applications like SQL/MSSQL servers is critical to preventing the initial access vector used in this attack.

Implement strict egress filtering policies for servers. If a server has no business reason to make Teams calls, block outbound TURN/QUIC traffic to prevent this C2 channel.

Use EDR or similar tools to create behavioral rules that detect and block techniques like BYOVD, termination of security processes, and DLL sideloading.

Use application control solutions (e.g., AppLocker) to prevent the execution of unauthorized or unsigned binaries, which would stop custom malware like Backdoor.Turn from running.

D3FEND Defensive Countermeasures

To counter 'Backdoor.Turn', which abuses Microsoft Teams' TURN servers, defenders must employ sophisticated Network Traffic Analysis that goes beyond simple IP/domain blocklists. Since the destination IPs are legitimate Microsoft servers, analysis must focus on the source and context of the traffic. Security teams should establish a baseline of normal network behavior and create alerts for anomalies. Specifically, any server within a data center initiating traffic on TURN ports (UDP 3478-3481) or QUIC (UDP 443) to Microsoft's network should be treated as a high-priority alert, as servers typically do not make VoIP calls. This requires network sensors or EDR agents capable of identifying the protocol and source process of network connections. Correlating this anomalous network traffic with the execution of an unsigned Go binary on the source server would provide a high-confidence indicator of a 'Backdoor.Turn' infection.

The DragonForce attack involved multiple custom components, including the Go-based 'Backdoor.Turn' and a BYOVD component. Executable Allowlisting is a powerful mitigation against such threats. On critical servers, administrators should implement a strict application control policy that denies the execution of any binary by default. Only a pre-approved list of executables and drivers required for business operations should be allowed to run. This would prevent the custom backdoor from executing, as its hash would not be on the allowlist. It would also block the BYOVD attack by preventing the vulnerable driver from being loaded. While implementing a full allowlist can be challenging, it is highly effective for single-purpose servers, like the SQL server likely compromised in this attack, and provides a strong defense against novel malware.

Timeline of Events

1
August 1, 2024

Praetorian documents the "Ghost Calls" C2 technique, which forms the basis for Backdoor.Turn's communication method.

2
December 1, 2025

DragonForce operators gain initial access to the victim's network, likely via a compromised SQL server.

3
June 18, 2026

Symantec, Carbon Black, and The Hacker News publish findings on the 'Backdoor.Turn' malware, its abuse of Microsoft Teams, and the specific drivers used in its BYOVD attacks.

Sources & References(when first published)

Article Author

Jason Gomes

Jason Gomes

• Cybersecurity Practitioner

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.

Threat Intelligence & AnalysisSecurity Orchestration (SOAR/XSOAR)Incident Response & Digital ForensicsSecurity Operations Center (SOC)SIEM & Security AnalyticsCyber Fusion & Threat SharingSecurity Automation & IntegrationManaged Detection & Response (MDR)

Editorial Standards & Analyst Review

CyberNetSec.io uses automation to assist source monitoring, deduplication, observable extraction, and structured intelligence generation. Published analysis follows human-defined editorial standards and adds defensive context including MITRE ATT&CK, D3FEND, STIX, and Sigma where applicable. Read our editorial policy.

Tags

C2Defense EvasionLiving off the LandGoQUICBYOVDDLL SideloadingProcess Injection

📢 Share This Article

Help others stay informed about cybersecurity threats

🎯 MITRE ATT&CK Mapped

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.

🧠 Enriched & Analyzed

Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.

🛡️ Actionable Guidance

Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.

🔗 STIX Visualizer

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 Generator

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.