STATUS: ACTIVE
XWorm Full Tech — Pricing Upon Demand
Command & Control

How XWorm Command-and-Control Works

A safe architectural explanation of XWorm C2 communications across versions and campaigns.

AUTHOR: Threat Intelligence Research TeamUPDATED: 2026-10-04VERIFIED: 2026-10-04
COMPROMISED ENDPOINT
↓
XWORM CLIENT
↓
ENCRYPTED SESSION
↓
ATTACKER C2
↓
REMOTE TASKING / COLLECTION

Research has documented direct socket/TCP-based C2 architectures across versions. Different campaigns may use IP addresses, domains, dynamic DNS, temporary infrastructure, abused cloud infrastructure, or loaders that contact separate staging infrastructure.

Some trojanized XWorm-related builds have also incorporated Telegram-based communications. However, core XWorm campaigns frequently use direct C2 infrastructure; Telegram is particularly notable in modified/trojanized ecosystems.

Do not overgeneralize
Do not incorrectly claim "XWorm normally uses Telegram as its primary C2." Core XWorm campaigns frequently use direct C2 infrastructure. Telegram is a legitimate communications platform that can be abused by criminal operators. See XWorm and Telegram.
Cloudflare tunnel abuse
Proofpoint documented campaigns in 2024 using Cloudflare tunnels in attack chains distributing XWorm and AsyncRAT. Temporary legitimate cloud infrastructure presents challenges: infrastructure can be rapidly created, domains/IPs change, static blocklists become less useful. Cloudflare is a legitimate provider whose services can be abused by threat actors — Cloudflare is not associated with development of XWorm.

Version 6+: AES-wrapped beacon

Earlier builds stored their configuration as Base64 and AES. Version 6 keeps the custom TCP protocol but wraps it in AES-256 with a build-time key, which broke network signatures that matched older cleartext beacons. Gurucul's v7 write-up describes the same model: version, address, port, and a shared configuration value (referenced in research as SETTINGS.KEY) pulled from the embedded config at startup. Some samples take the C2 address from a command line passed by a PowerShell stager; others hardcode it — both patterns have been observed. Published beacon ports include 4411 and 10992; these are operator-chosen and are not a family constant.

Network detection must assume AES
Because the beacon is AES-wrapped from version 6 onward, network detection should be matched on behavior (long-lived TCP sessions from non-browser processes, timing, destination reputation) rather than on a cleartext banner signature.

References

  1. [1]Trellix, Old Loader, New Threat: Exploring XWorm RAT's Distribution and Tactics, 2023-07-31
  2. [2]Proofpoint, Cloudflare Tunnel campaigns delivering XWorm and AsyncRAT, 2024
  3. [3]Trellix, XWorm's Evolving Infection Chain: From Predictable to Deceptive, 2025-09-03
  4. [4]Trellix, XWorm V6: Exploring Pivotal Plugins, 2025
  5. [5]FortiGuard Labs, Deep Dive into New XWorm Campaign Utilizing Multiple-Themed Phishing Emails, 2026-02-10
  6. [6]Netskope, XWorm V6.0: hardcoded C2, AMSI-related delivery, anti-analysis, 2025-07-28
  7. [7]Trellix, XWorm V6 plugin analysis (35+ in-memory DLL plugins; Ransomware.dll / NoCry overlap), 2025-10-07
  8. [8]Gurucul, XWorm v7 infection chain: process hollowing, AES config, keyboard hook, 2026-02-11
  9. [9]NTT Security, XWorm V6 technical note — AES-256 C2, 2026-02-04
XWorm Full Tech Access — Pricing Upon Demand — Access Granted, Network Mapped
Professional Spy Phones ZERO-CLICK Spyware
Contact us on Telegram