splunk-security_content/docs/_posts/2021-10-01-vbscript_execution_using_wscript_app.md

title, excerpt, categories, last_modified_at, toc, toc_label, tags

title	excerpt	categories	last_modified_at	toc	toc_label	tags
Vbscript Execution Using Wscript App	Visual Basic , Command and Scripting Interpreter	Endpoint	2021-10-01	true		Visual Basic Command and Scripting Interpreter Execution Execution Splunk Enterprise Splunk Enterprise Security Splunk Cloud Endpoint

Try in Splunk Security Cloud{: .btn .btn--success}

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.

• Type: TTP
• Product: Splunk Enterprise, Splunk Enterprise Security, Splunk Cloud
• Datamodel: Endpoint
• Datasource: Splunk Add-on for Sysmon
• Last Updated: 2021-10-01
• Author: Teoderick Contreras, Splunk
• ID: 35159940-228f-11ec-8a49-acde48001122

ATT&CK

ID	Technique	Tactic
T1059.005	Visual Basic	Execution

| T1059 | Command and Scripting Interpreter | Execution |

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`

Macros

The SPL above uses the following Macros:

• security_content_ctime
• security_content_summariesonly

Note that vbscript_execution_using_wscript_app_filter is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.

Required field

• _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

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

Associated Analytic story

• FIN7
• Remcos

Kill Chain Phase

• Exploitation

RBA

Risk Score	Impact	Confidence	Message
49.0	70	70	Process name process_name with commandline process to execute vbsscript

Reference

• https://www.joesandbox.com/analysis/369332/0/html

Test Dataset

Replay any dataset to Splunk Enterprise by using our replay.py tool or the UI. Alternatively you can replay a dataset into a Splunk Attack Range

• https://media.githubusercontent.com/media/splunk/attack_data/master/datasets/attack_techniques/T1059.005/vbs_wscript/sysmon.log

source | version: 1