huntrule

Windows Hacktool Execution Flagged by Imphash in Process Creation

Alerts on Windows process executions where the import hash matches known hacktool binaries, even if renamed.

FreeReviewedSigma · Critical · v2
Product
windows
Category
process_creation
Author
Florian Roth (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2022-03-04
Updated
2026-07-31
AnalysisDetection

ATT&CK techniques

Resource Dev → Cred Access

  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Discovery

  10. Lateral Movement

  11. Collection

  12. C2

  13. Exfiltration

  14. Impact

What it detects

This rule identifies execution of multiple Windows-based hacktools by matching their specific import hashes (imphash) in process creation telemetry, even when the executable names have changed. Attackers rely on consistent binary structure to reuse compiled tools, making imphash a useful way to connect renamed files to known tool families. The detection depends on process creation logs that include the imphash value.

Reporting behind it

Related detections9 linkedT1003 — drag to rearrange
Windows Hacktool Execution via PE Metadata Company Field
Suspicious Credential Dump via lsa.exe Debug Output
Malicious Wdigest Authentication Enabled - Reg via Command (via process_creation)
Malicious Diskshadow Command Abuse to Expose VSS Backup (via process_creation)
Malicious IIS Application Pool Credential Dumping (via process_creation)
Malicious Wdigest Authentication Enabled - Registry (via registry_set)
Malicious Viper C2 Installation via f8x One-Liner Setup Script (via process_creation)
Suspicious Veeam Backup Credential Harvesting via PowerShell (via ps_script)
Suspicious Network Provider Registration for Credential Interception via NPPSpy
Windows Hacktool Execution Flagged by Imphash in Process Creation
Pivot detection · T1003 · 9 related

Changelog

v2
  1. v2
    Candidate ingested via manual entry.2026-07-31
  2. v1
    No changelog recorded for this version.2026-07-30

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.