Detection: Jscript Execution Using Cscript App

Description

The following analytic detects the execution of JScript using the cscript.exe process. It leverages data from Endpoint Detection and Response (EDR) agents, focusing on process and command-line telemetry. This behavior is significant because JScript files are typically executed by wscript.exe, making cscript.exe execution unusual and potentially indicative of malicious activity, such as the FIN7 group's tactics. If confirmed malicious, this activity could allow attackers to execute arbitrary scripts, leading to code execution, data exfiltration, or further system compromise.

Search

 1
 2| tstats `security_content_summariesonly`
 3  count min(_time) as firstTime
 4        max(_time) as lastTime
 5
 6FROM datamodel=Endpoint.Processes WHERE
 7(
 8    (
 9        Processes.parent_process_name = "cscript.exe"
10        Processes.parent_process = "*//e:jscript*"
11    )
12    OR
13    (
14        Processes.process_name = "cscript.exe"
15        Processes.process = "*//e:jscript*"
16    )
17)
18
19NOT Processes.process="*/Job:AgentHIScript*"
20NOT Processes.parent_process="*/Job:AgentHIScript*"
21
22BY Processes.action Processes.dest Processes.original_file_name
23   Processes.parent_process Processes.parent_process_exec Processes.parent_process_guid
24   Processes.parent_process_id Processes.parent_process_name Processes.parent_process_path
25   Processes.process Processes.process_exec Processes.process_guid
26   Processes.process_hash Processes.process_id Processes.process_integrity_level
27   Processes.process_name Processes.process_path Processes.user
28   Processes.user_id Processes.vendor_product
29
30
31| `drop_dm_object_name(Processes)`
32
33| `security_content_ctime(firstTime)`
34
35| `security_content_ctime(lastTime)`
36
37| `jscript_execution_using_cscript_app_filter`

Data Source

Name	Platform	Sourcetype	Source
Sysmon EventID 1	Windows	'XmlWinEventLog'	'XmlWinEventLog:Microsoft-Windows-Sysmon/Operational'
CrowdStrike ProcessRollup2	Other	'crowdstrike:events:sensor'	'crowdstrike'

Macros Used

Annotations

Default Configuration

This detection is configured by default in Splunk Enterprise Security to run with the following settings:

Implementation

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

Symantec Host Integrity check uses Jscript through cscript.exe

Associated Analytic Story

• FIN7

• Remcos

Intermediate Findings

Threat Objects

References

• https://nasbench.medium.com/symantec-endpoint-protection-meets-com-using-symantec-sshelper-as-a-lolbin-40d515a121ce

• https://www.mandiant.com/resources/fin7-pursuing-an-enigmatic-and-evasive-global-criminal-operation

• https://attack.mitre.org/groups/G0046/

Detection Testing

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

Source: GitHub |

Version: 14