Windows Process Creation: Rubeus HackTool Execution Indicators

Flags Windows process executions of Rubeus.exe when command lines include Kerberos attack-related actions.

FreeReviewedSigma · Critical · v2
Product
windows
Category
process_creation
Author
Florian Roth (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2018-12-19
Updated
2026-07-31

ATT&CK techniques

Defense Evasion → Lateral Movement
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Discovery

  8. Lateral Movement

  9. Collection

  10. C2

  11. Exfiltration

  12. Impact

What it detects

This rule identifies execution of the Rubeus executable by matching process creation telemetry to Rubeus binary characteristics and specific Kerberos-related command-line parameters. Attackers commonly use Rubeus for credential access and ticket manipulation, so spotting these argument patterns helps detect abuse even when the executable name varies. The detection relies on Windows process creation fields such as Image, OriginalFileName, Description, and CommandLine substring matches.

Related detections9 linkedT1003 — drag to rearrange
Rubeus HackTool Execution via PowerShell ScriptBlock Flags (Windows)
Suspicious Modification of msDS-KeyCredentialLink for Shadow Credential Abuse
Windows: Detect KrbRelayUp.exe HackTool Process Execution
Malicious Kerberoasting or AS-REP Roasting via Rubeus
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
Windows HackTool Execution: GoldenDMSA.exe Launch with Directory Manipulation Parameters
Possible Kerberoasting via RC4 Service Ticket Requests
Windows Process Creation: Rubeus HackTool Execution Indicators
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.