Splunk Adds Linux EFI Bootloader Tampering Detections for Bootkit Persistence
Patch & Detection Intelligence · 4 sources · Updated 3mo ago · First seen Jul 8, 2026

Splunk published new endpoint detections for suspicious changes to Linux EFI boot components that could indicate bootkit installation, firmware-level persistence, or tampering with the system boot chain. One analytic flags deletion of .efi files in /boot/efi/EFI/BOOT/, while another monitors processes that modify files in the EFI boot volume using EDR telemetry such as process GUIDs, parent-child relationships, and full command-line logging. Splunk said both behaviors are unusual in normal operations, though legitimate administrator activity, package updates, OS reinstalls, and tools such as grub or shim may generate false positives.
The detections map to MITRE ATT&CK Pre-OS Boot techniques T1542.001 and T1542.003, which cover malicious changes to system firmware and bootkits that execute before the operating system loads. MITRE notes that attackers can persist by overwriting legacy BIOS boot records such as the MBR or VBR, or by creating or modifying files in the EFI System Partition (ESP) on UEFI systems so attacker-controlled code runs during boot. Splunk also linked the bootloader-modification analytic to CVE-2024-7344, underscoring concern that EFI boot artifacts remain a high-value target for stealthy persistence and difficult-to-remediate compromise.


