STATUS: ACTIVE
XWorm Full Tech — Pricing Upon Demand
Technical Analysis

Inside XWorm's Architecture

A conceptual breakdown of the XWorm client, configuration, C2 communication, command handler, and plugin framework.

AUTHOR: Threat Intelligence Research TeamUPDATED: 2026-10-04VERIFIED: 2026-10-04
CORE CLIENT
↓
CONFIGURATION
↓
C2 COMMUNICATION
↓
COMMAND HANDLER
↓
PLUGIN FRAMEWORK
↓
OPTIONAL MODULES

Core Client

Responsible for startup, host identification, C2 establishment, command processing, and basic remote-access operations. The core is the minimal footprint that establishes and maintains the operator channel.

Configuration

May contain data such as the C2 address, port, campaign identifier, version identifier, mutex, timing values, and persistence settings. Active C2 credentials are never exposed on this site.

C2 Communication

Research has documented direct socket/TCP-based C2 architectures across versions, typically using encrypted network sessions to attacker-controlled infrastructure. See How XWorm Command-and-Control Works.

Command Handler

Receives and dispatches operator tasking. The handler routes instructions to either built-in core functions or to loaded plugins, which is why capability profiles vary between builds.

Plugin Framework

Additional functionality can be loaded by modular components. Plugins matter because they enable a smaller core payload, capabilities that change between operators, functionality that evolves over time, and infections that do not contain identical modules. See XWorm Plugins Explained.

Why modularity matters for defenders
"XWorm capability" should not automatically mean "capability observed in every XWorm sample." Distinguish core, plugin, campaign-specific, and modified-build capability throughout analysis.

Evasion and self-protection, as published

Published anti-analysis behavior includes debugger checks, a virtual-machine/sandbox exit, an ip-api lookup used to abort if the host's address belongs to a hosting provider or a known analysis network, and a terminate-on-Windows-XP check — Netskope noted the same XP check is also used by AsyncRAT. Delivery chains have disabled or bypassed AMSI before reflective loading.

Forcepoint and Gurucul both document in-memory execution, including process hollowing into a suspended legitimate process such as RegSvcs.exe. Netskope described a critical-process trick in one 6.0 sample: marking the host process critical so that stopping it can bugcheck the host, after which a Run-key entry restarts XWorm on reboot. Persistence observed in the wild is a Run key, a startup shortcut, or a hidden scheduled task — some builds do not survive a reboot at all, so there is no single persistence artefact.

References

  1. [1]Trellix, Old Loader, New Threat: Exploring XWorm RAT's Distribution and Tactics, 2023-07-31
  2. [2]Palo Alto Networks, XWorm persistence and XCoder/EvilCoder attribution research, 2023
  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]Forcepoint, Excel add-in (.xlam) to in-memory XWorm 6.5, 2025-09
  9. [9]Gurucul, XWorm v7 infection chain: process hollowing, AES config, keyboard hook, 2026-02-11
XWorm Full Tech Access — Pricing Upon Demand — Access Granted, Network Mapped
Professional Spy Phones ZERO-CLICK Spyware
Contact us on Telegram