Zombierat

Category: trojan · Aliases: ZombieRAT, Backdoor.Win32.ZombieRat, Zombie RAT by The Bo$$, ZombieRat 1.0, Backdoor:Win32/ZombieRat · Sample count (EMBER 2018): 0 · Enrichment: curated_sourced · Updated: 2026-10-14
Category: TrojanStatus: Automated SignatureFirst seen: 2003Motivation: Unauthorized Access🕸 Explore Relationship Graph⚙ API JSON⚡ Sigma Rule💾 YARA RuleOS: Windows 11, Windows 10, Windows 7
Executive Summary
ZombieRAT (also cataloged across antimalware archives as ZombieRat, Backdoor.Win32.ZombieRat, and Zombie RAT by The Bo$$) is an early-to-mid 2000s Remote Access Trojan created in Visual Basic around 2003 by a developer using the handle 'The Bo$$'.

Table of Contents

Overview

ZombieRAT (also cataloged across antimalware archives as ZombieRat, Backdoor.Win32.ZombieRat, and Zombie RAT by The Bo$$) is an early-to-mid 2000s Remote Access Trojan created in Visual Basic around 2003 by a developer using the handle 'The Bo$$'. Operating under a client-server architecture, ZombieRAT allowed unauthorized operators to connect to infected Windows 9x, ME, and 2000 workstations over direct TCP network sockets. Upon initial execution, ZombieRAT copies its executable payload into the Windows System directory, establishes persistence by creating registry entries under the Windows Run key, and listens for inbound connections. The trojan provided operators with a graphical management console offering remote surveillance and control commands, including file system browsing, file transfer, registry tampering, remote process termination, keystroke interception, desktop viewing, and disruptive hardware routines.

Known aliases

Threat reports may refer to this family under multiple names:

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: Visual Basic Rat Frameworks

Known Derivatives & Downstream Variants: Zombierat 1.0 · Zombierat 2.0 · Zombierat Gold

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-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-FDAFile Directory Access AuditingDetectT1083Audit and alert on high-frequency recursive directory queries executed by non-system and unclassified binaries.
D3-SDScreen Capture DetectionDetectT1113Monitor desktop graphics API calls (BitBlt, GetDC) triggered by non-standard background threads.
D3-RPMRegistry Persistence MonitoringDetectT1547.001Audit and restrict write privileges to user and machine-level Registry Run/RunOnce keys using Endpoint Privilege Management.

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_ZOMBIERAT_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Zombierat"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "zombierat" ascii wide nocase
        $s2 = "zombierat" ascii wide nocase
        $s3 = "backdoor.win32.zombierat" ascii wide nocase
        $s4 = "zombie rat by the bo$$" ascii wide nocase
        $s5 = "zombierat 1.0" ascii wide nocase
        $s6 = "backdoor:win32/zombierat" 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 - Zombierat (Trojan) Execution & Triage
id: d3732968-9a8e-59cf-8446-2040c369849c
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Zombierat malware family. Detects suspicious execution from temporary user
  directories with hidden window flags and background transfer utilities.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/zombierat
- https://malware-families-catalog.systemhelpdesk.com/defensive/downloader-dropper-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.trojan
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1059_003
- attack.t1547_001
- attack.t1113
- attack.t1083
- attack.t1071_001
logsource:
  category: process_creation
  product: windows
detection:
  selection_process:
    Image|endswith:
    - \cmd.exe
    - \powershell.exe
    - \cscript.exe
    - \wscript.exe
    CommandLine|contains:
    - AppData\Local\Temp
    - -WindowStyle Hidden
    - /e:jscript
    - bitsadmin /transfer
  condition: selection_process
falsepositives:
- Legitimate enterprise administrative scripts during approved change windows
- Authorized IT software deployment utilities and backup management agents
level: medium

Tier 3 Attribution Fingerprint Rule (High Fidelity)

Deep signature matching distinctive operational fingerprints and payload characteristics.

rule MALWARE_WIN_ZOMBIERAT_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Zombierat 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 = "zombierat" 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. Disconnect the affected host from the local network to sever unauthorized remote administration sessions.
  2. Kill the active ZombieRAT server process using Task Manager or administrative tools.
  3. Remove startup keys under HKCU\Software\Microsoft\Windows\CurrentVersion\Run.
  4. Delete the server binary from the Windows System32 directory.

What to Avoid

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

  1. Do not execute software attachments received from unknown senders or IRC file exchanges.
  2. Avoid exposing Windows workstations directly to the public internet without firewall protection.

References & External Analysis

Frequently Asked Questions

What is the ZombieRAT remote access trojan?

ZombieRAT is an early-2000s Visual Basic remote access trojan that grants unauthorized remote control and surveillance over Windows computers.

Who developed ZombieRAT?

ZombieRAT was developed around 2003 by an author known as 'The Bo$$' and distributed across underground hacking forums.

What remote control actions could ZombieRAT perform?

It allowed file transfers, keystroke monitoring, screen captures, process termination, registry editing, and system reboots.

How does ZombieRAT maintain persistence across reboots?

It writes executable startup references into HKCU and HKLM Software\Microsoft\Windows\CurrentVersion\Run registry keys.

How can systems be defended against ZombieRAT?

Block unexpected listening ports at network firewalls, monitor registry autostart keys, and deploy standard antivirus software.

How do I remove the Zombierat Trojan from Windows?

Manual removal of Zombierat 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 Zombierat a virus or a Trojan?

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

What are the main symptoms of a Zombierat infection?

Symptoms of Zombierat 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 Trojans

Want to prevent Zombierat and similar threats from compromising your organization? Read our comprehensive defensive guide: Banking Trojan 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 Threat Intelligence Team.

Machine-readable

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