System Shutdown/Reboot

Adversaries may shutdown/reboot systems to interrupt access to, or aid in the destruction of, those systems. Operating systems may contain commands to initiate a shutdown/reboot of a machine. In some cases, these commands may also be used to initiate a shutdown/reboot of a remote computer.[1] Shutting down or rebooting systems may disrupt access to computer resources for legitimate users.

Adversaries may attempt to shutdown/reboot a system after impacting it in other ways, such as Disk Structure Wipe or Inhibit System Recovery, to hasten the intended effects on system availability.[2][3]

ID: T1529
Tactic: Impact
Platform: Linux, macOS, Windows
Permissions Required: User, Administrator, root, SYSTEM
Data Sources: Windows event logs, Process command-line parameters, Process monitoring
Impact Type: Availability
Version: 1.0

Procedure Examples

Name Description
APT37 APT37 has used malware that will issue the command shutdown /r /t 1 to reboot a system after wiping its MBR. [5]
APT38 APT38 has used a custom MBR wiper named BOOTWRECK, which will initiate a system reboot after wiping the victim's MBR. [6]
Lazarus Group Lazarus Group has rebooted systems after destroying files and wiping the MBR on infected systems. [7]
LockerGoga LockerGoga has been observed shutting down infected systems. [4]
NotPetya NotPetya will reboot the system one hour after infection. [2]
Olympic Destroyer Olympic Destroyer will shut down the compromised system after it is done modifying system configuration settings. [3]


This type of attack technique cannot be easily mitigated with preventive controls since it is based on the abuse of system features.


Use process monitoring to monitor the execution and command line parameters of binaries involved in shutting down or rebooting systems. Windows event logs may also designate activity associated with a shutdown/reboot, ex. Event ID 1074 and 6006.