Files
splunk-security_content/detections/endpoint/windows_masquerading_msdtc_process.yml
2024-06-26 14:41:53 +00:00

77 lines
3.3 KiB
YAML

name: Windows Masquerading Msdtc Process
id: 238f3a07-8440-480b-b26f-462f41d9a47c
version: 2
date: '2024-05-19'
author: Teoderick Contreras, Splunk
status: production
type: TTP
data_source:
- Sysmon EventID 1
description: The following analytic identifies the execution of msdtc.exe with specific
command-line parameters (-a or -b), which are indicative of the PlugX malware. This
detection leverages data from Endpoint Detection and Response (EDR) agents, focusing
on process names and command-line arguments. This activity is significant because
PlugX uses these parameters to masquerade its malicious operations within legitimate
processes, making it harder to detect. If confirmed malicious, this behavior could
allow attackers to gain unauthorized access, exfiltrate data, and conduct espionage,
severely compromising the affected system.
search: '| tstats `security_content_summariesonly` min(_time) as firstTime max(_time)
as lastTime from datamodel=Endpoint.Processes where Processes.process_name = "msdtc.exe"
Processes.process = "*msdtc.exe*" Processes.process IN ("* -a*", "* -b*") by Processes.dest
Processes.user Processes.parent_process_name Processes.parent_process Processes.process_name
Processes.original_file_name Processes.process Processes.process_id Processes.parent_process_id
| `drop_dm_object_name(Processes)` | `security_content_ctime(firstTime)` | `security_content_ctime(lastTime)`
| `windows_masquerading_msdtc_process_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: unknown
references:
- https://malpedia.caad.fkie.fraunhofer.de/details/win.plugx
tags:
analytic_story:
- PlugX
asset_type: Endpoint
confidence: 80
impact: 80
message: msdtc.exe process with process commandline used by PlugX malware in $dest$.
mitre_attack_id:
- T1036
observable:
- name: dest
type: Hostname
role:
- Victim
product:
- Splunk Enterprise
- Splunk Enterprise Security
- Splunk Cloud
risk_score: 64
required_fields:
- _time
- Processes.dest
- Processes.user
- Processes.parent_process_name
- Processes.parent_process
- Processes.original_file_name
- Processes.process_name
- Processes.process
- Processes.process_id
- Processes.parent_process_path
- Processes.process_path
- Processes.parent_process_id
security_domain: endpoint
tests:
- name: True Positive Test
attack_data:
- data:
https://media.githubusercontent.com/media/splunk/attack_data/master/datasets/attack_techniques/T1036/msdtc_process_param/msdtc_a_sysmon.log
source: XmlWinEventLog:Microsoft-Windows-Sysmon/Operational
sourcetype: xmlwineventlog