In short
Quasar RAT is a free, open-source remote administration tool for Windows, written in C# and published on GitHub under the MIT license. It offers remote desktop, keylogging and credential theft over an encrypted channel. Criminals and state-linked groups such as Kimsuky and menuPass have used it as a remote access trojan.
Key takeaways
- What it is
- An open-source C# remote administration tool for Windows, tracked by MITRE ATT&CK as QuasarRAT (S0262).
- How it works
- A built client connects back to the operator's server over an encrypted channel and adds keylogging, remote desktop and credential theft.
- Why it matters
- It is free and capable, so both commodity criminals and APT groups use it, which makes attribution hard.
- What Odin Research saw
- 2,938 historical Quasar records in Monograph 08 but only two live controllers; one is published for blocking.
- What to do first
- Hunt the default CN=Quasar Server CA certificate and treat old feed addresses as watchlist leads.
What is Quasar RAT?
Quasar RAT is a free, open-source remote administration tool for Windows, written in C# and published on GitHub under the MIT license. It gives the operator remote desktop, file, keylogging and credential-recovery features. Criminal groups and several state-linked actors have used it as a remote access trojan (RAT).
The project calls itself a "Free, Open-Source Remote Administration Tool for Windows". MITRE ATT&CK tracks it as QuasarRAT (S0262), also known as xRAT, and notes it has been on GitHub since at least 2014.
Quasar sits in the same commodity RAT group as AsyncRAT, DCRat and VenomRAT. Its code is public, so anyone can build a client, rename it or modify it. That is why it shows up in both low-skill crime and targeted espionage.
How Quasar RAT works
Quasar has two parts. The operator runs a server application with a control panel. Each infected Windows machine runs a client that connects back to that server.
- Client build. The operator builds a client that knows where its server is, then places it on the target through whatever access they have.
- Encrypted channel. MITRE ATT&CK lists encrypted C2 over AES and a non-application-layer protocol among its behaviors. Odin's reports describe Quasar traffic as Protobuf messages over TLS.
- Persistence. MITRE maps Quasar to registry run keys and scheduled tasks.
- Collection. MITRE lists keylogging, webcam viewing, remote desktop and theft of saved credentials from browsers and FTP clients.
A stock Quasar server presents a self-signed TLS certificate named CN=Quasar Server CA. Many operators never change it, which makes it one of the most useful hunting signals for this family.
Quasar RAT requirements and versions
According to its README, Quasar needs .NET Framework 4.5.2 or later. It supports 32-bit and 64-bit Windows 11, 10, 8 and 8.1 and 7, and Windows Server 2022, 2019, 2016, 2012 and 2008 R2. Older systems are covered by Quasar version 1.3.0.
Because the code is open, many forks and custom builds exist. MITRE notes that the group APT-C-36 used a customized variant called BlotchyQuasar. A sample may therefore differ from the public release in strings, certificates and features.
Is Quasar legal? The software is MIT-licensed. Using it to control computers without the owner's consent is illegal, whatever the tool is called.
Who uses Quasar RAT
MITRE ATT&CK lists seven groups that have used QuasarRAT: Patchwork, LazyScripter, Gorgon Group, Kimsuky, menuPass (also tracked as APT10 and Stone Panda), BackdoorDiplomacy and APT-C-36.
That list is a reminder that free tools are not only for amateurs. State-linked operators choose them because they are capable, cheap and blend in with crime. Attribution based on "Quasar was used" alone is weak, because thousands of unrelated operators run the same code.
Its use maps to Remote Access Tools (T1219) and, once installed, to Registry Run Keys (T1547.001) and Input Capture (T1056).
What Odin Research observed
- Thousands of records, few live servers. Monograph 08 reviewed 2,938 historical Quasar records across 77 countries, 15.2% of 19,391 commodity RAT records. Only two Quasar controllers were confirmed live between 13 and 16 November 2026.
- Old lists catch new tenants. Six unconfirmed Quasar candidates in Monograph 08 showed the same generic
CN=defaultsubject as confirmed servers. A certificate subject alone cannot separate a live controller from a recycled VPS address. - 33 listeners, two confirmed. Monograph 15 counted 33 Quasar endpoints on 30 hosts: 2 confirmed, 4 suspected and 27 candidates.
- One to block, one to watch. One confirmed controller on a UK hosting network carried the stock
CN=Quasar Server CAcertificate and a matching TLS fingerprint, and was seen twice. Odin publishes it for blocking. The other sat on a Canadian cable subscriber network on port5000, so it went to a short watchlist instead.
The pattern matches other commodity RATs. Feeds hold far more Quasar addresses than there are live servers, and addresses on consumer lines change hands often.
How to detect Quasar RAT
- Default certificates. Hunt TLS sessions that present
CN=Quasar Server CAon any port. Combine it with a matching TLS fingerprint before blocking. - Odd outbound TLS. A user process that keeps a long TLS session to a raw IP address on a high port is suspicious, whatever the family.
- Persistence keys. New run keys or scheduled tasks pointing to binaries in user-writable folders deserve review.
- Keylogging and credential access. EDR alerts for keyboard hooks or reads of browser credential stores by an unknown binary are classic Quasar behaviors.
- Not port alone. Quasar ports are configurable, so a port list ages fast.
Monograph 15 publishes a Suricata signature for the Quasar default certificate, plus KQL, Sigma and YARA rules for commodity RAT infrastructure. Monograph 08 carries a Suricata rule set for RAT certificate subjects. All are in the Defense Kit. For rule formats, see YARA and Sigma rules.
How to respond to a Quasar RAT infection
- Isolate the host and keep a memory image if you can. The client may hold its configuration in memory.
- Reset credentials used on the machine, starting with browser-saved passwords and VPN or email accounts. Assume keystrokes were captured.
- Remove persistence by checking run keys, scheduled tasks and startup folders, or reimage the machine.
- Hunt for the controller address and certificate across your proxy and firewall logs to find other infected hosts.
- Close the entry point. Find out how the client arrived, for example a phishing attachment or a loader, and fix that path.
Quasar RAT compared with other commodity RATs
| RAT | Origin | Records in Monograph 08 | Confirmed live |
|---|---|---|---|
| Quasar RAT | Open-source C# tool, on GitHub since at least 2014 (MITRE) | 2,938 | 2 |
| AsyncRAT | Open-source tool first published on GitHub (MITRE) | 11,473 | 1 |
| DCRat | Commodity RAT | 1,593 | 1 |
| VenomRAT | Commodity RAT | 1,292 | 2 |
| njRAT | Remote access tool first seen in 2012 (MITRE) | 18 | 0 |
Frequently asked questions about Quasar RAT
What is Quasar RAT?
Quasar RAT is a free, open-source remote administration tool for Windows, written in C# and released under the MIT license. Criminals and several state-linked groups use it as a remote access trojan.
Is Quasar RAT malware?
The code is published as a remote administration tool. When it is installed without the owner's consent, it works as a remote access trojan, which is how criminals and APT groups use it.
Is Quasar RAT legal?
The software is MIT-licensed and legal to publish. Installing it on computers you do not own, or without the owner's permission, is illegal.
Who uses Quasar RAT?
MITRE ATT&CK lists Patchwork, LazyScripter, Gorgon Group, Kimsuky, menuPass (APT10), BackdoorDiplomacy and APT-C-36, plus many criminal operators.
What can Quasar RAT do?
MITRE lists keylogging, webcam viewing, remote desktop, credential theft from browsers and FTP clients, and AES-encrypted command and control.
How do I detect Quasar RAT?
Hunt for TLS sessions presenting the default CN=Quasar Server CA certificate, unknown persistence entries and keylogging alerts. Odin Research publishes Suricata, KQL, Sigma and YARA rules in its Defense Kit.
Quasar RAT vs AsyncRAT: what is the difference?
Both are open-source RATs first published on GitHub. In Odin's data AsyncRAT had about four times as many historical records, 11,473 against 2,938, but both had only one or two live servers.
What is xRAT?
xRAT is a name associated with Quasar. MITRE ATT&CK lists xRAT as an associated name of QuasarRAT (S0262).
Sources
- Quasar project, README, GitHub. raw.githubusercontent.com/quasar/Quasar/master/README.md (checked 21 November 2026)
- MITRE ATT&CK, QuasarRAT (S0262). attack.mitre.org/software/S0262/ (checked 21 November 2026)
- MITRE ATT&CK, menuPass (G0045). attack.mitre.org/groups/G0045/ (checked 21 November 2026)
- MITRE ATT&CK, AsyncRAT (S1087). attack.mitre.org/software/S1087/ (checked 21 November 2026)
- MITRE ATT&CK, njRAT (S0385). attack.mitre.org/software/S0385/ (checked 21 November 2026)
- MITRE ATT&CK, Remote Access Tools (T1219). attack.mitre.org/techniques/T1219/ (checked 21 November 2026)
Related tools and terms
What is XWorm?
XWorm is a commodity .NET remote access trojan sold to criminals. It offers remote control, keylogging and plugin modules.
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.