mirror of
https://github.com/splunk/security_content
synced 2026-06-08 17:32:49 +00:00
Patrick
87 lines
3.5 KiB
YAML
87 lines
3.5 KiB
YAML
name: Vbscript Execution Using Wscript App
|
|
id: 35159940-228f-11ec-8a49-acde48001122
|
|
version: 2
|
|
date: '2024-05-14'
|
|
author: Teoderick Contreras, Splunk
|
|
status: production
|
|
type: TTP
|
|
description: The following analytic detects the execution of VBScript using the wscript.exe
|
|
application. It leverages data from Endpoint Detection and Response (EDR) agents,
|
|
focusing on process and command-line telemetry. This activity is significant because
|
|
wscript.exe is typically not used to execute VBScript, which is usually associated
|
|
with cscript.exe. This deviation can indicate an attempt to evade traditional process
|
|
monitoring and antivirus defenses. If confirmed malicious, this technique could
|
|
allow attackers to execute arbitrary code, potentially leading to system compromise,
|
|
data exfiltration, or further lateral movement within the network.
|
|
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.parent_process_name
|
|
= "wscript.exe" AND Processes.parent_process = "*//e:vbscript*") OR (Processes.process_name
|
|
= "wscript.exe" AND Processes.process = "*//e:vbscript*") by Processes.parent_process_name
|
|
Processes.parent_process Processes.process_name Processes.process_id Processes.process
|
|
Processes.dest Processes.user | `drop_dm_object_name(Processes)` | `security_content_ctime(firstTime)`
|
|
| `security_content_ctime(lastTime)` | `vbscript_execution_using_wscript_app_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://www.joesandbox.com/analysis/369332/0/html
|
|
- https://malpedia.caad.fkie.fraunhofer.de/details/win.asyncrat
|
|
tags:
|
|
analytic_story:
|
|
- FIN7
|
|
- Remcos
|
|
- AsyncRAT
|
|
asset_type: Endpoint
|
|
confidence: 70
|
|
impact: 70
|
|
message: Process name $process_name$ with commandline $process$ to execute vbsscript
|
|
mitre_attack_id:
|
|
- T1059.005
|
|
- T1059
|
|
observable:
|
|
- name: dest
|
|
type: Endpoint
|
|
role:
|
|
- Victim
|
|
- name: user
|
|
type: User
|
|
role:
|
|
- Victim
|
|
product:
|
|
- Splunk Enterprise
|
|
- Splunk Enterprise Security
|
|
- Splunk Cloud
|
|
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
|
|
risk_score: 49
|
|
security_domain: endpoint
|
|
tests:
|
|
- name: True Positive Test
|
|
attack_data:
|
|
- data:
|
|
https://media.githubusercontent.com/media/splunk/attack_data/master/datasets/attack_techniques/T1059.005/vbs_wscript/sysmon.log
|
|
source: XmlWinEventLog:Microsoft-Windows-Sysmon/Operational
|
|
sourcetype: xmlwineventlog
|