Xorer
Table of Contents
Overview
Xorer (cataloged across security intelligence feeds under signatures including Virus:Win32/Xorer, Worm:Win32/Xorer, and Trojan.Xorer) is a notorious polymorphic Windows PE file infector and network worm active since 2006. Originating in East Asia, Xorer combines aggressive file infection with automated worm propagation over removable USB drives and local network shares. Upon execution, Xorer terminates endpoint security processes, hooks native file access APIs, and injects viral decryptor routines into 32-bit PE executable files across all mounted drives. Furthermore, it creates hidden autorun.inf files on flash drives, disables Windows Safe Mode, prevents access to the Registry Editor and Task Manager, and establishes encrypted backdoor connections to remote C2 servers.
Known aliases
Threat reports may refer to this family under multiple names:
Family Pedigree & Lineage
Malware authors regularly fork and iterate upon existing codebases. Observed upstream lineage and downstream variants for this family include:
Known Derivatives & Downstream Variants: Virus:Win32/Xorer.A · Virus:Win32/Xorer.B
MITRE ATT&CK Techniques
This family has been observed using the following ATT&CK techniques: T1055.001 · T1091 · T1562.001 · T1112 · T1547.001
MITRE D3FEND™ Defensive Countermeasures
Defensive techniques mapped to counter the offensive tradecraft observed in this family (via the MITRE D3FEND matrix):
| D3FEND ID | Countermeasure Name | Tactic | Countered ATT&CK | Defensive Guidance |
|---|---|---|---|---|
D3-DIA | DLL Injection Analysis | Detect | T1055.001 | Monitor remote thread creation (CreateRemoteThread) and unauthorized DLL loading into core Windows processes (svchost.exe, explorer.exe). |
D3-RMC | Removable Media Access Control | Harden | T1091 | Enforce Group Policy settings disabling Windows autorun and block execution permissions on removable USB storage media. |
D3-RVM | Registry Value Modification Analysis | Detect | T1112 | Log Windows Event ID 4657 to monitor unauthorized modifications to system configuration and security settings. |
D3-RPM | Registry Persistence Monitoring | Detect | T1547.001 | Audit and restrict write privileges to user and machine-level Registry Run/RunOnce keys using Endpoint Privilege Management. |
D3-STA | Security Tool Anti-Tamper Enforcement | Harden | T1562.001 | Block unauthorized modification of antivirus registry flags and prevent stopping security agent services. |
Tiered Detection Rules (Cisco CAIRN Model)
Modern threat detection requires multi-layered rule engineering. We classify detections into three operational tiers based on signal fidelity:
Tier 1 Primitive Artifact Rule (Fast Triage)
Matches raw strings and file markers. Vulnerable to binary repacking and simple obfuscation.
rule MALWARE_WIN_XORER_T1_ARTIFACT {
meta:
description = "Tier 1 Primitive Artifact: Raw string matches for Xorer"
tier = "T1 - Primitive Artifact"
confidence = "Low-Medium (Fast Triage)"
author = "SystemHelpdesk Threat Research Desk"
date = "2026-10-14"
strings:
$s1 = "xorer" ascii wide nocase
$s2 = "virus:win32/xorer" ascii wide nocase
$s3 = "worm:win32/xorer" ascii wide nocase
$s4 = "trojan.xorer" ascii wide nocase
$s5 = "win32/xorer" ascii wide nocase
$s6 = "xorer.worm" ascii wide nocase
condition:
uint16(0) == 0x5a4d and any of them
}
Tier 2 Behavioral Context Rule (Process Chains & Sigma)
Tracks parent-child process anomalies and suspicious scripting telemetry. Resilient against file renames.
title: SystemHelpDesk Detection - Xorer (Worm) Execution & Triage
id: 94a26ee9-46bb-5221-b18b-4dec5ac53f90
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
with the Xorer malware family. Detects suspicious execution from temporary user
directories with hidden window flags and background transfer utilities.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/xorer
- https://malware-families-catalog.systemhelpdesk.com/defensive/ransomware-protection
- https://malware-families-catalog.systemhelpdesk.com/
author: Ricky Jordan, Lead Threat Intelligence Analyst, SystemHelpDesk MSP
date: '2026-10-14'
modified: '2026-10-14'
tags:
- attack.worm
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1055_001
- attack.t1091
- attack.t1562_001
- attack.t1112
- attack.t1547_001
logsource:
category: process_creation
product: windows
detection:
selection_process:
Image|endswith:
- \cmd.exe
- \powershell.exe
- \cscript.exe
- \wscript.exe
CommandLine|contains:
- AppData\Local\Temp
- -WindowStyle Hidden
- /e:jscript
- bitsadmin /transfer
condition: selection_process
falsepositives:
- Legitimate enterprise administrative scripts during approved change windows
- Authorized IT software deployment utilities and backup management agents
level: medium
Tier 3 Attribution Fingerprint Rule (High Fidelity)
Deep signature matching distinctive operational fingerprints and payload characteristics.
rule MALWARE_WIN_XORER_T3_ATTRIBUTION {
meta:
description = "Tier 3 Attribution Fingerprint: Heuristic detection for Xorer tradecraft"
tier = "T3 - Attribution Fingerprint"
confidence = "High (Confirmed Family Signature)"
author = "SystemHelpdesk Threat Research Desk"
date = "2026-10-14"
strings:
// Core family identifier & heuristic payload signatures
$attrib_str = "xorer" ascii wide nocase
$pe_magic = "MZ" ascii
$net_marker = "http" ascii nocase
condition:
uint16(0) == 0x5a4d and ($attrib_str and $net_marker) and filesize < 15MB
}
References & External Analysis
- Microsoft Defender Threat Encyclopedia - Virus:Win32/Xorer
- Trend Micro Threat Encyclopedia - PE_XORER
- Search "xorer" on VirusTotal (External Analysis)
- Search "xorer" on Any.Run (Sandbox Sandbox)
- Search "xorer" on MalwareBazaar (Malware Samples)
Frequently Asked Questions
What is Virus:Win32/Xorer?
Xorer is a destructive polymorphic file-infecting worm that corrupts PE executables and spreads via USB flash drives and network shares.
How does Xorer infect executable files?
It traverses local and network drives, appending polymorphic encrypted shellcode to 32-bit PE binaries and redirecting the entry point.
How does Xorer spread across removable media?
It copies hidden executable files to USB drives alongside an autorun.inf configuration to trigger execution when inserted.
How does Xorer impair Windows security tools?
It modifies registry policies to disable Task Manager and Regedit, terminates antivirus processes, and disables Safe Mode booting.
How can an enterprise remediate a Xorer outbreak?
Boot from offline recovery media, run specialized antimalware disinfectors to repair infected PE binaries, and restore corrupted system files.
How do I remove the Xorer Worm from Windows?
Manual removal of Xorer is highly discouraged as it may leave persistence mechanisms intact. We recommend disconnecting the device from the internet and utilizing a professional incident response service or enterprise-grade EDR software to conduct a full forensic sweep.
Is Xorer a virus or a Worm?
Xorer is classified as a Worm. Unlike traditional viruses that infect files, modern malware like Xorer typically operates as a standalone payload designed to compromise systems, steal data, or deploy secondary stage implants.
What are the main symptoms of a Xorer infection?
Symptoms of Xorer can include unexpected system slowness, unauthorized outbound network traffic to unknown IP addresses, disabled security software, and suspicious background processes running from AppData or Temp directories.
Protect Your Network Against Worms
Want to prevent Xorer and similar threats from compromising your organization? Read our comprehensive defensive guide: Worm & Virus Protection.
📣 Threat Intel Correction or Update?
Notice an outdated IOC, unlisted alias, or disputed attribution? Threat researchers are invited to propose an update on GitHub or contact the SystemHelpDesk research desk. All community revisions are credited in our public CHANGELOG.
Machine-readable
Get this profile as JSON: https://malware-families-catalog.systemhelpdesk.com/api/xorer.json
Ecosystem & Interactive Environments
This profile is part of the Malware Families Catalog, a public dataset of 2,899 malware families. The catalog is also published across our ecosystem: Hugging Face, Kaggle, Zenodo, Replit, StackBlitz, CodeSandbox, and CodePen.