XWorm Plugins Explained
A defensive architectural explanation of why XWorm's modularity means two samples labeled 'XWorm' may have very different capability profiles.
XWorm is not simply one fixed executable with an identical capability set. Plugins can extend the RAT. This means the combination of core plus plugins creates a different behavioral profile per operator.
- Core capability — present in the base client.
- Plugin capability — loaded by a modular component.
- Campaign-specific capability — observed in a particular campaign.
- Modified-build capability — added by a cracker or third party.
How the plugin bus works (as published)
Trellix describes a command that carries the SHA-256 hash of a DLL plus its arguments. If the client has not already cached that hash, it asks the listener for the plugin, receives it encoded, and loads it in memory — plugins observed in the wild have been cached under a per-user registry key. This site does not reproduce the loading recipe or command grammar; the architecture is described only to explain why capability profiles differ between samples.
Named modules documented in the 6.x set (Trellix, Oct 2025)
Trellix counted more than 35 plugins across the 6.0–6.5 generation. Rootkit.dll is described as a modified r77. ResetSurvival.dll abuses registry configuration so that a system reset does not clear the foothold. Ransomware.dll is covered separately — see Ransomware Capability. This is a capability inventory, not a loading guide.
Therefore "XWorm capability" should not automatically mean "capability observed in every XWorm sample." See Capability Matrix and Architecture.



