FortiSIEM Rules

Windows: PUA - Process Hacker Execution

Rule ID


Default Status



Detects the execution of Process Hacker based on binary metadata information (Image, Hash, Imphash, etc). Process Hacker is a tool to view and manipulate processes, kernel options and other low level options. Threat actors regularly abuse it to manipulate system processes. This rule is adapted from







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.

MITRE ATT&CK® Techniques

No Technique Specified



Data Source

Windows Sysmon via FortiSIEM Agent



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.


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 ".*\\ProcessHacker_.*" OR procName REGEXP "\\ProcessHacker\.exe$" OR srcFileName IN ("Process Hacker","ProcessHacker.exe") OR description="Process Hacker" OR product="Process Hacker" OR hashCode REGEXP ".*IMPHASH=04DE0AD9C37EB7BD52043D2ECAC958DF.*|.*IMPHASH=3695333C60DEDECDCAFF1590409AA462.*|.*MD5=68F9B52895F4D34E74112F3129B3B00D.*|.*MD5=B365AF317AE730A67C936F21432B9C71.*|.*SHA1=A0BDFAC3CE1880B32FF9B696458327CE352E3B1D.*|.*SHA1=C5E2018BF7C0F314FED4FD7FE7E69FA2E648359E.*|.*SHA256=BD2C2CF0631D881ED382817AFCCE2B093F4E412FFB170A719E2762F250ABFEA4.*|.*SHA256=D4A0FE56316A2C45B9BA9AC1005363309A3EDC7ACF9E4DF64D326A0FF273E80F.*" OR hashMD5 IN ("68f9b52895f4d34e74112f3129b3b00d","b365af317ae730a67c936f21432b9c71") OR hashSHA1 IN ("a0bdfac3ce1880b32ff9b696458327ce352e3b1d","c5e2018bf7c0f314fed4fd7fe7e69fa2e648359e") OR hashSHA256 IN ("bd2c2cf0631d881ed382817afcce2b093f4e412ffb170a719e2762f250abfea4","d4a0fe56316a2c45b9ba9ac1005363309a3edc7acf9e4df64d326a0ff273e80f") OR hashIMP IN ("04de0ad9c37eb7bd52043d2ecac958df","3695333c60dedecdcaff1590409aa462"))

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


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,
product = Filter.product,
srcFileName = Filter.srcFileName