In short
XWorm is a commodity remote access trojan for Windows, built on .NET and used by criminals. It lets an operator run commands, log keystrokes, take screenshots, move files, launch DDoS attacks and load plugins. It spreads through phishing attachments, other malware and removable drives, and leaked builders make it widely available.
Key takeaways
- What it is
- A .NET remote access trojan for Windows, offered as a builder kit, with many versions from V3.1 to 6.x in circulation.
- How it works
- It persists through a Run key, adds Defender exclusions, talks to its C2 over TCP and offers keylogging, screenshots, DDoS and plugins.
- Why it matters
- Forcepoint documented a 2025 chain from an invoice-themed Excel add-in to memory-only loaders, which evades file-based scanning.
- What Odin Research saw
- Ready-to-compile XWorm 5.6 source posing as a Windows Update helper, and XWorm panels staged beside other RAT kits and tax lures.
- What to do first
- Alert on AppData Run keys, PowerShell Defender exclusions and on-host .NET compiling. Reset credentials after any infection.
What is XWorm?
XWorm is a commodity remote access trojan (RAT) for Windows, built on .NET and widely available to criminals as a ready-made kit. It gives an operator remote control of an infected computer, with keylogging, screenshots, file transfer, DDoS commands and add-on plugins. Builder versions circulate widely, including cracked and leaked copies.
Security vendors track many XWorm versions. Trend Micro's encyclopedia entry lists vendor names such as Kaspersky's UDS:Backdoor.MSIL.XWorm.gen and Microsoft's Trojan:MSIL/XWorm.C!MTB. Forcepoint analyzed a 2025 sample that identified itself as XWorm client 6.5, and Odin Research found source code for version 5.6.
XWorm is a classic remote access trojan. It is malware, not a dual-use admin tool. Odin Research found cracked builders and leaked source, so many unrelated criminals can run it.
How XWorm works
Trend Micro describes an XWorm variant first received in February 2024. Its capabilities give a good picture of the family:
- Remote commands. Download and run files, run shell commands, shut down, restart or log off the PC, and launch DoS or DDoS attacks.
- Collection. Log keystrokes, capture screenshots and gather system details such as user name, OS, hardware, webcam availability, admin rights and installed antivirus.
- Plugins. Run add-on plugins that can be stored in the registry.
- Spreading. Copy itself to removable drives, hide the original files and create shortcuts that start the malware along with them.
- Defense evasion. Add Microsoft Defender exclusions for its own paths and processes through PowerShell.
That variant talks to its command-and-control server over TCP. For persistence it adds a value to the current user's Run key that points to a copy in the user's application data folder, so it starts at every logon. This is Registry Run Keys / Startup Folder (T1547.001). A mutex keeps a single copy running.
How XWorm spreads
Trend Micro says the variant it analyzed arrives dropped by other malware, downloaded from malicious websites, or through removable drives.
Forcepoint X-Labs documented a 2025 chain that started with phishing:
- An invoice-themed email carried an Excel add-in (
.xlam) attachment. - The file opened as blank or corrupted. An embedded OLE object hid encrypted shellcode.
- The shellcode downloaded a first-stage executable into the user's AppData folder.
- That .NET program loaded a second-stage DLL from its resources in memory, which loaded a third stage.
- The final stage injected into the first-stage process and connected to its C2 server.
The middle stages never touched disk. That is reflective code loading followed by process injection, and it is why file scanning alone often misses XWorm.
What Odin Research observed
Odin Research found XWorm on exposed attacker staging servers in two reports. These are staged files. Nothing in the data shows they were used against a target.
- Ready-to-compile source. In Monograph 08, a server in Russia exposed 209 files, including 323,901 bytes of unobfuscated XWorm 5.6 Visual Basic .NET source in four files.
- A fake Windows Update helper. The source posed as "Windows Update Helper" from "Microsoft Corporation". That is only metadata. The builds carry no valid Microsoft signature. This is masquerading.
- Compile on the target. A small batch file was written to fetch the source and compile it on the target with the built-in .NET compiler, so no known binary hash ships.
- Script add-ons. Short PowerShell scripts added keystroke capture, screenshots, command polling and file theft without a custom executable.
- Distrust of a cracked panel. Four scripts audited a cracked XWorm V3.1 builder for a hidden backdoor before use, which fits a criminal operator rather than a research lab.
- Several kits as backup. In Monograph 26, a second staging server held XWorm version 6 and 5.6 panels next to full XenoRAT and Remcos kits, HVNC builds and corporate tax lures.
Monograph 08 also checked feed lists of commodity RATs. Only 6 of 920 recently active candidates were confirmed live C2 servers. Passive RAT lists age fast on recycled VPS addresses.
How to detect XWorm
- Run-key writes. Alert on new Run values that point into AppData, especially names that copy a browser or Windows component.
- Defender exclusions. PowerShell adding Defender exclusions from a user process is rarely legitimate.
- On-host compiling. Alert when
vbc.exeorcsc.exeis started bycmd.exe, PowerShell or a script host outside developer tools. - Inline keyboard hooks. PowerShell script block logs that compile C# with low-level keyboard hooks point to input capture.
- Office add-ins that download. An Office process that writes an executable into AppData fits the chain Forcepoint described.
- Fake publisher strings. Validate Authenticode signatures. Do not trust a "Microsoft Corporation" company name on its own.
Monograph 08 publishes YARA rules for XWorm 5.6 source and the related keylogger script, Suricata signatures for requests for the XWorm source files, and Sigma rules for the endpoint behaviors above. The rules are in the Defense Kit.
How to respond to an XWorm infection
- Isolate the machine and capture memory. Later stages may live only in memory.
- Remove persistence. Check Run keys, the Startup folder and scheduled tasks, and remove any Defender exclusions the malware added.
- Reset credentials. Assume keystrokes and saved passwords were captured. Reset passwords and revoke sessions for every account used on the machine. See how to handle leaked credentials.
- Check removable media that touched the host, since some variants spread through USB drives.
- Block confirmed C2 only. Confirm a RAT controller is live before you block it permanently.
XWorm compared with other commodity RATs
| RAT | Platform | Odin data | Notes |
|---|---|---|---|
| XWorm | Windows .NET | Source and panels on staging servers (Monographs 08 and 26) | Builders leaked and cracked |
| AsyncRAT | Windows .NET | 121 listeners on 55 IPs (Monograph 15) | MessagePack over TLS |
| Quasar | Windows .NET | 33 listeners (Monograph 15) | Protobuf over TLS |
| DCRat | Windows .NET | 13 listeners (Monograph 15) | Modular C2 |
| PureRAT | Windows .NET | 61 endpoints (Monograph 26) | Sequential high ports 56001 to 56003 |
Frequently asked questions about XWorm
What is XWorm?
XWorm is a commodity .NET remote access trojan for Windows. It gives criminals remote control of infected computers, with keylogging, screenshots, file transfer, DDoS and plugin features.
Is XWorm a virus or a RAT?
XWorm is a remote access trojan. Some variants also copy themselves to removable drives, which is why Trend Micro classes one variant as a worm.
How does XWorm get on a computer?
Trend Micro says it is dropped by other malware, downloaded from malicious sites or spread through removable drives. Forcepoint documented phishing emails with Excel add-in attachments.
What can XWorm do?
Trend Micro lists running commands, downloading files, keylogging, screenshots, hiding files and processes, plugins and DoS or DDoS attacks, plus adding Defender exclusions.
How do I detect XWorm?
Look for Run keys that point into AppData, PowerShell adding Defender exclusions, unexpected .NET compiler launches and Office files that download executables. Odin Research publishes YARA, Suricata and Sigma rules in its Defense Kit.
How do I remove XWorm?
Isolate the machine, remove the Run key and other persistence, delete added Defender exclusions and reset all credentials used on it. For a business device, a clean reimage is safer.
Who uses XWorm?
XWorm builders are cracked and leaked, so many unrelated criminals run it. A single XWorm sample does not point to one group.
XWorm vs AsyncRAT: what is the difference?
Both are .NET remote access trojans for Windows. In Odin Research data, AsyncRAT showed up mostly as live C2 listeners, while XWorm showed up as source code and panels on staging servers.
Sources
- Trend Micro, Threat Encyclopedia, Worm.MSIL.XWORM.YXEBVZ. www.trendmicro.com/vinfo/us/threat-encyclopedia/malware/worm.msil.xworm.yxebvz (checked 21 November 2026)
- Forcepoint X-Labs, "XWorm RAT Delivered via Shellcode: Multi-Stage Attack Analysis", updated 26 September 2025. www.forcepoint.com/blog/x-labs/xworm-rat-shellcode-multi-stage-analysis (checked 21 November 2026)
Related tools and terms
What is Quasar?
Quasar is an open-source .NET remote access tool for Windows that criminals and some state actors use as a RAT.
Remote access trojanWhat is AsyncRAT?
AsyncRAT is an open-source .NET remote access trojan widely used in commodity malware campaigns.
Remote access trojanWhat is DCRat?
DCRat (DarkCrystal RAT) is a low-cost commodity .NET remote access trojan sold on underground forums.
Remote access trojanWhat is VenomRAT?
VenomRAT is a commodity remote access trojan descended from the Quasar and AsyncRAT code bases.
Remote access trojanWhat is PureRAT?
PureRAT, also tracked as PureHVNC, is a commercial modular .NET remote access trojan with hidden-desktop control.
Remote access trojanWhat is XenoRAT?
XenoRAT is an open-source C# remote access trojan with hidden-desktop (HVNC) support.
Odin Research
Get the rules, not just the definition
Every Odin Research report ships with verified indicators and detection rules you can load today.