| ID | Name |
|---|---|
| T1542.001 | System Firmware |
| T1542.002 | Component Firmware |
| T1542.003 | Bootkit |
| T1542.004 | ROMMONkit |
| T1542.005 | TFTP Boot |
Adversaries may use bootkits to persist on systems. 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.
A bootkit is a malware variant that modifies the boot sectors of a hard drive, including the Master Boot Record (MBR) and Volume Boot Record (VBR). [1] 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. [2]
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.
| ID | Name | Description |
|---|---|---|
| G0007 | APT28 |
APT28 has deployed a bootkit along with Downdelph to ensure its persistence on the victim. The bootkit shares code with some variants of BlackEnergy.[3] |
| G0096 | APT41 |
APT41 deployed Master Boot Record bootkits on Windows systems to hide their malware and maintain persistence on victim systems.[4] |
| S0114 | BOOTRASH |
BOOTRASH is a Volume Boot Record (VBR) bootkit that uses the VBR to maintain persistence.[1][5][6] |
| S0484 | Carberp |
Carberp has installed a bootkit on the system to maintain persistence.[7] |
| S0182 | FinFisher | |
| G0032 | Lazarus Group |
Lazarus Group malware WhiskeyAlfa-Three modifies sector 0 of the Master Boot Record (MBR) to ensure that the malware will persist even if a victim machine shuts down.[10][11] |
| S0112 | ROCKBOOT |
ROCKBOOT is a Master Boot Record (MBR) bootkit that uses the MBR to establish persistence.[5] |
| S0266 | TrickBot |
TrickBot can implant malicious code into a compromised device's firmware.[12] |
| ID | Mitigation | Description |
|---|---|---|
| M1046 | Boot Integrity |
Use Trusted Platform Module technology and a secure or trusted boot process to prevent system integrity from being compromised. [13] [14] |
| M1026 | Privileged Account Management |
Ensure proper permissions are in place to help prevent adversary access to privileged accounts necessary to install a bootkit. |
| ID | Data Source | Data Component |
|---|---|---|
| DS0016 | Drive | Drive Modification |
Perform integrity checking on MBR and VBR. Take snapshots of MBR and VBR and compare against known good samples. Report changes to MBR and VBR as they occur for indicators of suspicious activity and further analysis.