Try in Splunk Security Cloud

Description

This detection is to identify the common service name created by the CLOP ransomware as part of its persistence and high privilege code execution in the infected machine. Ussually CLOP ransomware use StartServiceCtrlDispatcherW API in creating this service entry.

  • Type: TTP
  • Product: Splunk Enterprise, Splunk Enterprise Security, Splunk Cloud
  • Datamodel: Endpoint
  • Last Updated: 2021-03-17
  • Author: Teoderick Contreras
  • ID: 07e08a12-870c-11eb-b5f9-acde48001122

Annotations

ATT&CK
ID Technique Tactic
T1543 Create or Modify System Process Persistence, Privilege Escalation
Kill Chain Phase
  • Exploitation
NIST
CIS20
CVE
1
2
3
4
5
`wineventlog_system` EventCode=7045 Service_Name IN ("SecurityCenterIBM", "WinCheckDRVs") 
| stats count min(_time) as firstTime max(_time) as lastTime by EventCode Service_File_Name Service_Name Service_Start_Type Service_Type 
| `security_content_ctime(firstTime)` 
| `security_content_ctime(lastTime)` 
| `clop_ransomware_known_service_name_filter`

Macros

The SPL above uses the following Macros:

Note that clop_ransomware_known_service_name_filter is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.

Required field

  • EventCode
  • cmdline
  • _time
  • parent_process_name
  • process_name
  • OriginalFileName
  • process_path

How To Implement

To successfully implement this search, you need to be ingesting logs with the Service name, Service File Name Service Start type, and Service Type from your endpoints.

Known False Positives

unknown

Associated Analytic story

RBA

Risk Score Impact Confidence Message
100.0 100 100 An instance of $parent_process_name$ spawning $process_name$ was identified on endpoint $dest$ executing known Clop Ransomware service names.

Reference

Test Dataset

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

source | version: 1