Windows RegistrySet: EulaAccepted set for renamed Sysinternals tools

Flags Windows registry writes to \EulaAccepted for Sysinternals-related objects when performed by non-matching executables.

FreeReviewedSigma · High · v1
Product
windows
Category
registry_set
Author
Nasreddine Bencherchali (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2022-08-24
Updated
2026-07-30

ATT&CK techniques

Resource Dev
  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 registry writes where the TargetObject contains specific Sysinternals-related path patterns and ends with \EulaAccepted, indicating the EULA acceptance flag was set. It then excludes events where the setting is performed by the expected Sysinternals executable image names. Attackers may use renamed or proxy binaries to blend in while still setting the same EULA acceptance registry value, so the detection relies on Windows RegistrySet telemetry capturing TargetObject and the writing process Image.

Related detections9 linkedT1588.002 — drag to rearrange
Malicious Viper C2 Installation via f8x One-Liner Setup Script (via process_creation)
Windows Registry Set: Sysinternals EULA Accepted Key for PUA Tool Execution
Windows Registry: Sysinternals Renamed Tool Execution Indicator via EulaAccepted Key
Windows Hacktool Execution via PE Metadata Company Field
Windows Hacktool Execution Flagged by Imphash in Process Creation
Windows: Renamed Sysinternals DebugView Process Execution
Windows Registry: Suspicious Keyboard Layout Preload in User Session
Windows Registry Key Created: Sysinternals EULA Acceptance
Windows: Command-line execution using Sysinternals -accepteula flag
Windows RegistrySet: EulaAccepted set for renamed Sysinternals tools
Pivot detection · T1588.002 · 9 related

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