Skip to navigation

Threat reportRansomwareTL-2026-2181

DragonForce Ransomware Abuses Microsoft Teams TURN Relays to Hide Backdoor.Turn C2 Traffic

criticalACTIVE

Symantec's Broadcom Threat Hunter Team identified Backdoor.Turn, a Go-based backdoor deployed by the DragonForce ransomware cartel (tracked as Hackledorb), that abuses legitimate Microsoft Teams TURN relay infrastructure to conceal C2 traffic. Deployed during a 1-2 month intrusion at a U.S. services firm, the backdoor obtains an anonymous Teams visitor token, routes through a genuine Microsoft TURN relay, and then opens a direct QUIC session to the real C2 server before the DragonForce ransomware payload is dropped.

Key facts

IdentifiersTL-2026-2181, CVE-2023-52271, CVE-2025-61155, CVE-2025-1055
SeverityCRITICAL
EPSSCVE-2023-52271: 0.3% (21.5th percentile); CVE-2025-61155: 0.2% (18.6th percentile); CVE-2025-1055: 0.2% (12.8th percentile)
Affected productsTopaz Evolution Antifraud (wsftprm.sys kernel driver); Hotta Studio Tower of Fantasy (GameDriverX64.sys kernel driver); K7 Security K7 Security Anti-Malware (K7RKScan.sys kernel driver); Huawei HWAuidoOs2Ec.sys kernel driver; Microsoft Microsoft Teams / Skype TURN relay infrastructure (abused as a covert channel, not itself vulnerable)
Weaknesses (CWE)CWE-400, CWE-862
AttributionDragonForce (high confidence)
Nation-state nexusMalaysia
MalwareBackdoor.Turn, DragonForce, ransombay
ToolsABYSSWORKER
MITRE ATT&CK techniquesT1021 Remote Services, T1027 Obfuscated Files or Information, T1036.005 Match Legitimate Resource Name or Location, T1046 Network Service Discovery, T1059.001 PowerShell, T1087.002 Domain Account, T1090.002 External Proxy, T1112 Modify Registry, T1136.001 Local Account, T1190 Exploit Public-Facing Application, T1555.003 Credentials from Web Browsers, T1573 Encrypted Channel and 3 more in the attack flow
MotivationFINANCIAL
Target sectorsprofessional services
Target regionsNorth America
Detection rules9 (1 shown free)
Sources11 cited sources

Detection coverage

As of 2026-06-16, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-2181 across Splunk SPL, Microsoft KQL and Sigma, covering 30 indicator(s) of compromise. The whole corpus is readable without an account. Every threat comes with one complete detection in Splunk SPL, Microsoft KQL and Sigma, free for everyone; a free account adds daily TL Creds to unlock the rest. Paid plans add a larger daily allowance, correlation and the MCP server. Threadlinqs MCP server · View plans.

Free detection: DragonForce BYOVD Driver Abuse and DbgView64 DLL Side-Loading

Detects loading of the vulnerable/malicious kernel drivers (Topaz Antifraud wsftprm.sys, Tower of Fantasy GameDriverX64.sys, K7 Security K7RKScan.sys, Huawei HWAuidoOs2Ec.sys, and the ABYSSWORKER driver masquerading as CrowdStrike Falcon) that DragonForce operators abuse via crafted IOCTL requests to terminate protected security processes, plus the companion DLL side-load of vboxrt.dll into the legitimate DbgView64.exe process used to host Backdoor.Turn, and the LimitBlankPassword registry change, local backdoor-account creation, and host firewall modifications used for follow-on persistence.

Splunk SPL

(index=sysmon sourcetype="XmlWinEventLog:Microsoft-Windows-Sysmon/Operational" EventCode=6 (ImageLoaded="*wsftprm.sys" OR ImageLoaded="*GameDriverX64.sys" OR ImageLoaded="*K7RKScan.sys" OR ImageLoaded="*HWAuidoOs2Ec.sys" OR Hashes="*8284c8676cc22c4b2e66826ac16986da7ddecba1f2776b16771be17bfdc45dc2*"))
OR (index=sysmon sourcetype="XmlWinEventLog:Microsoft-Windows-Sysmon/Operational" EventCode=7 Image="*DbgView64.exe" ImageLoaded="*vboxrt.dll")
OR (index=wineventlog sourcetype="WinEventLog:Security" EventCode=4657 ObjectName="*LimitBlankPassword*")
OR (index=wineventlog sourcetype="WinEventLog:Security" EventCode=4720)
OR (index=wineventlog sourcetype="WinEventLog:Firewall" (EventCode=2004 OR EventCode=2005))
| eval detection_reason=case(
    EventCode=6, "BYOVD vulnerable/malicious driver load",
    EventCode=7, "DLL side-load into DbgView64.exe (vboxrt.dll)",
    EventCode=4657, "LimitBlankPassword registry modification",
    EventCode=4720, "Local backdoor account creation",
    (EventCode=2004 OR EventCode=2005), "Host firewall rule added/modified to permit C2")
| table _time, Computer, EventCode, detection_reason, Image, ImageLoaded, ObjectName, TargetUserName, Hashes, User

Microsoft KQL

DeviceEvents
| where Timestamp > ago(24h)
| where ActionType == "DriverLoad"
| where FileName has_any ("wsftprm.sys","GameDriverX64.sys","K7RKScan.sys","HWAuidoOs2Ec.sys") or SHA256 == "8284c8676cc22c4b2e66826ac16986da7ddecba1f2776b16771be17bfdc45dc2"
| project Timestamp, DeviceName, ActionType, FileName, FolderPath, SHA256, InitiatingProcessAccountName
| union (
    DeviceImageLoadEvents
    | where Timestamp > ago(24h)
    | where InitiatingProcessFileName =~ "DbgView64.exe" and FileName =~ "vboxrt.dll"
    | project Timestamp, DeviceName, ActionType="DLLSideLoad", FileName, FolderPath, SHA256, InitiatingProcessAccountName
)
| union (
    DeviceRegistryEvents
    | where Timestamp > ago(24h)
    | where RegistryValueName =~ "LimitBlankPassword"
    | project Timestamp, DeviceName, ActionType="RegistryModify", FileName=RegistryKey, FolderPath="", SHA256="", InitiatingProcessAccountName
)
| union (
    DeviceEvents
    | where Timestamp > ago(24h)
    | where ActionType == "UserAccountCreated"
    | project Timestamp, DeviceName, ActionType, FileName=AccountName, FolderPath="", SHA256="", InitiatingProcessAccountName
)
| sort by Timestamp desc

Sigma

title: DragonForce BYOVD Vulnerable Kernel Driver Load (Backdoor.Turn Intrusion)
id: 9b2f4d6a-1c3e-4a7b-8d5f-2e6a1b3c4d5e
status: experimental
description: Detects loading of kernel drivers known to be abused by DragonForce/Backdoor.Turn operators (Topaz Antifraud wsftprm.sys CVE-2023-52271, Tower of Fantasy GameDriverX64.sys CVE-2025-61155, K7 Security K7RKScan.sys CVE-2025-1055, Huawei HWAuidoOs2Ec.sys, and the ABYSSWORKER driver masquerading as CrowdStrike Falcon) to terminate protected security processes via crafted IOCTL requests ahead of ransomware deployment.
references:
    - https://www.security.com/threat-intelligence/dragonforce-msteams-backdoor
    - https://www.elastic.co/security-labs/abyssworker
author: Threadlinqs Team
date: 2026-06-16
tags:
    - attack.defense-evasion
    - attack.t1562.001
    - attack.t1036.005
    - attack.tool.abyssworker
    - cve.2023.52271
    - cve.2025.61155
    - cve.2025.1055
logsource:
    category: driver_load
    product: windows
detection:
    selection_filename:
        ImageLoaded|endswith:
            - '\wsftprm.sys'
            - '\GameDriverX64.sys'
            - '\K7RKScan.sys'
            - '\HWAuidoOs2Ec.sys'
    selection_hash:
        Hashes|contains: '8284C8676CC22C4B2E66826AC16986DA7DDECBA1F2776B16771BE17BFDC45DC2'
    condition: selection_filename or selection_hash
falsepositives:
    - Legitimate use of Topaz Antifraud, Tower of Fantasy, or K7 Security Anti-Malware products still running an unpatched driver version (rare in hardened enterprise environments)
level: critical

Known false positives:

  • Legitimate installation/update of Topaz Antifraud, Tower of Fantasy, or K7 Security Anti-Malware software still running an unpatched driver version
  • Legitimate Sysinternals DebugView usage alongside a genuine VirtualBox install where a vboxrt.dll load is coincidental and the hash/driver-name checks do not match

Tuning notes: Maintain the vulnerable-driver filename/hash list against Microsoft's official vulnerable-driver blocklist and update as new BYOVD drivers are disclosed (the Huawei HWAuidoOs2Ec.sys abuse here predates its March 2026 public documentation); suppress the firewall/registry/account-creation branches for known change-management windows and correlate the driver-load branch with detection 3's C2 alert on the same host to prioritize triage.

8 more detection rules (Splunk SPL, Microsoft KQL, Sigma) · unlock with TL Creds. Sign up free to unlock the detection rules or query them with the Threadlinqs MCP server (Purple)
  • TechSupV18Fix3 PowerShell Dropper Retrieval — DragonForce Initial Foothold · unlock with TL Creds
  • DragonForce BYOVD Driver Abuse and DbgView64 DLL Side-Loading · unlock with TL Creds
  • Backdoor.Turn C2 via Microsoft Teams TURN Relay and Post-Compromise Lateral Movement · unlock with TL Creds
  • TechSupV18Fix3 PowerShell Dropper Retrieval — DragonForce Initial Foothold · unlock with TL Creds
  • DragonForce BYOVD Driver Abuse and DbgView64 DLL Side-Loading · unlock with TL Creds
  • Backdoor.Turn C2 via Microsoft Teams TURN Relay and Post-Compromise Lateral Movement · unlock with TL Creds
  • TechSupV18Fix3 PowerShell Dropper Retrieval — DragonForce Initial Foothold · unlock with TL Creds
  • Backdoor.Turn C2 via Microsoft Teams TURN Relay and Post-Compromise Lateral Movement · unlock with TL Creds

Indicators of compromise

As of 2026-06-16, Threadlinqs Intelligence tracks 30 indicators of compromise for TL-2026-2181.

Sample indicators (3 of 30)

  • IP address: 62.164.177[.]25
  • Domain: projetosmecanicos[.]com[.]br
  • File hash: 82b37a92589dfd4d67ca87eb9e52ac8e682e8e60d2211f59074cd5ccc693013b

Defanged, TLP:CLEAR. Full set of 30 indicators: unlock with TL Creds.

30 indicators of compromise · unlock with TL Creds. Compare plans

Community OSINT corroboration

1 of this threat's indicators have also been reported by the open-source security community. Community sightings are unverified and are kept separate from Threadlinqs' curated indicators. Indicator values, reporters and campaign linkage are available to authenticated Red-tier users.

Technical analysis

Symantec/Broadcom's Threat Hunter Team documented an intrusion at a U.S. services firm in which the DragonForce ransomware cartel (the group Symantec tracks internally as Hackledorb) maintained access for one to two months before deploying its ransomware payload. Initial access is suspected to involve exploitation of an internet-facing SQL or Microsoft SQL Server, or purchase of existing access from an initial access broker; the exact entry point was not conclusively determined. In December 2025 the operators executed PowerShell commands to retrieve a ZIP archive disguised as a tech-support hotfix ('TechSupV18Fix3.zip') from 192.36.27.51, then used DLL side-loading of a legitimate VirtualBox/DbgView64.exe binary paired with a malicious 'vboxrt.dll' to run reconnaissance and evasion code.

The attackers escalated defense evasion using a bring-your-own-vulnerable-driver (BYOVD) chain: three previously known vulnerable, signed kernel drivers (Topaz Antifraud wsftprm.sys / CVE-2023-52271, Tower of Fantasy GameDriverX64.sys / CVE-2025-61155, and K7 Security K7RKScan.sys / CVE-2025-1055) were abused to terminate protected security processes via crafted IOCTL requests, alongside a novel abuse of a Huawei HWAuidoOs2Ec.sys driver (documented publicly by Huntress only in March 2026, after this intrusion) and ABYSSWORKER -- a custom malicious driver, signed with likely-stolen certificates, that masquerades as a CrowdStrike Falcon driver and was first documented powering Medusa ransomware EDR-killing attacks.

The centerpiece of the intrusion is Backdoor.Turn, a Go-based remote access backdoor injected into the legitimate DbgView64.exe process. Backdoor.Turn requests an anonymous Microsoft Teams visitor token from Microsoft's Skype-backed identity services, uses that token to obtain credentials for a legitimate Microsoft TURN (Traversal Using Relays around NAT) relay server, and then tunnels a direct QUIC session to the attacker's real C2 server through that relay. Because the only traffic a network defender observes is an outbound connection to genuine Microsoft Teams/Skype infrastructure, the technique conceals the true C2 channel entirely within trusted collaboration-platform traffic. Symantec states this is the first known in-the-wild abuse of TURN relay infrastructure for C2 in this manner; the approach mirrors 'Ghost Calls,' a WebRTC/TURN-tunneling C2 technique against Zoom, Teams, and Google Meet publicly presented by Praetorian researcher Adam Crosser (open-sourced as the 'TURNt' tool) at Black Hat USA. Backdoor.Turn supports command execution, process creation, network/TLS-certificate/web-title scanning, LDAP and Active Directory searching, credential-based lateral movement, and browser credential theft.

For persistence and further defense evasion, the operators modified the LimitBlankPassword registry setting, created local backdoor accounts, and altered host firewall rules to permit their C2 communications. After roughly one to two months of dwell time, DragonForce deployed its ransomware payload, encrypting and exfiltrating victim data. DragonForce, active since June 2023, has since March 2025 operated as a formalized ransomware 'cartel' offering white-label branding to affiliates under its 'Ransom Bay' program, and by August-September 2025 had announced coordination partnerships with LockBit and Qilin -- evidence Symantec cites of the group's growing organizational maturity and technical sophistication.

MITRE ATT&CK techniques by tactic:

Lateral Movement

T1021 Remote Services

Defense Evasion

T1027 Obfuscated Files or Information; T1036.005 Match Legitimate Resource Name or Location; T1574.001 DLL

Discovery

T1046 Network Service Discovery; T1087.002 Domain Account

Execution

T1059.001 PowerShell

Command and Control

T1090.002 External Proxy; T1573 Encrypted Channel

defense-impairment

T1112 Modify Registry; T1685 Disable or Modify Tools; T1686 Disable or Modify System Firewall

Persistence

T1136.001 Local Account

Initial Access

T1190 Exploit Public-Facing Application

Credential Access

T1555.003 Credentials from Web Browsers

Remediation

Patches

  • Update Topaz Antifraud beyond the vulnerable wsftprm.sys 2.0.0.0 (CVE-2023-52271)
  • Update Tower of Fantasy's GameDriverX64.sys beyond v7.23.4.7 (CVE-2025-61155)
  • Update K7 Security Anti-Malware to K7RKScan.sys 23.0.0.10 or later (CVE-2025-1055)

Immediate actions

  • Monitor and alert on Microsoft Teams/Skype TURN relay traffic originating from non-interactive, headless, or unexpected processes rather than the Teams client itself
  • Hunt for DbgView64.exe or VirtualBox binaries running from non-standard install paths alongside unexpected companion DLLs such as vboxrt.dll
  • Block/deny-list the known vulnerable driver files by hash and name (wsftprm.sys, GameDriverX64.sys, K7RKScan.sys, HWAuidoOs2Ec.sys, ABYSSWORKER/smuol.sys) via Microsoft's vulnerable driver blocklist (WDAC/HVCI)
  • Block outbound traffic to the identified C2 IP (62.164.177.25) and C2/distribution domains, and alert on retrieval of archives named similarly to TechSupV18Fix3.zip

Workarounds

  • Restrict or closely monitor Microsoft Teams anonymous/guest visitor access where it is not a business requirement
  • Restrict loading of unsigned or unapproved third-party kernel drivers via Windows Defender Application Control policy

Longer-term hardening

  • Enforce Windows Defender Application Control / HVCI-based vulnerable-driver blocklisting fleet-wide, not just on a per-incident basis
  • Deploy network egress inspection capable of flagging anomalous QUIC sessions tunneled through legitimate collaboration-platform relay infrastructure
  • Harden and restrict internet exposure of SQL/MSSQL servers, and patch aggressively, given the suspected initial access vector
  • Deploy EDR with kernel self-protection / tamper resistance capable of surviving BYOVD-based process-termination attacks

Affected and fixed versions

  • Topaz Evolution — Antifraud (wsftprm.sys kernel driver)
    Vulnerable versions: 2.0.0.0 and prior
    Fixed in: not publicly specified
  • Hotta Studio — Tower of Fantasy (GameDriverX64.sys kernel driver)
    Vulnerable versions: 7.23.4.7 and prior
    Fixed in: not publicly specified
  • K7 Security — K7 Security Anti-Malware (K7RKScan.sys kernel driver)
    Vulnerable versions: prior to 23.0.0.10
    Fixed in: 23.0.0.10
  • Huawei — HWAuidoOs2Ec.sys kernel driver
    Vulnerable versions: novel BYOVD abuse documented by Huntress March 2026, no public patch identified in sources
  • Microsoft — Microsoft Teams / Skype TURN relay infrastructure (abused as a covert channel, not itself vulnerable)

Timeline

  • DragonForce ransomware-as-a-service operation (tracked by Symantec as Hackledorb) begins operating.
  • DragonForce rebrands as a ransomware 'cartel,' offering white-label affiliate branding under its 'Ransom Bay' model.
  • DragonForce announces a cartel partnership with LockBit, taking a cut to handle encryptors, infrastructure, and negotiation portals for partners.
  • DragonForce publicly announces a coordination partnership with Qilin and LockBit to share resources and dictate ransomware market conditions.
  • Attackers gain access to a U.S. services firm's network, executing PowerShell commands to retrieve locked-ioc-16 from 192.36.27.51, a ZIP archive disguised as a tech-support hotfix.
  • Operators DLL side-load a malicious locked-ioc-26 alongside the legitimate VirtualBox/locked-ioc-21 binary to run reconnaissance and detection-evasion code.
  • Attackers deploy multiple BYOVD drivers (locked-ioc-25/CVE-2023-52271, locked-ioc-17/CVE-2025-61155, locked-ioc-23/CVE-2025-1055, locked-ioc-18, and ABYSSWORKER) to terminate protected security processes.
  • Backdoor.Turn is injected into the legitimate locked-ioc-21 process, establishing C2 by obtaining an anonymous Teams visitor token and tunneling a QUIC session through a legitimate Microsoft TURN relay.
  • Attackers conduct LDAP/Active Directory enumeration, harvest browser-stored credentials, and move laterally across the victim network using stolen credentials.
  • After roughly one to two months of dwell time, the DragonForce ransomware payload is deployed, encrypting and exfiltrating victim data.
  • Huntress researchers publicly document the locked-ioc-18 Huawei driver vulnerability used in the intrusion, after the attack had already occurred.
  • Symantec's Broadcom Threat Hunter Team publishes 'Hidden in Teams,' disclosing Backdoor.Turn and the Microsoft Teams TURN relay C2 evasion technique; Help Net Security and The Hacker News report on the findings the same day.

Sources cited

More from DragonForce

Other reports on CVE-2023-52271

Previous and next in ransomware

Drafted by the Threadlinqs research pipeline from 11 sources; published ; last updated —.

Threadlinqs Intelligence — Real-Time Threat Detection Platform

// threat_feed
$ sort --newest
Showing all threats

Live intelligence console

Threat level

Latest Threats