{
  "family": "rewriteboota",
  "sample_count": 2,
  "category": "trojan",
  "description": "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`).<br><br><b>Understanding Rewriteboota (MBR Infectors)</b><br>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.<br><br><b>Execution and Destruction Mechanics</b><br>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.<br><br><b>Indicators of Compromise & Impact</b><br>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.",
  "cta": "Published by the SystemHelpdesk team.",
  "aliases": [],
  "enrichment_level": "expert-seo",
  "faq": [],
  "faq_count": 0,
  "mitre_attack": [
    "T1561.001",
    "T1014",
    "T1542.003"
  ],
  "cisa_advisory": null,
  "last_updated": "2026-06-09",
  "mitre_attack_detail": [
    {
      "id": "T1561.001",
      "name": "Disk Wipe: Disk Content Wipe (Overwriting the Master Boot Record)",
      "tactic": "Impact"
    },
    {
      "id": "T1542.003",
      "name": "Pre-OS Boot: Bootkit (Modifying the boot sequence to load malware before the OS)",
      "tactic": "Persistence"
    },
    {
      "id": "T1014",
      "name": "Rootkit (Bypassing the OS to write directly to physical disk sectors)",
      "tactic": "Defense Evasion"
    }
  ],
  "containment_steps": [
    "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.",
    "If the system is already unbootable, boot from a clean Windows Installation USB or a WinPE recovery environment.",
    "Use the Windows Recovery Environment command prompt and run `bootrec /fixmbr` and `bootrec /fixboot` to attempt to repair the Master Boot Record.",
    "If the partition table was destroyed, specialized data recovery software (or restoring from a full image backup) will be necessary."
  ],
  "what_to_avoid": [
    "Do not blindly reboot a machine if EDR alerts indicate a potential MBR modification; this will trigger the destructive payload.",
    "Avoid paying a ransom if a message is displayed at boot; MBR lockers are notoriously buggy and paying rarely results in recovery."
  ],
  "target_industries": [
    "Global / Opportunistic"
  ],
  "motivation": "Opportunistic",
  "threat_actors": [
    "Unknown / Cybercriminal"
  ],
  "target_geographies": [
    "Global"
  ]
}