Files
splunk-security_content/docs/_posts/2022-04-07-detect_html_help_renamed.md
2022-07-19 21:35:47 +00:00

6.1 KiB
Raw Permalink Blame History

title, excerpt, categories, last_modified_at, toc, toc_label, tags
title excerpt categories last_modified_at toc toc_label tags
Detect HTML Help Renamed System Binary Proxy Execution , Compiled HTML File
Endpoint
2022-04-07 true
System Binary Proxy Execution
Compiled HTML File
Defense Evasion
Defense Evasion
Splunk Enterprise
Splunk Enterprise Security
Splunk Cloud
Endpoint

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

Description

The following analytic identifies a renamed instance of hh.exe (HTML Help) executing a Compiled HTML Help (CHM). This particular technique will load Windows script code from a compiled help file. CHM files may contain nearly any file type embedded, but only execute html/htm. 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. Validate it is the legitimate version of hh.exe by reviewing the PE metadata. hh.exe is natively found in C:\Windows\system32 and C:\Windows\syswow64.

  • Type: Hunting
  • Product: Splunk Enterprise, Splunk Enterprise Security, Splunk Cloud
  • Datamodel: Endpoint
  • Last Updated: 2022-04-07
  • Author: Michael Haag, Splunk
  • ID: 62fed254-513b-460e-953d-79771493a9f3

Annotations

ATT&CK
ID Technique Tactic
T1218 System Binary Proxy Execution Defense Evasion

| T1218.001 | Compiled HTML File | Defense Evasion |

Kill Chain Phase
  • Actions on Objectives
NIST
  • PR.PT
  • DE.CM
CIS20
  • CIS 8
CVE

| tstats `security_content_summariesonly` count min(_time) as firstTime max(_time) as lastTime from datamodel=Endpoint.Processes where Processes.process_name!=hh.exe AND Processes.original_file_name=HH.EXE by Processes.dest Processes.user Processes.parent_process_name Processes.original_file_name Processes.process_name Processes.process Processes.process_id Processes.parent_process_id 
| `drop_dm_object_name(Processes)` 
| `security_content_ctime(firstTime)` 
| `security_content_ctime(lastTime)` 
| `detect_html_help_renamed_filter`

Macros

The SPL above uses the following Macros:

detect_html_help_renamed_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

Although unlikely a renamed instance of hh.exe will be used legitimately, filter as needed.

Associated Analytic story

RBA

Risk Score Impact Confidence Message
80.0 80 100 The following process_name has been identified as renamed, spawning from parent_process_name.

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: 4