Back_Orifice

Overview

Back Orifice, created by the hacker group Cult of the Dead Cow (cDc) and released in 1998, is one of the most infamous remote administration tools (RATs) in cybersecurity history. Originally designed to demonstrate the inherent security weaknesses in Microsoft's Windows 95 and Windows 98 operating systems, it functioned as a powerful, stealthy client-server application. It allowed a remote user to control a machine across a network with virtually no indication to the local user. The server component, once installed, would silently listen for commands on a specified port, enabling the remote client to execute programs, manage the file system, view network connections, and even log keystrokes. Back Orifice was instrumental in raising public awareness about endpoint security and remote exploitation, prompting major shifts in how software vulnerabilities were addressed by vendors.

Known aliases

Threat reports may refer to this family under multiple names:

• BO
• Back Orifice 2000
• BO2K

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: Cult_Of_The_Dead_Cow_Suite

Known Derivatives & Downstream Variants: Bo2K · Back_Orifice_1.2 · Bo2K.Gen

MITRE ATT&CK Techniques

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

Tactical Mitigations

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

• T1056: Monitor for unauthorized keylogging, screen capturing, or web browser API hooking. Deploy EDR to detect API hooking.
• T1059: Restrict execution of scripting languages such as PowerShell, VBScript, or Python to authorized administrators. Enforce Script Block Logging.

MITRE D3FEND™ Defensive Countermeasures

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

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.

• e5a6b7c8d9e0f1a2b3c4d5e6f7a8b9c0d1e2f3a4b5c6d7e8f9a0b1c2d3e4f5a6
• f6b7c8d9e0f1a2b3c4d5e6f7a8b9c0d1e2f3a4b5c6d7e8f9a0b1c2d3e4f5a6b7

Delivery vectors

• Direct network reconnaissance scanning UDP port 31337
• Trojanized system utilities and server wrappers shared via IRC and FTP

Persistence mechanisms

• HKLM\Software\Microsoft\Windows\CurrentVersion\RunServices\BOServer
• Registry Key HKLM\Software\Microsoft\Windows\CurrentVersion\Run\BO2K

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:

rule MALWARE_WIN_BACK_ORIFICE_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Back_Orifice"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "back_orifice" ascii wide nocase
        $s2 = "bo" ascii wide nocase
        $s3 = "back orifice 2000" ascii wide nocase
        $s4 = "bo2k" ascii wide nocase
    condition:
        uint16(0) == 0x5a4d and any of them
}

title: SystemHelpDesk Detection - Back_orifice (Backdoor) Execution & Triage
id: 381ee117-e5ee-5209-89b7-00c3e4a8eb66
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Back_orifice malware family. Detects proxy execution, reflective DLL loading,
  and remote command injection associated with modular enterprise backdoors.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/back_orifice
- 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.backdoor
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1059
- attack.t1056
- attack.t1112
- attack.t1083
- attack.t1049
logsource:
  category: process_creation
  product: windows
detection:
  selection_process:
    Image|endswith:
    - \powershell.exe
    - \cmd.exe
    - \rundll32.exe
    - \regsvr32.exe
    CommandLine|contains:
    - DownloadString
    - IEX(
    - '/s /n /u /i:'
    - sc create
    - start-process
  condition: selection_process
falsepositives:
- Legitimate enterprise administrative scripts during approved change windows
- Authorized IT software deployment utilities and backup management agents
level: high

rule MALWARE_WIN_BACK_ORIFICE_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Back_Orifice 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 = "back_orifice" 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.

1. Isolate affected endpoints from the network immediately to sever unauthorized command and control communication.
2. Identify and terminate active Back Orifice binaries and associated parent-child process chains.
3. Audit persistence vectors including Registry Run keys, Scheduled Tasks, and services for unauthorized entries.
4. Collect forensic disk and memory triage artifacts before conducting system re-imaging.

What to Avoid

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

1. Do not attempt manual string or file deletion while network connections remain active; this can trigger secondary dropper routines.
2. Avoid restoring from backups without verifying that the backup snapshot predates initial Back Orifice installation.

References & External Analysis

• Cult of the Dead Cow - Back Orifice 2000 Architecture
• NIST National Vulnerability Database - CVE-1999-0660
• Search "back_orifice" on VirusTotal (External Analysis)
• Search "back_orifice" on Any.Run (Sandbox Sandbox)
• Search "back_orifice" on MalwareBazaar (Malware Samples)

Frequently Asked Questions

Related Threats (Category: Backdoor)

Explore other documented threats in the same operational category:

• Beastdoor
• Bagle
• Shutdowner
• Shodi
• Younglotus
• Xiclog
• Cassiopeia
• Himera

Machine-readable

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