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

87 lines
3.5 KiB
YAML

name: Windows AutoIt3 Execution
id: 0ecb40d9-492b-4a57-9f87-515dd742794c
version: 2
date: '2024-05-28'
author: Michael Haag, Splunk
status: production
type: TTP
data_source:
- Sysmon EventID 1
description: The following analytic detects the execution of AutoIt3, a scripting
language often used for automating Windows GUI tasks and general scripting. It identifies
instances where AutoIt3 or its variants are executed by searching for process names
or original file names matching 'autoit3.exe'. This activity is significant because
attackers frequently use AutoIt3 to automate malicious actions, such as executing
malware. If confirmed malicious, this activity could lead to unauthorized code execution,
system compromise, or further propagation of malware within the environment.
search: '| tstats `security_content_summariesonly` count min(_time) as firstTime max(_time)
as lastTime from datamodel=Endpoint.Processes where Processes.process_name IN ("autoit3.exe",
"autoit*.exe") OR Processes.original_file_name IN ("autoit3.exe", "autoit*.exe")
by Processes.dest Processes.user Processes.parent_process_name 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_autoit3_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: False positives may be present if the application is legitimately
used, filter by user or endpoint as needed.
references:
- https://github.com/PaloAltoNetworks/Unit42-timely-threat-intel/blob/main/2023-10-25-IOCs-from-DarkGate-activity.txt
tags:
analytic_story:
- DarkGate Malware
asset_type: Endpoint
atomic_guid: []
confidence: 100
impact: 50
message: Execution of AutoIt3 detected. The source process is $parent_process_name$
and the destination process is $process_name$ on $dest$ by
mitre_attack_id:
- T1059
observable:
- name: parent_process_name
type: Process
role:
- Parent Process
- name: process_name
type: Process
role:
- Child Process
- name: dest
type: Hostname
role:
- Victim
- name: user
type: User
role:
- Other
product:
- Splunk Enterprise
- Splunk Enterprise Security
- Splunk Cloud
risk_score: 50
required_fields:
- Processes.dest
- Processes.user
- Processes.parent_process_name
- Processes.process_name
- Processes.original_file_name
- Processes.process
- Processes.process_id
- 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/T1059/autoit/sysmon.log
source: XmlWinEventLog:Microsoft-Windows-Sysmon/Operational
sourcetype: xmlwineventlog