Simbot

Category: backdoor · Aliases: Simbot, Backdoor:Win32/Simbot, Taidoor, BKDR_SIMBOT, Trojan:Win32/Simbot, Taidoor RAT, Backdoor.Win32.Simbot · Sample count (EMBER 2018): 634 · Enrichment: curated_sourced · Updated: 2026-10-14
Category: BackdoorStatus: Automated SignaturePlatform: WINDOWS_PEStage: Execution, PersistenceFirst seen: 2008Actor: Unknown / CybercriminalIndustry: Global / OpportunisticMotivation: Cyber Espionage🕸 Explore Relationship Graph⚙ API JSON⚡ Sigma Rule💾 YARA RuleOS: Windows 11, Windows 10, Windows Server 2022
Executive Summary
Backdoor:Win32/Simbot (prominently tracked by US-CERT / CISA as the Taidoor RAT, and cataloged across vendor telemetry as BKDR_SIMBOT, Trojan:Win32/Simbot, or Backdoor.Win32.Simbot) is a sophisticated remote access trojan (RAT) and cyber espionage backdoor associated with Chinese state-sponsored advanced persistent threat (APT) actors.

Table of Contents

Overview

Backdoor:Win32/Simbot (prominently tracked by US-CERT / CISA as the Taidoor RAT, and cataloged across vendor telemetry as BKDR_SIMBOT, Trojan:Win32/Simbot, or Backdoor.Win32.Simbot) is a sophisticated remote access trojan (RAT) and cyber espionage backdoor associated with Chinese state-sponsored advanced persistent threat (APT) actors. Featured prominently in CISA Alert AA20-216A (MAR-10292089) and documented jointly by the CISA, FBI, and DoD, Simbot/Taidoor is deployed in targeted spear-phishing campaigns against government agencies, defense contractors, and geopolitical think tanks. Simbot consists of a loader (frequently disguised as a modified svchost.dll) and an encrypted payload that executes solely in memory. It uses custom RC4 and AES stream ciphers and proprietary network handshake headers (such as 'F::') to communicate with C2 servers, allowing adversaries to execute arbitrary shell commands, exfiltrate sensitive files, manipulate processes, and stage lateral movement across enterprise networks.

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: Taidoor Remote Access Trojan Lineage

Known Derivatives & Downstream Variants: Backdoor:Win32/Simbot.Gen · Bkdr_Simbot.A · Taidoor X64 Backdoor

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-EAFEgress Analysis and FilteringIsolateT1041Enforce perimeter TLS inspection and alert on anomalous outbound data volume ratios transmitting over active C2 channels.
D3-PIADProcess Injection Analysis & DetectionDetectT1055Monitor cross-process thread creation (CreateRemoteThread) and asynchronous procedure calls (QueueUserAPC).
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-FSFile Sandboxing (Attachment Detonation)IsolateT1566.001Detonate macro-enabled documents, ISOs, and password-protected archives inside an isolated hypervisor.
D3-NTIEncrypted Traffic AnalysisDetectT1573.001Inspect TLS handshake metadata (JA3/JA4 fingerprints) to identify malicious encrypted C2 sessions.

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_SIMBOT_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Simbot"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "simbot" ascii wide nocase
        $s2 = "simbot" ascii wide nocase
        $s3 = "backdoor:win32/simbot" ascii wide nocase
        $s4 = "taidoor" ascii wide nocase
        $s5 = "bkdr_simbot" ascii wide nocase
        $s6 = "trojan:win32/simbot" ascii wide nocase
        $s7 = "taidoor rat" ascii wide nocase
        $s8 = "backdoor.win32.simbot" 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 - Simbot (Backdoor) Execution & Triage
id: 976a2044-dce4-5569-9e57-9df27dd3ee61
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Simbot 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/simbot
- 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.t1566_001
- attack.t1055
- attack.t1071_001
- attack.t1573_001
- attack.t1059_003
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

Tier 3 Attribution Fingerprint Rule (High Fidelity)

Deep signature matching distinctive operational fingerprints and payload characteristics.

rule MALWARE_WIN_SIMBOT_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Simbot 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 = "simbot" 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. Immediately isolate the compromised host from internal LAN and WAN environments to cut off interactive remote shell sessions established by Simbot.
  2. Inspect active socket listeners and outbound established network connections ('netstat -ano') to identify and sever covert TCP/UDP channels used by Simbot.
  3. Scan Windows Services, Scheduled Tasks, and Startup folders to locate and eliminate persistent backdoor listeners configured by Simbot.
  4. Invalidate all active VPN profiles, local administrator credentials, and session tokens that may have been harvested by the Simbot operator.
  5. Re-image the affected host using a validated golden image prior to reconnecting it to enterprise network segments.

What to Avoid

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

  1. Do not attempt to interact with or send messages through the Simbot remote terminal, as this alerts the attacker and may cause them to execute destructive anti-forensic commands.
  2. Avoid relying solely on static file signatures, as Simbot payloads frequently execute reflectively in memory without writing binaries to disk.

References & External Analysis

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: AA20-216A ↗

Frequently Asked Questions

What is Simbot (Taidoor) malware?

Simbot is a state-sponsored remote access trojan (RAT) also known as Taidoor, utilized by Chinese APT actors for targeted cyber espionage against government and defense targets.

What government advisory details Simbot/Taidoor operations?

CISA Alert AA20-216A (jointly released by CISA, FBI, and the Department of Defense) documents Taidoor technical indicators, C2 handshakes, and remediation strategies.

How does Simbot communicate with command-and-control servers?

Simbot uses custom TCP packet headers (such as initial packets starting with 'F::') and encrypts communications using RC4 and AES stream ciphers to evade intrusion detection.

What capabilities does Simbot provide to remote operators?

Simbot enables arbitrary shell command execution, file upload and download, process creation and termination, screen captures, and network reconnaissance.

How can enterprise networks detect and defend against Simbot?

Enterprises should monitor for suspicious DLL side-loading (svchost.dll), inspect egress traffic for non-standard encrypted handshakes, and enforce EDR endpoint controls.

How do I remove the Simbot Backdoor from Windows?

Manual removal of Simbot 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 Simbot a virus or a Backdoor?

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

What are the main symptoms of a Simbot infection?

Symptoms of Simbot 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 Backdoors

Want to prevent Simbot 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.

Need help with an active incident? Published by the SystemHelpdesk team.

Machine-readable

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