Adversaries may stop or disable services on a system to render those services unavailable to legitimate users. Stopping critical services or processes can inhibit or stop response to an incident or aid in the adversary's overall objectives to cause damage to the environment.[1][2]
Adversaries may accomplish this by disabling individual services of high importance to an organization, such as MSExchangeIS
, which will make Exchange content inaccessible [2]. In some cases, adversaries may stop or disable many or all services to render systems unusable.[1] Services or processes may not allow for modification of their data stores while running. Adversaries may stop services or processes in order to conduct Data Destruction or Data Encrypted for Impact on the data stores of services like Exchange and SQL Server.[3]
ID | Name | Description |
---|---|---|
S0640 | Avaddon |
Avaddon looks for and attempts to stop database processes.[4] |
S0638 | Babuk |
Babuk can stop specific services related to backups.[5][6][7] |
S0611 | Clop |
Clop can kill several processes and services related to backups and security solutions.[8][9] |
S0575 | Conti |
Conti can stop up to 146 Windows services related to security, backup, database, and email solutions through the use of |
S0625 | Cuba |
Cuba has a hardcoded list of services and processes to terminate.[11] |
S0659 | Diavol |
Diavol will terminate services using the Service Control Manager (SCM) API.[12] |
S0605 | EKANS |
EKANS stops database, data backup solution, antivirus, and ICS-related processes.[13][14][15] |
S0697 | HermeticWiper |
HermeticWiper has the ability to stop the Volume Shadow Copy service.[16] |
S0431 | HotCroissant |
HotCroissant has the ability to stop services on the infected host.[17] |
G0119 | Indrik Spider |
Indrik Spider has used PsExec to stop services prior to the execution of ransomware.[18] |
S0604 | Industroyer |
Industroyer’s data wiper module writes zeros into the registry keys in |
S0607 | KillDisk |
KillDisk terminates various processes to get the user to reboot the victim machine.[20] |
G0032 | Lazarus Group |
Lazarus Group has stopped the MSExchangeIS service to render Exchange contents inaccessible to users.[21] |
S0582 | LookBack | |
S0449 | Maze |
Maze has stopped SQL services to ensure it can encrypt any database.[23] |
S0576 | MegaCortex |
MegaCortex can stop and disable services on the system.[24] |
S0688 | Meteor |
Meteor can disconnect all network adapters on a compromised host using |
S0457 | Netwalker |
Netwalker can terminate system processes and services, some of which relate to backup software.[26] |
S0365 | Olympic Destroyer |
Olympic Destroyer uses the API call |
S0556 | Pay2Key |
Pay2Key can stop the MS SQL service at the end of the encryption process to release files locked by the service.[27] |
S0583 | Pysa | |
S0481 | Ragnar Locker |
Ragnar Locker has attempted to stop services associated with business applications and databases to release the lock on files used by these applications so they may be encrypted.[29] |
S0496 | REvil |
REvil has the capability to stop services and kill processes.[30][31] |
S0400 | RobbinHood |
RobbinHood stops 181 Windows services on the system before beginning the encryption process.[32] |
S0446 | Ryuk |
Ryuk has called |
S0533 | SLOTHFULMEDIA |
SLOTHFULMEDIA has the capability to stop processes and services.[34] |
S0366 | WannaCry |
WannaCry attempts to kill processes associated with Exchange, Microsoft SQL Server, and MySQL to make it possible to encrypt their data stores.[35][3] |
G0102 | Wizard Spider |
Wizard Spider has used taskkill.exe and net.exe to stop backup, catalog, cloud, and other services prior to network encryption.[36] |
ID | Mitigation | Description |
---|---|---|
M1030 | Network Segmentation |
Operate intrusion detection, analysis, and response systems on a separate network from the production environment to lessen the chances that an adversary can see and interfere with critical response functions. |
M1022 | Restrict File and Directory Permissions |
Ensure proper process and file permissions are in place to inhibit adversaries from disabling or interfering with critical services. |
M1024 | Restrict Registry Permissions |
Ensure proper registry permissions are in place to inhibit adversaries from disabling or interfering with critical services. |
M1018 | User Account Management |
Limit privileges of user accounts and groups so that only authorized administrators can interact with service changes and service configurations. |
Monitor processes and command-line arguments to see if critical processes are terminated or stop running.
Monitor for edits for modifications to services and startup programs that correspond to services of high importance. Look for changes to services that do not correlate with known software, patch cycles, etc. Windows service information is stored in the Registry at HKLM\SYSTEM\CurrentControlSet\Services
. Systemd service unit files are stored within the /etc/systemd/system, /usr/lib/systemd/system/, and /home/.config/systemd/user/ directories, as well as associated symbolic links.
Alterations to the service binary path or the service startup type changed to disabled may be suspicious.
Remote access tools with built-in features may interact directly with the Windows API to perform these functions outside of typical system utilities. For example, ChangeServiceConfigW
may be used by an adversary to prevent services from starting.[1]