Rewriteboota

Category: trojan · Aliases: None known · Sample count (EMBER 2018): 2 · Enrichment: expert-seo · Updated: 2026-06-09
Category: TrojanStatus: Automated SignaturePlatform: WINDOWS_PEStage: Execution, PersistenceActor: Unknown / CybercriminalIndustry: Global / OpportunisticMotivation: Opportunistic🕸 Explore Relationship Graph⚙ API JSON⚡ Sigma Rule💾 YARA RuleOS: Windows 11, Windows 10, Windows 7
Executive Summary
Trojan:Win32/Rewriteboota is a highly destructive trojan classified as a 'Bootkit' or MBR (Master Boot Record) infector.

Table of Contents

Overview

Trojan:Win32/Rewriteboota is a highly destructive trojan classified as a 'Bootkit' or MBR (Master Boot Record) infector. Its primary objective is not necessarily to steal data, but to establish the deepest possible level of persistence or to cause catastrophic denial of service by overwriting the critical boot sectors of the infected hard drive, rendering the operating system unbootable (`T1561.001`).

Understanding Rewriteboota (MBR Infectors)
To an end-user, the impact of Rewriteboota is immediate and catastrophic: upon restarting their computer, instead of Windows loading, they are met with a black screen, a custom ransom message, or a 'No bootable device found' error. For a security responder, a bootkit represents one of the most difficult infections to remediate, as the malware executes before the operating system and its security tools even load.

Execution and Destruction Mechanics
Rewriteboota requires administrative privileges to execute. Once running, it uses low-level disk access APIs (such as `DeviceIoControl`) to bypass the Windows filesystem entirely and write directly to the physical sectors of the hard drive (`T1014`). It targets Sector 0, the Master Boot Record. It may overwrite the MBR with a malicious bootloader that loads the malware into memory before Windows starts (establishing deep persistence), or it may simply overwrite it with garbage data or a ransom note (causing denial of service). This technique completely bypasses traditional file-based antivirus scanning.

Indicators of Compromise & Impact
The primary impact is a completely unbootable system and potential total data loss (if the partition table is also destroyed). Host-based IoCs are difficult to detect while the OS is running, but advanced EDR solutions may flag anomalous processes attempting raw disk access (`\.\PhysicalDrive0`). The most obvious IoC is the failure of the system to boot, or the display of a non-standard message during the POST sequence.

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

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-KMCKernel Memory Integrity CheckingHardenT1014Enable Hypervisor-Protected Code Integrity (HVCI) and UEFI Secure Boot to prevent unsigned kernel driver execution.

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_REWRITEBOOTA_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Rewriteboota"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "rewriteboota" 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 - Rewriteboota (Trojan) Execution & Triage
id: 54786d29-b774-53d5-ac45-9f3b9129c612
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Rewriteboota 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/rewriteboota
- 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.t1561_001
- attack.t1014
- attack.t1542_003
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_REWRITEBOOTA_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Rewriteboota 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 = "rewriteboota" 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. If the system is still running but raw disk access alerts have fired, do NOT reboot the machine. Capture a live memory image and attempt to block the process.
  2. If the system is already unbootable, boot from a clean Windows Installation USB or a WinPE recovery environment.
  3. Use the Windows Recovery Environment command prompt and run `bootrec /fixmbr` and `bootrec /fixboot` to attempt to repair the Master Boot Record.
  4. If the partition table was destroyed, specialized data recovery software (or restoring from a full image backup) will be necessary.

What to Avoid

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

  1. Do not blindly reboot a machine if EDR alerts indicate a potential MBR modification; this will trigger the destructive payload.
  2. Avoid paying a ransom if a message is displayed at boot; MBR lockers are notoriously buggy and paying rarely results in recovery.

References & External Analysis

Frequently Asked Questions

What is Rewriteboota and what threat category does it belong to?

Rewriteboota is classified as a Trojan. Documented across security telemetry, it is engineered to execute unauthorized operations, establish persistent footholds on target endpoints, and facilitate malicious campaigns targeting enterprise and individual environments.

How does Rewriteboota establish persistence and evade defensive controls?

Rewriteboota typically establishes persistence through registry run keys, scheduled tasks, or service installations, while evading signature-based antivirus solutions through code obfuscation, memory injection, or anti-analysis sandbox checks.

What are the essential incident response steps for mitigating a Rewriteboota compromise?

Security teams responding to Rewriteboota should immediately isolate affected endpoints from the network, perform memory triage to capture volatile forensic artifacts, audit registry and startup persistence mechanisms, revoke exposed user credentials, and restore systems from verified, clean backups.

What secondary payloads and staging behaviors are commonly associated with Rewriteboota?

Rewriteboota frequently operates as a loader or dropper designed to establish a foothold before downloading and executing secondary high-impact malware payloads. Depending on the threat actor's objectives, these dropped modules can range from ransomware and banking injects to modular infostealers and remote management backdoors.

How can security operations teams effectively detect and hunt for Rewriteboota across enterprise endpoints?

Defenders should hunt for Rewriteboota by deploying behavioral endpoint detection and response (EDR) rules that monitor suspicious process spawning (such as cmd.exe or powershell.exe spawned from office documents or temporary directories), anomalous outbound network connections from non-browser binaries, and unauthorized modifications to Windows Run keys and scheduled task registries.

How do I remove the Rewriteboota Trojan from Windows?

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

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

What are the main symptoms of a Rewriteboota infection?

Symptoms of Rewriteboota 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 Rewriteboota 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 team.

Machine-readable

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