Quasarrat
Table of Contents
Overview
QuasarRAT (frequently tracked as Quasar, Quasar Remote Administration Tool, and Backdoor:MSIL/Quasar) is a powerful open-source remote access trojan coded in C# (.NET). While originally published on GitHub by developer 'MaxXor' as an administrative management utility, the software's lightweight architecture, robust TLS encryption, and modular design led to widespread weaponization across cybercrime groups and advanced persistent threat (APT) actors. The implant establishes reverse TCP connections to command-and-control infrastructure using TLS-secured sockets with optional certificate pinning to defeat SSL/TLS inspection proxies. Once connected, Quasar delivers an exhaustive suite of surveillance capabilities: real-time desktop screen streaming, audio capturing, keystroke logging, reverse socks5 proxy routing, file system traversal, remote shell access, and process management. It systematically extracts stored credentials from web browsers (Chrome, Edge, Firefox), FTP clients, and email clients. Multiple government advisories (including CISA Alert AA18-337A) highlight Quasar's deployment by nation-state actors including APT10 and APT33 for long-term target surveillance.
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.
- APT10, APT33, Gaza Cybergang, Diverse Cybercrime Actors High confidence
Basis:
Family Pedigree & Lineage
Malware authors regularly fork and iterate upon existing codebases. Observed upstream lineage and downstream variants for this family include:
Derived From / Upstream Ancestry: Quasar Open-Source Repository
Known Derivatives & Downstream Variants: Quasar Rat V1.3 · Quasar Rat V1.4 · Custom Apt-Modified Quasar
MITRE ATT&CK Techniques
Observed techniques used by this family, mapped to our technical analysis hubs and the official MITRE ATT&CK framework:
| Technique | Name | Tactic | Official Spec |
|---|---|---|---|
T1059.003 | Windows Command Shell | execution | ATT&CK ↗ |
T1056.001 | Keylogging | credential-access | ATT&CK ↗ |
T1573.002 | Asymmetric Cryptography | command-and-control | ATT&CK ↗ |
T1021.001 | Remote Desktop Protocol | lateral-movement | ATT&CK ↗ |
T1547.001 | Registry Run Keys / Startup Folder | persistence | ATT&CK ↗ |
T1082 | System Information Discovery | discovery | ATT&CK ↗ |
T1113 | Screen Capture | collection | ATT&CK ↗ |
T1041 | Exfiltration Over C2 Channel | exfiltration | ATT&CK ↗ |
Tactical Mitigations
Based on the techniques used by this family, consider the following defensive strategies:
- T1056.001: Implement Endpoint Detection and Response (EDR) to monitor for suspicious API calls related to keystroke interception. Enforce Multi-Factor Authentication (MFA) to render stolen passwords useless.
- T1059.003: Restrict execution of Windows Command Shell (cmd.exe) and block unauthorized batch scripts.
- T1113: Monitor for frequent or unauthorized screen captures or clipboard reads. Restrict background applications from accessing desktop APIs.
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-RDP | RDP Access Controls & NLA | Harden | T1021.001 | Enforce Network Level Authentication (NLA) on RDP and restrict remote desktop ports via host firewalls. |
D3-EAF | Egress Analysis and Filtering | Isolate | T1041 | Enforce perimeter TLS inspection and alert on anomalous outbound data volume ratios transmitting over active C2 channels. |
D3-MFA | Multi-factor Authentication | Harden | T1056.001 | Enforce FIDO2 / WebAuthn physical tokens to render keystroke-intercepted passwords useless. |
D3-PBA | Process Spawn Analysis | Detect | T1059.003 | Inspect command-line arguments and anomalous parent-child relationships spawning from cmd.exe. |
D3-SDA | System Discovery Analysis | Detect | T1082 | Alert on rapid enumerations of systeminfo, hostname, and registry hardware trees in short intervals. |
D3-SD | Screen Capture Detection | Detect | T1113 | Monitor desktop graphics API calls (BitBlt, GetDC) triggered by non-standard background threads. |
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-NTI | Encrypted Traffic Analysis | Detect | T1573.002 | Inspect TLS handshake metadata (JA3/JA4 fingerprints) to identify malicious encrypted C2 sessions. |
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.
| Protocols | TLS, TCP |
|---|---|
| Observed ports | 443, 4782, 8888 |
| Identifiable from traffic alone | Medium |
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.
a4c7e6b0142b6a7a58a7be8e7e1273934d70b6d19a2e31d4512b18972b9a1111f7b2c93847849e7552eb412854c6020c644d622830f0f35a4d467888b13d2222
Delivery vectors
spear_phishing_attachmentsmalicious_office_macrossoftware_cracks
Persistence mechanisms
HKCU\Software\Microsoft\Windows\CurrentVersion\RunScheduled Task Creation
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_QUASARRAT_T1_ARTIFACT {
meta:
description = "Tier 1 Primitive Artifact: Raw string matches for Quasarrat"
tier = "T1 - Primitive Artifact"
confidence = "Low-Medium (Fast Triage)"
author = "SystemHelpdesk Threat Research Desk"
date = "2026-10-14"
strings:
$s1 = "quasarrat" ascii wide nocase
$s2 = "quasar rat" ascii wide nocase
$s3 = "quasar" ascii wide nocase
$s4 = "backdoor.msil.quasar" ascii wide nocase
$s5 = "win32/quasar" 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 - Quasarrat (Rat) Execution & Triage
id: 44cf2879-504c-50db-b642-f3facbcacf5c
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
with the Quasarrat 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/quasarrat
- 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.t1573_002
- attack.t1021_001
- attack.t1547_001
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_QUASARRAT_T3_ATTRIBUTION {
meta:
description = "Tier 3 Attribution Fingerprint: Heuristic detection for Quasarrat 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 = "quasarrat" 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
}
Containment & Response Steps
Ordered checklist for responders. Adapt to your environment and engage professional support for active incidents.
- Terminate suspicious .NET processes executing out of user temporary or AppData directories.
- Inspect and remove unauthorized autostart registry entries under CurrentVersion\Run.
- Sever active outbound TCP connections to unknown IP addresses on ports 4782 or 443.
- Force domain password resets for all users whose workstations show evidence of Quasar execution.
What to Avoid
Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.
- Do not treat Quasar as a legitimate administrative tool in enterprise environments; its presence indicates unauthorized access.
- Avoid relying solely on default port monitoring; Quasar's C2 port is freely configurable by the operator.
- Do not overlook infected developer machines where .NET tools might otherwise escape suspicion.
References & External Analysis
- CISA Advisory AA18-337A: Overview of Quasar RAT
- MITRE ATT&CK Software Profile: Quasar (S0262)
- GitHub: Quasar Development Repository
- CISA Advisory: AA18-337A
- Search "quasarrat" on VirusTotal (External Analysis)
- Search "quasarrat" on Any.Run (Sandbox Sandbox)
- Search "quasarrat" on MalwareBazaar (Malware Samples)
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: AA18-337A ↗
Frequently Asked Questions
What is QuasarRAT?
QuasarRAT is an open-source .NET remote access trojan that provides threat actors with encrypted remote administration, desktop monitoring, keylogging, and credential theft capabilities.
Who uses Quasar RAT?
Quasar is used by a broad spectrum of threat actors, from low-tier cybercriminals conducting credential theft to advanced nation-state groups like APT10 and APT33 executing targeted corporate espionage.
How does Quasar encrypt its network traffic?
Quasar encrypts C2 communications using AES-128 or AES-256 over custom TLS connections, frequently embedding self-signed certificates into clients to authenticate the server.
What data does Quasar RAT steal from infected computers?
Quasar extracts stored passwords from web browsers, email clients, FTP utilities, Windows credentials vaults, real-time keystroke logs, and webcam/audio feeds.
How do defenders detect Quasar RAT?
Defenders detect Quasar by inspecting suspicious .NET assemblies executing from user directories, monitoring outbound TLS traffic on non-standard ports, and checking autostart registry entries.
How do I remove the Quasarrat Rat from Windows?
Manual removal of Quasarrat 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 Quasarrat a virus or a Rat?
Quasarrat is classified as a Rat. Unlike traditional viruses that infect files, modern malware like Quasarrat typically operates as a standalone payload designed to compromise systems, steal data, or deploy secondary stage implants.
What are the main symptoms of a Quasarrat infection?
Symptoms of Quasarrat 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 Quasarrat 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.
Machine-readable
Get this profile as JSON: https://malware-families-catalog.systemhelpdesk.com/api/quasarrat.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.