Safe Mode Boot
- ID
- T1688
- Tactics
- TA0112 Defense Impairment
- Platforms
- Windows
- Data sources
- Process Creation, Windows Registry Key Modification, Windows Registry Key Creation
- Source
- attack.mitre.org
- MITRE last modified
- 12 May 2026
Adversaries may abuse Windows safe mode to disable endpoint defenses. Safe mode starts up the Windows operating system with a limited set of drivers and services. Third-party security software such as endpoint detection and response (EDR) tools may not start after booting Windows in safe mode. There are two versions of safe mode: Safe Mode and Safe Mode with Networking. It is possible to start additional services after a safe mode boot.[2][3]
Adversaries may abuse safe mode to disable endpoint defenses that may not start with a limited boot. Hosts can be forced into safe mode after the next reboot via modifications to Boot Configuration Data (BCD) stores, which are files that manage boot application settings.[4]
Adversaries may also add their malicious applications to the list of minimal services that start in safe mode by modifying relevant Registry values (i.e. Modify Registry). Malicious Component Object Model (COM) objects may also be registered and loaded in safe mode.[1][5][6]
Detection
- DET0116 Detection Strategy for Safe Mode Boot Abuse
Data components: Process Creation, Windows Registry Key Modification, Windows Registry Key Creation
Mitigations (2)
- M1026 Privileged Account Management
Restrict administrator accounts to as few individuals as possible, following least privilege principles, that may be abused to remotely boot a machine in safe mode.[1]
- M1054 Software Configuration
Ensure that endpoint defenses run in safe mode.[1]
Software (7)
- S0496 REvil
- S1053 AvosLocker
- S1070 Black Basta
- S1202 LockBit 3.0
- S1212 RansomHub
- S1242 Qilin
- S1247 Embargo