Service Stop
- ID
- T1489
- Tactics
- TA0040 Impact
- Platforms
- ESXi, IaaS, Linux, macOS, Windows
- Data sources
- Process Creation, Logon Session Metadata, Service Creation, Service Metadata, File Deletion, Process Termination
- Source
- attack.mitre.org
- MITRE last modified
- 12 Sep 2026
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.[2][3]
Adversaries may accomplish this by disabling individual services of high importance to an organization, such as MSExchangeIS, which will make Exchange content inaccessible.[3] In some cases, adversaries may stop or disable many or all services to render systems unusable.[2] 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, or on virtual machines hosted on ESXi infrastructure.[4][5]
Threat actors may also disable or stop service in cloud environments. For example, by leveraging the DisableAPIServiceAccess API in AWS, a threat actor may prevent the service from creating service-linked roles on new accounts in the AWS Organization.[6][7]
Detection
- DET0021 Behavioral Detection for Service Stop across Platforms
Data components: Process Creation, Logon Session Metadata, Service Creation, Service Metadata, File Deletion, Process Termination
Mitigations (5)
- M1018 User Account Management
Limit privileges of user accounts and groups so that only authorized administrators can interact with service changes and service configurations.
- 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.
- 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.
- M1060 Out-of-Band Communications Channel
Develop and enforce security policies that include the use of out-of-band communication channels for critical communications during a security incident.[1]
Groups (7)
- G0032 Lazarus Group
- G0034 Sandworm Team
- G0094 Kimsuky
- G0102 Wizard Spider
- G0119 Indrik Spider
- G1004 LAPSUS$
- G1051 Medusa Group
Software (50)
- S0365 Olympic Destroyer
- S0366 WannaCry
- S0400 RobbinHood
- S0431 HotCroissant
- S0446 Ryuk
- S0449 Maze
- S0457 Netwalker
- S0481 Ragnar Locker
- S0496 REvil
- S0533 SLOTHFULMEDIA
- S0556 Pay2Key
- S0575 Conti
- S0576 MegaCortex
- S0582 LookBack
- S0583 Pysa
- S0604 Industroyer
- S0605 EKANS
- S0607 KillDisk
- S0611 Clop
- S0625 Cuba
- S0638 Babuk
- S0640 Avaddon
- S0659 Diavol
- S0688 Meteor
- S0697 HermeticWiper
- S1053 AvosLocker
- S1058 Prestige
- S1068 BlackCat
- S1073 Royal
- S1096 Cheerscrypt
- S1139 INC Ransomware
- S1150 ROADSWEEP
- S1181 BlackByte 2.0 Ransomware
- S1191 Megazord
- S1194 Akira _v2
- S1199 LockBit 2.0
- S1202 LockBit 3.0
- S1211 Hannotog
- S1212 RansomHub
- S1217 VIRTUALPITA
- S1242 Qilin
- S1244 Medusa Ransomware
- S1245 InvisibleFerret
- S1247 Embargo
- S9013 DRYHOOK
- S9014 PHASEJAM
- S9015 BRICKSTORM
- S9050 Vidar
- S9051 The Gentlemen Ransomware
- S9052 MiniFast
