Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
Back to intelligence
ransomware-group-operationcommand-and-control-methodendpoint-security-bypasslateral-movement-method

DragonForce Hid Malware C2 in Microsoft Teams TURN Relays

Updated 2d agoFirst seen Jun 16, 202611 sources

Symantec reported that the DragonForce ransomware operation used a custom Go-based backdoor, Backdoor.TURN, to hide command-and-control traffic inside Microsoft Teams TURN relay infrastructure during an intrusion at a major U.S. services company. Researchers said the attackers likely gained initial access in December 2025 by exploiting an unknown SQL or MSSQL server flaw or through an initial access broker, then used DLL sideloading, reconnaissance, credential theft, lateral movement, rogue account creation, and firewall changes while remaining undetected for as long as two months. The malware reportedly obtained an anonymous visitor token through Microsoft’s Skype-linked identity services, authenticated to Teams infrastructure, relayed traffic through TURN servers, and then established a QUIC session to the real C2 server.

The intrusion escalated through extensive defense evasion and privilege abuse, including Bring Your Own Vulnerable Driver techniques and use of multiple vulnerable or malicious drivers such as Huawei’s HWAuidoOs2Ec.sys and the custom Abyss Worker driver, alongside drivers tied to CVE-2023-52271, CVE-2025-61155, and CVE-2025-1055. Symantec said the operators used kernel-level access to disable security tools, stole data, and ultimately deployed DragonForce ransomware to encrypt the victim’s systems. Researchers described the campaign as the first known real-world abuse of Microsoft Teams TURN relays for covert C2 and published indicators of compromise to help defenders detect similar attacks.

Share:
DragonForce Hid Malware C2 in Microsoft Teams TURN Relays
Stay ahead

Get ahead of threats like this

Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.

EVENT TIMELINE

How this story unfolded

5 events from the most recent confirmed update back to the earliest known activity.

5 EVENTS
Jun 18, 20264d ago

Symantec links DragonForce activity to Hackledorb

In reporting on the intrusion, Symantec assessed that the increasingly sophisticated tradecraft was tied to Hackledorb, identifying it as the actor behind DragonForce. This attribution accompanied technical details on Backdoor.Turn and Microsoft Teams TURN relay abuse.

DragonForce Hackers Abuse Microsoft Teams Relays to Hide Backdoor.Turn C2 Traffic
Jun 16, 20266d ago

Symantec publishes findings and indicators of compromise

Symantec disclosed the campaign and published indicators of compromise to help defenders detect and block similar attacks. The report detailed the use of Backdoor.Turn, Teams TURN relay abuse, and BYOVD techniques in the DragonForce intrusion.

Ransomware gang abuses Microsoft Teams relays to hide malicious traffic

DragonForce operators deploy ransomware after theft and evasion

After reconnaissance, credential theft, lateral movement, and data theft, the attackers used vulnerable and malicious drivers to disable security tools and then deployed DragonForce ransomware to encrypt the victim's systems. The intrusion reportedly remained undetected for up to two months.

Ransomware gang abuses Microsoft Teams relays to hide malicious traffic

Attackers abuse Microsoft Teams TURN relays for covert C2

During the intrusion, the operators deployed the custom Go-based malware Backdoor.Turn to hide command-and-control traffic inside Microsoft Teams TURN relay infrastructure. Symantec described this as the first known in-the-wild abuse of Microsoft Teams TURN relays for malware C2.

Ransomware gang abuses Microsoft Teams relays to hide malicious traffic
Dec 1, 20257mo ago

DragonForce intrusion begins at major U.S. services company

Symantec reported that a DragonForce ransomware intrusion against a major U.S. services company began in December 2025, likely through exploitation of an unknown SQL or MSSQL server vulnerability or via an initial access broker. The attackers then established persistence and began operating inside the environment.

Ransomware gang abuses Microsoft Teams relays to hide malicious traffic
LINKED ENTITIES

Related entities

Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.

58 LINKEDOpen in app
Affected products
5 linked
WindowsZoomOracle Vm VirtualboxSkypeActive Directory
Organizations
33 linked
Microsoft CorporationBroadcomHuawei TechnologiesPalo Alto NetworksCarbon BlackPraetorianZoom CommunicationsK7 SecurityTopaz AntifraudTower of FantasyOraclePerfect World GamesK7 ComputingLinkedinBlack DuckXHuntressGoogleKeeper SecurityBleepingComputerSectigoPicus SecurityThreatLockerHackread.comMicrosoft SysinternalsSecurity AffairsThe Hacker NewsTopaz SystemsA U.S. services companyU.S. services companyTopaz LabsUnnamed United States services firmUnnamed major United States services firm
Breaches
8 linked
UNNAMEDUSSERVICESCOMPANY-2026-06USSERVICESFIRM-2025-12MAJORUSSERVICESFIRM-2026-06MAJORUSSERVICESCOMPANY-2025-12MAJORUSSERVICESFIRM-2025-12USSERVICESCOMPANY-2026-06USSERVICESCOMPANY-2025-12MAJORUNNAMEDUSSERVICESFIRM-2025-12
The operational view lives in Mallory

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t — which of your assets are affected, which threat actors are using it right now, which detections to deploy, and what to do next.
Exposure mapping

Map indicators from this story to your assets and identify affected systems in minutes.

Threat actor evidence

Every observed campaign, victim, and pivot linked to actors named in this story.

Associated malware

Malware, exploits, and IOCs connected to the activity described here.

Detection signatures

YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.

Scheduled alerts

Get matching new stories delivered to your team as they break — not the next morning.

AI threads

Ask questions about this story and take action on the answers.