Files
splunk-security_content/dev/endpoint/vbscript_execution_using_wscript_app.yml
T
2023-01-20 13:24:15 +01:00

63 lines
2.0 KiB
YAML

name: Vbscript Execution Using Wscript App
id: 35159940-228f-11ec-8a49-acde48001122
version: 1
date: '2021-10-01'
author: Teoderick Contreras, Splunk
status: production
type: TTP
description: This analytic is to detect a suspicious wscript commandline to execute
vbscript. This technique was seen in several malware to execute malicious vbs file
using wscript application. commonly vbs script is associated to cscript process
and this can be a technique to evade process parent child detections or even some
av script emulation system.
data_source:
- Sysmon Event ID 1
search:
selection1:
ParentCommandLine: '*//e:vbscript*'
ParentImage: wscript.exe
selection2:
CommandLine: '*//e:vbscript*'
Image|endswith: wscript.exe
condition: selection1 or selection2
how_to_implement: To successfully implement this search you need to be ingesting information
on process that include the name of the process responsible for the changes from
your endpoints into the `Endpoint` datamodel in the `Processes` node. In addition,
confirm the latest CIM App 4.20 or higher is installed and the latest TA for the
endpoint product.
known_false_positives: unknown
references:
- https://www.joesandbox.com/analysis/369332/0/html
tags:
analytic_story:
- FIN7
- Remcos
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
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