Detection of Rubeus Kerberos Exploitation Tool
This brief covers detection strategies for the Rubeus hacktool, which is frequently used by attackers to perform Kerberos-based credential theft and lateral movement.
Rubeus is a widely used C# toolset designed for interacting with the Kerberos protocol in Windows environments. It serves as a comprehensive suite for credential harvesting, ticket manipulation, and performing advanced Kerberos-based attacks such as AS-REP Roasting, Kerberoasting, and Silver/Golden ticket creation. Threat actors utilize Rubeus to escalate privileges, dump sensitive account information (such as krbtgt hashes), and maintain persistence through pass-the-ticket (PTT) techniques. Given its common use by various offensive security actors to compromise Active Directory environments, defenders should prioritize monitoring for the specific command-line arguments and script blocks associated with its operations. The tool operates primarily by interacting with the Windows security subsystem via PowerShell or direct process execution, making script block logging and process creation telemetry essential for visibility.
Impact
Successful deployment of Rubeus allows attackers to gain unauthorized access to credentials, bypass multi-factor authentication for service accounts via Kerberoasting, and achieve full domain dominance through Golden Ticket attacks. This poses a critical risk of complete network compromise and large-scale data exfiltration within an Active Directory environment.
Recommendation
Detection engineering teams should focus on PowerShell Script Block Logging as the primary telemetry source to catch Rubeus activity regardless of the obfuscation technique used by the attacker.
- Enable PowerShell Script Block Logging (Event ID 4104) across all domain-joined endpoints to capture the specific execution flags identified in the provided Sigma rule.
- Deploy the provided Sigma rule to your SIEM to monitor for Rubeus-specific command-line arguments.
- Audit high-privilege account usage if Rubeus activity is identified, as the tool is often used by actors who have already gained initial administrative access.
Immediate actions
Enable PowerShell Script Block Logging (Event ID 4104) via GPO.
Threat Hunt
Search for Event ID 4104 logs containing Rubeus command arguments.
Data: PowerShell Script Block logs
Mitigations
Monitor and restrict the execution of unauthorized binaries in user-writable directories.
Credential Access TTPs
Detection coverage 1
HackTool - Rubeus Execution - ScriptBlock
highDetects the execution of the hacktool Rubeus using specific command line flags within PowerShell Script Blocks
Detection queries are available on the platform. Get full rules →