Try in Splunk Security Cloud

Description

The following analytic identifies hh.exe (HTML Help) execution of a Compiled HTML Help (CHM) file using InfoTech Storage Handlers. This particular technique will load Windows script code from a compiled help file, using InfoTech Storage Handlers. itss.dll will load upon execution. Three InfoTech Storage handlers are supported - ms-its, its, mk:@MSITStore. ITSS may be used to launch a specific html/htm file from within a CHM file. CHM files may contain nearly any file type embedded. Upon a successful execution, the following script engines may be used for execution - JScript, VBScript, VBScript.Encode, JScript.Encode, JScript.Compact. Analyst may identify vbscript.dll or jscript.dll loading into hh.exe upon execution. The "htm" and "html" file extensions were the only extensions observed to be supported for the execution of Shortcut commands or WSH script code. During investigation, identify script content origination. hh.exe is natively found in C:\Windows\system32 and C:\Windows\syswow64.

  • Type: TTP

  • Product: Splunk Behavioral Analytics

  • Last Updated: 2022-09-02
  • Author: Michael Haag, Splunk
  • ID: ba0c2450-caea-4086-ac3a-a71e2659754b

Annotations

ATT&CK

ATT&CK

ID Technique Tactic
T1218.001 Compiled HTML File Defense Evasion
T1218 System Binary Proxy Execution Defense Evasion
Kill Chain Phase
  • Exploitation
NIST
  • DE.CM
CIS20
  • CIS 10
CVE 


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22



 
| from read_ba_enriched_events() 
| eval timestamp = ucast(map_get(input_event,"time"),"long", null) 
| eval metadata = ucast(map_get(input_event, "metadata"),"map<string, any>", null) 
| eval metadata_uid = ucast(map_get(metadata, "uid"),"string", null) 
| eval process=ucast(map_get(input_event,"process"), "map<string, any>", null) 
| eval process_pid=ucast(map_get(process,"pid"), "string", null) 
| eval process_file=ucast(map_get(process,"file"), "map<string, any>", null) 
| eval process_file_path=ucast(map_get(process_file,"path"), "string", null) 
| eval process_file_name=ucast(map_get(process_file,"name"), "string", null) 
| eval process_cmd_line=ucast(map_get(process,"cmd_line"), "string", null) 
| eval actor=ucast(map_get(input_event,"actor"), "map<string, any>", null) 
| eval actor_user=ucast(map_get(actor,"user"), "map<string, any>", null) 
| eval actor_user_name=ucast(map_get(actor_user,"name"), "string", null) 
| eval actor_process=ucast(map_get(actor,"process"), "map<string, any>", null) 
| eval actor_process_pid=ucast(map_get(actor_process,"pid"), "string", null) 
| eval actor_process_file=ucast(map_get(actor_process,"file"), "map<string, any>", null) 
| eval actor_process_file_path=ucast(map_get(actor_process_file,"path"), "string", null) 
| eval actor_process_file_name=ucast(map_get(actor_process_file,"name"), "string", null) 
| eval device=ucast(map_get(input_event,"device"), "map<string, any>", null) 
| eval device_hostname=ucast(map_get(device,"hostname"), "string", null) 
| where (like(process_cmd_line, "%mk:@MSITStore:%") OR like(process_cmd_line, "%its:%")) AND process_file_name="hh.exe" --finding_report--

Macros

The SPL above uses the following Macros:

:information_source: windows_system_binary_proxy_execution_compiled_html_file_using_infotech_storage_handlers_filter is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.

Required fields

List of fields required to use this analytic.

  • process.pid
  • process.file.path
  • process.file.name
  • process.cmd_line
  • actor.user.name
  • actor.process.pid
  • actor.process.file.path
  • actor.process.file.name
  • device.hostname

How To Implement

To successfully implement this search, you need to be ingesting logs with the process name, parent process, and command-line executions from your endpoints. If you are using Sysmon, you must have at least version 6.0.4 of the Sysmon TA.

Known False Positives

It is rare to see instances of InfoTech Storage Handlers being used, but it does happen in some legitimate instances. Filter as needed.

Associated Analytic Story

RBA

Risk Score Impact Confidence Message
72.0 80 90 $process_name$ has been identified using Infotech Storage Handlers to load a specific file within a CHM on $dest_device_id$ under user $dest_user_id$.

:information_source: The Risk Score is calculated by the following formula: Risk Score = (Impact * Confidence/100). Initial Confidence and Impact is set by the analytic author.

Reference

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

source | version: 1