huntrule

Windows Hacktool Execution via PE Metadata Company Field

Flags execution of Windows binaries with PE Company metadata set to "Cube0x0", even when renamed.

FreeReviewedSigma · High · v2
Product
windows
Category
process_creation
Author
Florian Roth (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2022-04-27
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 process executions where the PE header Company value matches Cube0x0. Attackers commonly embed distinctive metadata in compiled binaries, so renamed files can still be attributed via their PE fields. It relies on Windows process creation telemetry that includes parsed PE metadata such as the Company value.

Reporting behind it

Related detections9 linkedT1003 — drag to rearrange
Windows Hacktool Execution Flagged by Imphash in Process Creation
Malicious NTDS Credential Dump via Ntdsutil IFM Snapshot (via process_creation)
Suspicious Mimilite Credential Dumper Execution Writing KB-Named Output
Malicious InternalMonologue NTLM Downgrade Execution via process_creation
Suspicious Modification of msDS-KeyCredentialLink for Shadow Credential Abuse
Possible OxideHarvest Stealer Execution via Combined Short Flag Set
Suspicious Credential Dump Attempt via Task Manager (via process_creation)
Suspicious Ivanti EPMM Database Dump via mysqldump with .mifpp Credentials (via process_creation)
Suspicious Credential Dump via lsa.exe Debug Output
Windows Hacktool Execution via PE Metadata Company Field
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.