mirror of
https://github.com/splunk/security_content
synced 2026-06-08 17:32:49 +00:00
Eric
91 lines
4.6 KiB
YAML
91 lines
4.6 KiB
YAML
name: Clop Common Exec Parameter
|
|
id: 5a8a2a72-8322-11eb-9ee9-acde48001122
|
|
version: 10
|
|
date: '2025-05-02'
|
|
author: Teoderick Contreras, Splunk
|
|
status: production
|
|
type: TTP
|
|
description: The following analytic identifies the execution of CLOP ransomware variants
|
|
using specific arguments ("runrun" or "temp.dat") to trigger their malicious activities.
|
|
This detection leverages data from Endpoint Detection and Response (EDR) agents,
|
|
focusing on process names and command-line arguments. Monitoring this activity is
|
|
crucial as it indicates potential ransomware behavior, which can lead to file encryption
|
|
on network shares or local machines. If confirmed malicious, this activity could
|
|
result in significant data loss and operational disruption due to encrypted files,
|
|
highlighting the need for immediate investigation and response.
|
|
data_source:
|
|
- Sysmon EventID 1
|
|
- Windows Event Log Security 4688
|
|
- CrowdStrike ProcessRollup2
|
|
search: '| tstats `security_content_summariesonly` count min(_time) as firstTime max(_time)
|
|
as lastTime from datamodel=Endpoint.Processes where Processes.process_name != "*temp.dat*"
|
|
Processes.process = "*runrun*" OR Processes.process = "*temp.dat*" by Processes.action
|
|
Processes.dest Processes.original_file_name Processes.parent_process Processes.parent_process_exec
|
|
Processes.parent_process_guid Processes.parent_process_id Processes.parent_process_name
|
|
Processes.parent_process_path Processes.process Processes.process_exec Processes.process_guid
|
|
Processes.process_hash Processes.process_id Processes.process_integrity_level Processes.process_name
|
|
Processes.process_path Processes.user Processes.user_id Processes.vendor_product
|
|
| `drop_dm_object_name(Processes)` | `security_content_ctime(firstTime)` | `security_content_ctime(lastTime)`
|
|
| `clop_common_exec_parameter_filter`'
|
|
how_to_implement: The detection is based on data that originates from Endpoint Detection
|
|
and Response (EDR) agents. These agents are designed to provide security-related
|
|
telemetry from the endpoints where the agent is installed. To implement this search,
|
|
you must ingest logs that contain the process GUID, process name, and parent process.
|
|
Additionally, you must ingest complete command-line executions. These logs must
|
|
be processed using the appropriate Splunk Technology Add-ons that are specific to
|
|
the EDR product. The logs must also be mapped to the `Processes` node of the `Endpoint`
|
|
data model. Use the Splunk Common Information Model (CIM) to normalize the field
|
|
names and speed up the data modeling process.
|
|
known_false_positives: Operators can execute third party tools using these parameters.
|
|
references:
|
|
- https://www.mandiant.com/resources/fin11-email-campaigns-precursor-for-ransomware-data-theft
|
|
- https://blog.virustotal.com/2020/11/keep-your-friends-close-keep-ransomware.html
|
|
drilldown_searches:
|
|
- name: View the detection results for - "$user$" and "$dest$"
|
|
search: '%original_detection_search% | search user = "$user$" dest = "$dest$"'
|
|
earliest_offset: $info_min_time$
|
|
latest_offset: $info_max_time$
|
|
- name: View risk events for the last 7 days for - "$user$" and "$dest$"
|
|
search: '| from datamodel Risk.All_Risk | search normalized_risk_object IN ("$user$",
|
|
"$dest$") starthoursago=168 | stats count min(_time) as firstTime max(_time)
|
|
as lastTime values(search_name) as "Search Name" values(risk_message) as "Risk
|
|
Message" values(analyticstories) as "Analytic Stories" values(annotations._all)
|
|
as "Annotations" values(annotations.mitre_attack.mitre_tactic) as "ATT&CK Tactics"
|
|
by normalized_risk_object | `security_content_ctime(firstTime)` | `security_content_ctime(lastTime)`'
|
|
earliest_offset: $info_min_time$
|
|
latest_offset: $info_max_time$
|
|
rba:
|
|
message: An instance of $parent_process_name$ spawning $process_name$ was identified
|
|
on endpoint $dest$ by user $user$ attempting using arguments to execute its main
|
|
code or feature of its code related to Clop ransomware.
|
|
risk_objects:
|
|
- field: user
|
|
type: user
|
|
score: 100
|
|
- field: dest
|
|
type: system
|
|
score: 100
|
|
threat_objects:
|
|
- field: parent_process_name
|
|
type: parent_process_name
|
|
- field: process_name
|
|
type: process_name
|
|
tags:
|
|
analytic_story:
|
|
- Compromised Windows Host
|
|
- Clop Ransomware
|
|
asset_type: Endpoint
|
|
mitre_attack_id:
|
|
- T1204
|
|
product:
|
|
- Splunk Enterprise
|
|
- Splunk Enterprise Security
|
|
- Splunk Cloud
|
|
security_domain: endpoint
|
|
tests:
|
|
- name: True Positive Test
|
|
attack_data:
|
|
- data: https://media.githubusercontent.com/media/splunk/attack_data/master/datasets/malware/clop/clop_b/windows-sysmon.log
|
|
source: XmlWinEventLog:Microsoft-Windows-Sysmon/Operational
|
|
sourcetype: XmlWinEventLog
|