Skip to main content
Mallory
← Back to News
detection-content-updatepersistence-methodendpoint-security-bypassendpoint-software-vulnerability

Splunk Adds Linux EFI Bootloader Tampering Detections for Bootkit Persistence

Patch & Detection Intelligence · 4 sources · Updated 3mo ago · First seen Jul 8, 2026

Splunk Adds Linux EFI Bootloader Tampering Detections for Bootkit Persistence

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.

Patch this, or something else?See real exploitation activity before you spend the cycle.
Triage this advisory
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

3 events · Sep 1, 2018 – Jul 8, 2026
  1. Jul 8, 20264mo ago

    Splunk updates Linux bootloader modification detection

    Splunk updated and published the "Linux Possible Bootloader Modification" analytic for Linux, which monitors processes modifying files in the EFI boot volume. The analytic is intended to surface unusual EFI boot file changes that may indicate bootkit activity or firmware persistence.

    Detection: Linux Possible Bootloader Modification | Splunk Security Content
  2. Jul 8, 20264mo ago

    Splunk publishes Linux EFI bootloader file deletion detection

    Splunk published the "Linux EFI Bootloader File Deletion" analytic to detect deleted .efi files under /boot/efi/EFI/BOOT/ on Linux. The detection is framed as a way to identify possible bootkit installation, firmware-level persistence, or tampering with the boot process.

    Detection: Linux EFI Bootloader File Deletion | Splunk Security Content
  3. Sep 1, 20188y ago

    MITRE ATT&CK publishes System Firmware persistence sub-technique entry

    MITRE ATT&CK published the T1542.001 System Firmware sub-technique entry covering firmware-level persistence behavior. This reference provides the ATT&CK technique context later used by related detections.

    Pre-OS Boot: System Firmware, Sub-technique T1542.001 - Enterprise | MITRE ATT&CK®
Linked entities

Related entities

Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.

Open in app →

Organizations

1 linked
Splunk
Do you run this?See real exploitation activity behind this advisory so you can triage it against everything else in the queue.
Prioritize This Patch
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.