Files
splunk-security_content/detections/endpoint/chcp_command_execution.yml
2024-07-17 14:41:50 +02:00

85 lines
3.4 KiB
YAML

name: CHCP Command Execution
id: 21d236ec-eec1-11eb-b23e-acde48001122
version: 2
date: '2024-05-09'
author: Teoderick Contreras, Splunk
status: production
type: TTP
description: The following analytic detects the execution of the chcp.exe application,
which is used to change the active code page of the console. This detection leverages
data from Endpoint Detection and Response (EDR) agents, focusing on process creation
events where chcp.exe is executed by cmd.exe with specific command-line arguments.
This activity is significant because it can indicate the presence of malware, such
as IcedID, which uses this technique to determine the locale region, language, or
country of the compromised host. If confirmed malicious, this could lead to further
system compromise and data exfiltration.
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=chcp.com
Processes.parent_process_name = cmd.exe (Processes.parent_process=*/c* OR Processes.parent_process=*/k*)
by Processes.process_name Processes.process Processes.parent_process_name Processes.parent_process
Processes.process_id Processes.parent_process_id Processes.dest Processes.user |
`drop_dm_object_name(Processes)` | `security_content_ctime(firstTime)` | `security_content_ctime(lastTime)`
| `chcp_command_execution_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: other tools or script may used this to change code page to
UTF-* or others
references:
- https://ss64.com/nt/chcp.html
- https://twitter.com/tccontre18/status/1419941156633329665?s=20
tags:
analytic_story:
- IcedID
- Azorult
- Forest Blizzard
asset_type: Endpoint
confidence: 30
impact: 30
message: parent process $parent_process_name$ spawning chcp process $process_name$
with parent command line $parent_process$
mitre_attack_id:
- T1059
observable:
- name: dest
type: Hostname
role:
- Victim
- name: user
type: User
role:
- Victim
product:
- Splunk Enterprise
- Splunk Enterprise Security
- Splunk Cloud
required_fields:
- _time
- process_name
- process
- parent_process_name
- parent_process
- process_id
- parent_process_id
- dest
- user
risk_score: 9
security_domain: endpoint
tests:
- name: True Positive Test
attack_data:
- data:
https://media.githubusercontent.com/media/splunk/attack_data/master/datasets/malware/icedid/simulated_icedid/windows-sysmon.log
source: XmlWinEventLog:Microsoft-Windows-Sysmon/Operational
sourcetype: xmlwineventlog