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 or network device. In some cases, these commands may also be used to initiate a shutdown/reboot of a remote computer or network device via Network Device CLI (e.g. reload).[1][2] They may also include shutdown/reboot of a virtual machine via hypervisor / cloud consoles or command line tools.
Shutting down or rebooting systems may disrupt access to computer resources for legitimate users while also impeding incident response/recovery.
Adversaries may also use Windows API functions, such as InitializeSystemShutdownExW or ExitWindowsEx, to force a system to shut down or reboot.[3][4] Alternatively, the NtRaiseHardErroror ZwRaiseHardError Windows API functions with the ResponseOption parameter set to OptionShutdownSystem may deliver a "blue screen of death" (BSOD) to a system.[5][6][7] In order to leverage these API functions, an adversary may need to acquire SeShutdownPrivilege (e.g., via Access Token Manipulation).[4]
In some cases, the system may not be able to boot again.
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.[8][9]
| ID | Name | Description |
|---|---|---|
| S1167 | AcidPour |
AcidPour includes functionality to reboot the victim system following wiping actions, similar to AcidRain.[10] |
| S1125 | AcidRain |
AcidRain reboots the target system once the various wiping processes are complete.[11] |
| S1133 | Apostle |
Apostle reboots the victim machine following wiping and related activity.[12] |
| G0067 | APT37 |
APT37 has used malware that will issue the command |
| G0082 | APT38 |
APT38 has used a custom MBR wiper named BOOTWRECK, which will initiate a system reboot after wiping the victim's MBR.[14] |
| S1053 | AvosLocker |
AvosLocker’s Linux variant has terminated ESXi virtual machines.[15] |
| S1136 | BFG Agonizer |
BFG Agonizer uses elevated privileges to call |
| S1070 | Black Basta |
Black Basta has used |
| S1149 | CHIMNEYSWEEP |
CHIMNEYSWEEP can reboot or shutdown the targeted system or logoff the current user.[17] |
| S1111 | DarkGate |
DarkGate has used the |
| S1033 | DCSrv |
DCSrv has a function to sleep for two hours before rebooting the system.[19] |
| S0697 | HermeticWiper |
HermeticWiper can initiate a system shutdown.[20][21] |
| S0607 | KillDisk |
KillDisk attempts to reboot the machine by terminating specific processes.[22] |
| S1160 | Latrodectus |
Latrodectus has the ability to restart compromised hosts.[23] |
| G0032 | Lazarus Group |
Lazarus Group has rebooted systems after destroying files and wiping the MBR on infected systems.[24] |
| S0372 | LockerGoga |
LockerGoga has been observed shutting down infected systems.[25] |
| S0582 | LookBack | |
| S0449 | Maze |
Maze has issued a shutdown command on a victim machine that, upon reboot, will run the ransomware within a VM.[27] |
| G1051 | Medusa Group |
Medusa Group has manually turned off and encrypted virtual machines.[28] |
| S1135 | MultiLayer Wiper |
MultiLayer Wiper reboots the infected system following wiping and related tasks to prevent system recovery.[4] |
| S0368 | NotPetya |
NotPetya will reboot the system one hour after infection.[8][29] |
| S0365 | Olympic Destroyer |
Olympic Destroyer will shut down the compromised system after it is done modifying system configuration settings.[9][29] |
| S1242 | Qilin |
Qilin can initiate a reboot of the backup server to hinder recovery.[30] |
| S0140 | Shamoon |
Shamoon will reboot the infected system once the wiping functionality has been completed.[31][32] |
| S1178 | ShrinkLocker |
ShrinkLocker can restart the victim system if it encounters an error during execution, and will forcibly shutdown the system following encryption to lock out victim users.[33] |
| S0689 | WhisperGate |
WhisperGate can shutdown a compromised host through execution of |
| S1207 | XLoader |
This type of attack technique cannot be easily mitigated with preventive controls since it is based on the abuse of system features.
| ID | Name | Analytic ID | Analytic Description |
|---|---|---|---|
| DET0559 | Multi-Platform Shutdown or Reboot Detection via Execution and Host Status Events | AN1538 |
Correlate process execution of shutdown/reboot commands (e.g., shutdown.exe, restart-computer) with host status change logs (Event IDs 1074, 6006) and absence of related administrative context (e.g., user not in Helpdesk group). |
| AN1539 |
Detect 'shutdown', 'reboot', or 'systemctl poweroff' executions with auditd/syslog and absence of scheduled maintenance windows or approved user context. |
||
| AN1540 |
Identify use of 'shutdown', 'reboot', or 'osascript' system shutdown invocations within unified logs and track unexpected shutdown sequences initiated by GUI or script. Cross-reference with user activity or absence thereof. |
||
| AN1541 |
Detect commands such as 'esxcli system shutdown' or 'vim-cmd vmsvc/power.shutdown' executed outside of maintenance windows or via unusual users. Reboot logs in hostd.log and shell logs should be correlated. |
||
| AN1542 |
Monitor CLI 'reload' commands issued without scheduled maintenance, and correlate to TACACS+/AAA logs for privilege validation. |