Orcus

Overview

Backdoor:Win32/Orcus is a highly advanced, feature-rich Remote Access Trojan (RAT) that was controversially marketed and sold commercially as a legitimate 'Remote Administration Tool' before its author was prosecuted. It is heavily utilized by cybercriminals for espionage, credential theft, and system disruption.

Understanding Orcus RAT
To the end-user, an Orcus infection is entirely invisible. For incident responders, Orcus is a top-tier threat. Because it was developed and sold commercially (often for around $40), it features a highly polished, modular architecture. Attackers can extend its capabilities using custom plugins written in C# or VB.NET. Its capabilities are vast: a fully interactive remote shell, keylogging, webcam/microphone capture, password extraction from browsers, and even the ability to trigger a devastating Blue Screen of Death (BSOD).

Execution and Evasion Strategies
Orcus is typically delivered via spearphishing (weaponized attachments) or drive-by downloads. Upon execution, the payload establishes deep persistence, frequently modifying the Registry Run keys (`HKCU\Software\Microsoft\Windows\CurrentVersion\Run`) or creating hidden scheduled tasks. Orcus is adept at evasion; it actively attempts to detect virtual machines or sandboxes, terminating execution if analysis tools are found. It communicates with its C2 server using a proprietary, encrypted TCP protocol, often disguised to look like legitimate HTTP or HTTPS traffic. It frequently injects its core DLL into legitimate processes like `explorer.exe` or `svchost.exe`.

Indicators of Compromise & Impact
The impact is total endpoint compromise, massive data exfiltration, and severe privacy violations. EDR platforms will trigger on Orcus's process injection attempts and its aggressive harvesting of browser credential databases. Network logs will show sustained, encrypted TCP connections. Threat hunters should look for the presence of the default Orcus mutexes or its heavily obfuscated configuration files stored in the `%AppData%` directory.

MITRE ATT&CK Techniques

Observed techniques used by this family, mapped to the MITRE ATT&CK framework:

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.
• T1071.001: Implement web filtering and SSL/TLS inspection to detect malicious command and control (C2) traffic hiding in HTTP/HTTPS.
• T1125: Restrict access to local camera or microphone APIs. Utilize endpoint protection that monitors hardware access.

Generated Detections (Boilerplate)

These YARA and Sigma rules are auto-generated based on the family name and aliases. They must be heavily tuned before deployment in a production environment.

YARA Rule

rule MALWARE_WIN_ORCUS {
    meta:
        description = "Detects Orcus (trojan)"
        author = "SystemHelpdesk Boilerplate Generator"
        date = "2026-07-06"
    strings:
        $s1 = "orcus" ascii wide nocase
    condition:
        uint16(0) == 0x5a4d and any of them
}

Sigma Rule

title: Suspicious Orcus Activity
id: 6e6ca74063416138a3fbf03dd2e189a6
status: experimental
description: Detects generic indicators of the orcus malware family.
logsource:
    category: process_creation
    product: windows
detection:
    selection:
        Image|endswith:
            - '\cmd.exe'
            - '\powershell.exe'
        CommandLine|contains:
            - "*orcus*"
    condition: selection
level: medium

Containment & Response Steps

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

1. Immediately sever the endpoint from the network to terminate the active Orcus session, halting data exfiltration and preventing the attacker from triggering a BSOD.
2. Do NOT reboot the machine immediately; capture a forensic memory image to extract the active Orcus configuration and C2 details.
3. Force a global password reset for all accounts accessed by the user, as Orcus aggressively targets saved browser and email credentials.
4. Assume the machine is fully compromised; perform a clean operating system rebuild to ensure complete eradication.

What to Avoid

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

1. Do not leave the machine connected to the network during triage; the attacker has live access and can manually destroy evidence.
2. Avoid relying solely on file deletion; Orcus often runs in memory and will recreate deleted files if the injected process is not killed.

References & External Analysis

• Search "orcus" on VirusTotal (External Analysis)

Frequently Asked Questions

Related Families (Category: trojan)

Explore other malware families in the same category:

• Nukesped
• Premium
• Collector
• Winsecsrv
• Arkeistealer

Machine-readable

Get this profile as JSON: https://jordanricky1604-ship-it.github.io/malware-families-catalog/api/orcus.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.