Cross-source coverage
T1542.003 / ATT&CK
Pre-OS Boot: Bootkit
5 rules across 3 sources.
From MITRE ATT&CK 19.2
Adversaries may use bootkits to persist on systems. A bootkit is a malware variant that modifies the boot sectors of a hard drive, allowing malicious code to execute before a computer's operating system has loaded. Bootkits reside at a layer below the operating system and may make it difficult to perform full remediation unless an organization suspects one was used and can act accordingly.
In BIOS systems, a bootkit may modify the Master Boot Record (MBR) and/or Volume Boot Record (VBR). The MBR is the section of disk that is first loaded after completing hardware initialization by the BIOS. It is the location of the boot loader. An adversary who has raw access to the boot drive may overwrite this area, diverting execution during startup from the normal boot loader to adversary code.
The MBR passes control of the boot process to the VBR. Similar to the case of MBR, an adversary who has raw access to the boot drive may overwrite the VBR to divert execution during startup to adversary code.
In UEFI (Unified Extensible Firmware Interface) systems, a bootkit may instead create or modify files in the EFI system partition (ESP). The ESP is a partition on data storage used by devices containing UEFI that allows the system to boot the OS and other utilities used by the system. An adversary can use the newly created or patched files in the ESP to run malicious kernel code.
- Tactics
- Stealth · Persistence
- Platforms
- Linux · Windows
- Telemetry
-
WinEventLog:Sysmonauditd:SYSCALLlinux:syslog
How MITRE says to detect it DET0150
Detection Strategy for File Creation or Modification of Boot Files
Windows Analytic 0428
Detection of raw access to physical drives, modification of boot records (MBR/VBR), and suspicious file creation or alteration within the EFI System Partition (ESP). Correlates privileged process execution with low-level disk modification and unexpected driver or firmware interactions.
WinEventLog:SysmonEventCode=9WinEventLog:SysmonEventCode=11
Linux Analytic 0429
Detection of suspicious write operations to block devices, modifications of bootloader files (GRUB, initrd, vmlinuz), and unexpected changes within the EFI System Partition. Monitors privileged execution of utilities like dd, grub-install, or efibootmgr that modify boot sectors or loader entries.
auditd:SYSCALLopen, write: Write operations targeting /dev/sda, /dev/nvme0n1, or EFI partition mountslinux:syslogBlock device write errors or unusual bootloader activity
splunk/security_content
3 rules| Detection | Severity | Format |
|---|---|---|
| Linux EFI Bootloader File Deletion | Undefined | SPL |
| Windows EFI Bootloader File Modification | Undefined | SPL |
| Windows WinLogon with Public Network Connection | Undefined | SPL |
SigmaHQ/sigma
1 rule| Detection | Severity | Format |
|---|---|---|
| Potential Ransomware or Unauthorized MBR Tampering Via Bcdedit.EXE | Medium | Sigma |
elastic/detection-rules
1 rule| Detection | Severity | Format |
|---|---|---|
| Initramfs Unpacking via unmkinitramfs | Low | Elastic TOML |