Windows: HackTool - PCHunter Execution

Rule ID

PH_Rule_SIGMA_2330

Default Status

Enabled

Description

Detects suspicious use of PCHunter, a tool like Process Hacker to view and manipulate processes, kernel options and other low level stuff. This rule is adapted from https://github.com/SigmaHQ/sigma/blob/master/rules/windows/process_creation/proc_creation_win_hktl_pchunter.yml

Severity

MITRE ATT&CK® Tactics

Persistence

Persistence consists of techniques that adversaries use to keep access to systems across restarts, changed credentials, and other interruptions that could cut off their access. Techniques used for persistence include any access, action, or configuration changes that let them maintain their foothold on systems, such as replacing or hijacking legitimate code or adding startup code.

https://attack.mitre.org/tactics/TA0003

MITRE ATT&CK® Techniques

No Technique Specified

Impacts

Server

Data Source

Windows Sysmon via FortiSIEM Agent

Detection

Correlation

Remediation Guidance

No remediation guidance specified

Time Window

If the following pattern or patterns match an ingested event within the given time window in seconds, trigger an incident.

300 seconds

Trigger Conditions

If the following defined pattern/s occur within a 300 second time window.

Filter

SubPattern Definitions

SubPattern Name: Filter

This is the named definition of the event query, this is important if multiple subpatterns are defined to distinguish them.

SubPattern Query

This is the query logic that matches incoming events

eventType="Win-Sysmon-1-Create-Process" AND (procName REGEXP "\\PCHunter32\.exe$|\\PCHunter64\.exe$" OR srcFileName="PCHunter.exe" OR description="Epoolsoft Windows Information View Tools" OR hashCode REGEXP ".*IMPHASH=0479F44DF47CFA2EF1CCC4416A538663.*|.*IMPHASH=444D210CEA1FF8112F256A4997EED7FF.*|.*MD5=228DD0C2E6287547E26FFBD973A40F14.*|.*MD5=987B65CD9B9F4E9A1AFD8F8B48CF64A7.*|.*SHA1=3FB89787CB97D902780DA080545584D97FB1C2EB.*|.*SHA1=5F1CBC3D99558307BC1250D084FA968521482025.*|.*SHA256=2B214BDDAAB130C274DE6204AF6DBA5AEEC7433DA99AA950022FA306421A6D32.*|.*SHA256=55F041BF4E78E9BFA6D4EE68BE40E496CE3A1353E1CA4306598589E19802522C.*" OR hashMD5 IN ("228dd0c2e6287547e26ffbd973a40f14","987b65cd9b9f4e9a1afd8f8b48cf64a7") OR hashSHA1 IN ("3fb89787cb97d902780da080545584d97fb1c2eb","5f1cbc3d99558307bc1250d084fa968521482025") OR hashSHA256 IN ("2b214bddaab130c274de6204af6dba5aeec7433da99aa950022fa306421a6d32","55f041bf4e78e9bfa6d4ee68be40e496ce3a1353e1ca4306598589e19802522c") OR hashIMP IN ("0479f44df47cfa2ef1ccc4416a538663","444d210cea1ff8112f256a4997eed7ff"))

Group by Attributes

This defines how matching events are aggregated, only events with the same matching attribute values are grouped into one unique incident ID

description,hashCode,hashIMP,hashMD5,hashSHA1,hashSHA256,hostName,procName,srcFileName

Aggregate Constraint

This is most typically a numerical constraint that defines when the rule should trigger an incident

COUNT(*) >= 1

Incident Attribute Mapping

This section defines which fields in matching raw events should be mapped to the incident attributes in the resulting incident.

The available raw event attributes to map are limited to the group by attributes and the aggregate event constraint fields for each subpattern

description = Filter.description,
hashCode = Filter.hashCode,
hashIMP = Filter.hashIMP,
hashMD5 = Filter.hashMD5,
hashSHA1 = Filter.hashSHA1,
hashSHA256 = Filter.hashSHA256,
hostName = Filter.hostName,
procName = Filter.procName,
srcFileName = Filter.srcFileName

FortiSIEM Rules