Try in Splunk Security Cloud


This search detects a suspicioous termination of known services killed by ransomware before encrypting files in a compromised machine. This technique is commonly seen in most of ransomware now a days to avoid exception error while accessing the targetted files it wants to encrypts because of the open handle of those services to the targetted file.

  • Type: TTP
  • Product: Splunk Enterprise, Splunk Enterprise Security, Splunk Cloud
  • Datamodel: Endpoint
  • Last Updated: 2021-06-04
  • Author: Teoderick Contreras, Splunk
  • ID: 3070f8e0-c528-11eb-b2a0-acde48001122


ID Technique Tactic
T1490 Inhibit System Recovery Impact
`wineventlog_system` EventCode=7036 Message IN ("*Volume Shadow Copy*","*VSS*", "*backup*", "*sophos*", "*sql*", "*memtas*", "*mepocs*", "*veeam*", "*svc$*") Message="*service entered the stopped state*" 
| stats count min(_time) as firstTime max(_time) as lastTime by EventCode Message dest Type 
| `security_content_ctime(lastTime)` 
| `security_content_ctime(firstTime)` 
| `known_services_killed_by_ransomware_filter`

Associated Analytic Story

How To Implement

To successfully implement this search, you need to be ingesting logs with the 7036 EventCode ScManager in System audit Logs from your endpoints.

Required field

  • _time
  • EventCode
  • Message
  • dest
  • Type

Kill Chain Phase

  • Exploitation

Known False Positives

Admin activities or installing related updates may do a sudden stop to list of services we monitor.


Risk Score Impact Confidence Message
72.0 90 80 Known services $Message$ terminated by a potential ransomware on $dest$


Test Dataset

Replay any dataset to Splunk Enterprise by using our tool or the UI. Alternatively you can replay a dataset into a Splunk Attack Range

source | version: 1