Backboot
Table of Contents
Overview
Backboot (classified across antivirus vendors under signatures including Trojan:Win32/Backboot, Trojan:Win32/Backboot.A, and VirTool:Win32/Backboot) is a persistent Windows backdoor and low-level system manipulator. Active in multi-stage intrusion campaigns, Backboot is deployed via trojan droppers or secondary exploit stages to establish long-term persistence that survives standard system reboots and security sweeps. It targets Windows boot-time initialization routines and kernel subsystem configurations, creating deceptive system services and hook routines that intercept filesystem read and write operations. Backboot opens reverse TCP/HTTP command channels to remote C2 infrastructure, providing threat actors with interactive shell capabilities, remote file upload and download operations, and process execution capabilities while suppressing operating system security event logging.
Known aliases
Threat reports may refer to this family under multiple names:
MITRE ATT&CK Techniques
Observed techniques used by this family, mapped to our technical analysis hubs and the official MITRE ATT&CK framework:
| Technique | Name | Tactic | Official Spec |
|---|---|---|---|
T1542.003 | Pre-OS Boot: Bootkit | Persistence | ATT&CK ↗ |
T1059.003 | Command and Scripting Interpreter: Windows Command Shell | Execution | ATT&CK ↗ |
T1543.003 | Create or Modify System Process: Windows Service | Persistence | ATT&CK ↗ |
T1562.001 | Impair Defenses: Disable or Modify Tools | Defense Evasion | ATT&CK ↗ |
T1071.001 | Application Layer Protocol: Web Protocols | Command and Control | ATT&CK ↗ |
Tactical Mitigations
Based on the techniques used by this family, consider the following defensive strategies:
- T1059.003: Restrict execution of Windows Command Shell (cmd.exe) and block unauthorized batch scripts.
- T1071.001: Implement web filtering and SSL/TLS inspection to detect malicious command and control (C2) traffic hiding in HTTP/HTTPS.
MITRE D3FEND™ Defensive Countermeasures
Defensive techniques mapped to counter the offensive tradecraft observed in this family (via the MITRE D3FEND matrix):
| D3FEND ID | Countermeasure Name | Tactic | Countered ATT&CK | Defensive Guidance |
|---|---|---|---|---|
D3-PBA | Process Spawn Analysis | Detect | T1059.003 | Inspect command-line arguments and anomalous parent-child relationships spawning from cmd.exe. |
D3-WAF | Web Content Filtering & Inspection | Filter | T1071.001 | Block newly registered domains (NRDs) and inspect HTTP Host and URI headers for known C2 profiles. |
D3-SCM | Windows Service Creation Monitoring | Detect | T1543.003 | Verify service binary image signatures and restrict standard users from creating or modifying service definitions. |
D3-STA | Security Tool Anti-Tamper Enforcement | Harden | T1562.001 | Block unauthorized modification of antivirus registry flags and prevent stopping security agent services. |
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_BACKBOOT_T1_ARTIFACT {
meta:
description = "Tier 1 Primitive Artifact: Raw string matches for Backboot"
tier = "T1 - Primitive Artifact"
confidence = "Low-Medium (Fast Triage)"
author = "SystemHelpdesk Threat Research Desk"
date = "2026-10-14"
strings:
$s1 = "backboot" ascii wide nocase
$s2 = "trojan:win32/backboot" ascii wide nocase
$s3 = "trojan:win32/backboot.a" ascii wide nocase
$s4 = "virtool:win32/backboot" ascii wide nocase
$s5 = "backdoor:win32/backboot" ascii wide nocase
$s6 = "win32/backboot" 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 - Backboot (Trojan) Execution & Triage
id: 985279a0-12f3-541a-96de-fee328e98aba
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
with the Backboot 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/backboot
- 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.t1542_003
- attack.t1059_003
- attack.t1543_003
- attack.t1562_001
- 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_BACKBOOT_T3_ATTRIBUTION {
meta:
description = "Tier 3 Attribution Fingerprint: Heuristic detection for Backboot 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 = "backboot" 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.
- Sever network connections immediately to prevent unauthorized remote command execution.
- Inspect system services using sc.exe or PowerShell to identify rogue services registered in HKLM\SYSTEM\CurrentControlSet\Services.
- Verify boot sector and BCD store integrity using bootrec.exe /fixmbr and bcdedit.
- Terminate malicious service hosts and delete corresponding binary files from System32 or Drivers directories.
- Scan the entire disk with an offline rescue media antimalware scanner to ensure rootkit/bootkit components are purged.
What to Avoid
Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.
- Do not perform standard in-OS remediation without checking offline registry and boot records, as kernel hooks may mask files.
- Do not reboot into standard Windows mode before verifying rogue persistence mechanisms are disabled.
References & External Analysis
- Microsoft Defender Threat Encyclopedia - Trojan:Win32/Backboot
- Trend Micro Threat Encyclopedia - Backdoor.Win32.Backboot
- Kaspersky Threat Intelligence Portal - Trojan.Win32.Backboot
- Search "backboot" on VirusTotal (External Analysis)
- Search "backboot" on Any.Run (Sandbox Sandbox)
- Search "backboot" on MalwareBazaar (Malware Samples)
Frequently Asked Questions
What is Trojan:Win32/Backboot?
Backboot is a persistent Windows backdoor and system manipulator that secures persistent access through low-level startup routines.
How does Backboot establish deep system persistence?
It hooks into Windows boot-time startup sequences and registers deceptive background system services.
What remote capabilities does Backboot provide to attackers?
It provides remote interactive command shell access, file upload/download functionality, and arbitrary process execution.
How does Backboot evade detection by security software?
It suppresses Windows event logging, hooks low-level file APIs, and operates through benign-looking service handles.
How can Backboot be completely remediated?
Boot into Windows Recovery Environment (WinRE) or clean PE media, audit service registry hives, delete unauthorized service binaries, and restore MBR/boot configuration.
How do I remove Backboot from Windows?
Manual removal of Backboot 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.
What are the main symptoms of a Backboot infection?
Symptoms of Backboot 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 Backboot 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.
Machine-readable
Get this profile as JSON: https://malware-families-catalog.systemhelpdesk.com/api/backboot.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.