The following analytic identifies the decompile parameter with the HTML Help application, HH.exe. This is a uncommon command to see ran and behavior. Most recently this was seen in a APT41 campaign where a CHM file was delivered and a script inside used a technique for running an arbitrary command in a CHM file via an ActiveX object. This unpacks an HTML help file to a specified path for launching the next stage.
- Type: TTP
Product: Splunk Behavioral Analytics
- Last Updated: 2022-09-02
- Author: Michael Haag, Splunk
- ID: 11c32b19-05a6-48a8-ab28-18dbd9ec5d50
Kill Chain Phase
- CIS 10
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 $main = from source | eval timestamp = time | eval metadata_uid = metadata.uid | eval process_pid = process.pid | eval process_file = process.file | eval process_file_path = process_file.path | eval process_file_name = lower(process_file.name) | eval process_cmd_line = process.cmd_line | eval actor_user = actor.user | eval actor_user_name = actor_user.name | eval actor_process = actor.process | eval actor_process_pid = actor_process.pid | eval actor_process_file = actor_process.file | eval actor_process_file_path = actor_process_file.path | eval actor_process_file_name = actor_process_file.name | eval device_hostname = device.hostname | where process_cmd_line LIKE "%-decompile%" AND process_file_name="hh.exe" --finding_report--
The SPL above uses the following Macros:
windows_system_binary_proxy_execution_compiled_html_file_decompile_filter is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
List of fields required to use this analytic.
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
False positives should be limited, filter as needed.
Associated Analytic Story
|90.0||100||90||$process_name$ has been identified using decompile against a CHM on $dest_device_id$ under user $dest_user_id$.|
The Risk Score is calculated by the following formula: Risk Score = (Impact * Confidence/100). Initial Confidence and Impact is set by the analytic author.
source | version: 1