Xtrat

Category: rat · Aliases: Xtreme RAT, XtremeRAT, xrat, xtrat, XRat · Sample count (EMBER 2018): 35,969 · Enrichment: curated_sourced · Updated: 2026-10-14
Category: RatStatus: Automated SignaturePlatform: WINDOWS_PEStage: Persistence, Command And Control, Remote AccessFirst seen: 2010Actor: Unknown / CybercriminalIndustry: Global / OpportunisticMotivation: Opportunistic🕸 Explore Relationship Graph⚙ API JSON⚡ Sigma Rule💾 YARA RuleOS: Windows 11, Windows 10, Windows Server 2022
Executive Summary
Xtreme RAT (widely tracked as xtrat or xrat) is a feature-complete, commercial-grade remote access trojan that first surfaced in late 2010.

Table of Contents

Overview

Xtreme RAT (widely tracked as xtrat or xrat) is a feature-complete, commercial-grade remote access trojan that first surfaced in late 2010. Engineered originally by an underground developer known as 'ip-owner' and sold on Arabic and English cybercrime forums, the tool quickly transcended ordinary cybercrime to become a favorite espionage weapon of advanced persistent threat (APT) actors. Xtreme RAT is notorious for its extensive surveillance and operational capabilities: it captures keystrokes, streams live video and audio from attached webcams and microphones, steals browser credentials, manipulates the local registry and file system, and provides interactive reverse command shells. The trojan was prominently deployed by state-sponsored actors including APT28 (Fancy Bear / Sofacy), the Syrian Electronic Army (SEA), and Middle Eastern espionage syndicates targeting defense contractors, government ministries, and political dissidents. Distribution was typically executed via targeted spear-phishing campaigns delivering weaponized Microsoft Office documents exploiting CVE-2012-0158 (ActiveX MSCOMCTL.OCX) and CVE-2014-1761, dropping packed payloads into the AppData directory.

Known aliases

Threat reports may refer to this family under multiple names:

Threat Actor Attribution

Attribution is probabilistic, not a science. Each link below states its confidence level and the evidence behind it.

→ Explore all Threat Actor & APT Campaign Profiles

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: Xtremerat V2 · Xtremerat V3 · Mof_Variant

MITRE ATT&CK Techniques

Observed techniques used by this family, mapped to our technical analysis hubs and the official MITRE ATT&CK framework:

→ Explore the complete 226-Technique ATT&CK Threat Matrix

Tactical Mitigations

Based on the techniques used by this family, consider the following defensive strategies:

MITRE D3FEND™ Defensive Countermeasures

Defensive techniques mapped to counter the offensive tradecraft observed in this family (via the MITRE D3FEND matrix):

D3FEND IDCountermeasure NameTacticCountered ATT&CKDefensive Guidance
D3-PIADProcess Injection Analysis & DetectionDetectT1055Monitor cross-process thread creation (CreateRemoteThread) and asynchronous procedure calls (QueueUserAPC).
D3-MFAMulti-factor AuthenticationHardenT1056.001Enforce FIDO2 / WebAuthn physical tokens to render keystroke-intercepted passwords useless.
D3-PBAProcess Spawn AnalysisDetectT1059.003Inspect command-line arguments and anomalous parent-child relationships spawning from cmd.exe.
D3-WAFWeb Content Filtering & InspectionFilterT1071.001Block newly registered domains (NRDs) and inspect HTTP Host and URI headers for known C2 profiles.
D3-NTINetwork Traffic InspectionDetectT1105Inspect deep packet payloads for anomalous staging binaries and unauthorized egress protocols.
D3-SDScreen Capture DetectionDetectT1113Monitor desktop graphics API calls (BitBlt, GetDC) triggered by non-standard background threads.
D3-HACHardware Device Access ControlIsolateT1125Enforce Group Policy hardware access restrictions on integrated webcams and microphones.
D3-RPMRegistry Persistence MonitoringDetectT1547.001Audit and restrict write privileges to user and machine-level Registry Run/RunOnce keys using Endpoint Privilege Management.

Exploited Vulnerabilities (CVEs)

This malware family is documented weaponizing the following common vulnerabilities and exposures:

Command & Control (C2) and Network Profile

How this family talks to its operators. C2 traffic can often identify a family even when its code and configuration are hard to analyse. Ports and patterns are historical and change between campaigns, so use them as hunting leads rather than block-only rules.

ProtocolsTCP, HTTP, Reverse Shell
Observed ports80, 443, 8080, 8181, 1024
Infrastructure modelDynamic DNS (No-IP, DynDNS) domains mapped to dedicated VPS command consoles, configured to receive reverse TCP socket connections from infected endpoints.
Encryption / encodingCustom XOR, RC4, or AES session encryption wrapping a proprietary binary protocol with fixed magic headers ('XTR', 'RAT', 'PING').
Traffic fingerprintPersistent raw TCP connections to non-standard high ports with repetitive keepalive beacon strings ('PING', 'PONG') and base64/hex encoded stream headers containing victim hostname and webcam/mic status.
Identifiable from traffic aloneHigh

Network detection ideas

Sources: MITRE ATT&CK S0036: XtremeRAT, US-CERT / CISA Alert TA14-149A

Indicators of Compromise

Public indicators drawn from CISA advisories and vendor reporting. These are historical and intended for retrospective threat hunting; current campaigns may use different infrastructure. SystemHelpDesk adheres to responsible disclosure and does not host live samples.

File hashes (SHA-256, sample)

Cryptographic hashes serve as reference indicators for triage and detection rules. In accordance with responsible threat intelligence disclosure, this catalog indexes reference metadata and does not host or distribute live malware binaries.

Delivery vectors

Persistence mechanisms

SIEM / EDR Ingestion: Need these reference indicators for threat hunting?

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_XTRAT_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Xtrat"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "xtrat" ascii wide nocase
        $s2 = "xtreme rat" ascii wide nocase
        $s3 = "xtremerat" ascii wide nocase
        $s4 = "xrat" ascii wide nocase
        $s5 = "xtrat" ascii wide nocase
        $s6 = "xrat" 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 - Xtrat (Rat) Execution & Triage
id: 87243534-33c0-5dd6-9c68-a009df07e47b
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Xtrat malware family. Detects unauthorized persistence creation via Windows
  Registry Run keys, scheduled tasks, and privilege escalation indicative of RAT installations.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/xtrat
- https://malware-families-catalog.systemhelpdesk.com/defensive/backdoor-rat-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.rat
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1059_003
- attack.t1056_001
- attack.t1113
- attack.t1125
- attack.t1105
logsource:
  category: process_creation
  product: windows
detection:
  selection_process:
    Image|endswith:
    - \reg.exe
    - \schtasks.exe
    - \cmd.exe
    - \powershell.exe
    CommandLine|contains:
    - \CurrentVersion\Run
    - /create /tn
    - bypass -enc
    - net user /add
    - net localgroup administrators
  condition: selection_process
falsepositives:
- Legitimate enterprise administrative scripts during approved change windows
- Authorized IT software deployment utilities and backup management agents
level: high

Tier 3 Attribution Fingerprint Rule (High Fidelity)

Deep signature matching distinctive operational fingerprints and payload characteristics.

rule MALWARE_WIN_XTRAT_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Xtrat 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 = "xtrat" 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
}
SOC & SIEM Rule Downloads: ⬇ Download YARA Rule (.yar) ⬇ Download Sigma Rule (YAML) ⬇ Download Sigma Rule (JSON) ⚙ Threat Profile API (JSON)

Containment & Response Steps

Home Users: If you suspect a malware infection on your personal device, disconnect from the internet immediately and run a full system scan with your antivirus software (see our TotalAV Antivirus & Security Support Guide). The steps below are intended for IT professionals responding to enterprise incidents.

Ordered checklist for responders. Adapt to your environment and engage professional support for active incidents.

  1. Immediately isolate the compromised host from internal LAN and WAN environments to cut off interactive remote shell sessions established by Xtrat.
  2. Inspect active socket listeners and outbound established network connections ('netstat -ano') to identify and sever covert TCP/UDP channels used by Xtrat.
  3. Scan Windows Services, Scheduled Tasks, and Startup folders to locate and eliminate persistent backdoor listeners configured by Xtrat.
  4. Invalidate all active VPN profiles, local administrator credentials, and session tokens that may have been harvested by the Xtrat operator.
  5. Re-image the affected host using a validated golden image prior to reconnecting it to enterprise network segments.

What to Avoid

Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.

  1. Do not attempt to interact with or send messages through the Xtrat remote terminal, as this alerts the attacker and may cause them to execute destructive anti-forensic commands.
  2. Avoid relying solely on static file signatures, as Xtrat payloads frequently execute reflectively in memory without writing binaries to disk.

References & External Analysis

North American Authority Advisory (CISA / NIST)

The Cybersecurity and Infrastructure Security Agency (CISA) has published an official US federal advisory on this family, which can be mapped to NIST Cybersecurity Framework (CSF) incident response controls: US-CERT Alert TA14-149A (Targeted Attacks Against Defense Entities) ↗

Frequently Asked Questions

What is Xtreme RAT (xtrat)?

Xtreme RAT is a commercial remote access trojan first developed in 2010 that provides complete administrative control over infected systems, including webcam recording, keylogging, and reverse command shells.

Who has used Xtreme RAT in cyberattacks?

Xtreme RAT has been deployed by nation-state actors including Russian APT28 (Fancy Bear), the Syrian Electronic Army (SEA), and Middle Eastern espionage groups targeting government, military, and diplomatic targets.

What vulnerabilities are commonly exploited to deliver Xtreme RAT?

Attackers frequently deliver Xtreme RAT through weaponized Microsoft Office documents exploiting CVE-2012-0158 and CVE-2014-1761 attached to spear-phishing emails.

How does Xtreme RAT communicate with its C2 server?

It uses reverse TCP socket connections over ports such as 8181 or 443 directed toward dynamic DNS hosts, protected by XOR, RC4, or AES session encryption with structured binary keepalives.

How can defenders detect Xtreme RAT infections?

Organizations should monitor outbound connections on non-standard ports for repetitive PING beacons, restrict execution from user AppData folders, and monitor office processes launching child script interpreters.

How do I remove the Xtrat Rat from Windows?

Manual removal of Xtrat 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 Xtrat a virus or a Rat?

Xtrat is classified as a Rat. Unlike traditional viruses that infect files, modern malware like Xtrat typically operates as a standalone payload designed to compromise systems, steal data, or deploy secondary stage implants.

What are the main symptoms of a Xtrat infection?

Symptoms of Xtrat 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 Rats

Want to prevent Xtrat and similar threats from compromising your organization? Read our comprehensive defensive guide: Backdoor & RAT Protection for Businesses.

📣 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.

Need help with an active incident? Published by the SystemHelpdesk team.

Machine-readable

Get this profile as JSON: https://malware-families-catalog.systemhelpdesk.com/api/xtrat.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.