Windows Hacktool Execution via PE Metadata Company Field

ATT&CK techniques

Resource Dev → Cred Access

Recon
Resource Dev
- T1588.002Tool
Initial Access
Execution
Persistence
Priv Esc
Defense Evasion
Cred Access
- T1003OS Credential Dumping
Discovery
Lateral Movement
Collection
C2
Exfiltration
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 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

Malicious Mimikatz Malicious Security Package (SSP) Exfiltrates Cleartext Passwords in File (via file_event)

Windows Hacktool Execution via PE Metadata Company Field

Pivot detection · T1003 · 9 related

Changelog

v2

v2
Candidate ingested via manual entry.2026-07-31
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.

windows-hacktool-execution-via-pe-company-metadata-cube0x0-37c1333a

title: Windows Hacktool Execution via PE Metadata Company Field
id: f2de78d5-9388-4333-a1a1-f77d9971d5f9
status: test
description: 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.
references:
  - https://github.com/cube0x0
  - https://www.virustotal.com/gui/search/metadata%253ACube0x0/files
  - https://github.com/SigmaHQ/sigma/blob/master/rules/windows/process_creation/proc_creation_win_hktl_execution_via_pe_metadata.yml
author: Florian Roth (Nextron Systems), Huntrule Team
date: 2022-04-27
modified: 2024-01-15
tags:
  - attack.credential-access
  - attack.resource-development
  - attack.t1588.002
  - attack.t1003
logsource:
  category: process_creation
  product: windows
detection:
  selection:
    Company: Cube0x0
  condition: selection
falsepositives:
  - Unlikely
level: high
license: DRL-1.1
related:
  - id: 37c1333a-a0db-48be-b64b-7393b2386e3b
    type: derived

Convert

This rule as a query you can run. Uses no unlock credit.

SplunkSPL