Registry key or value was renamed.
Renaming registry keys as anti-analysis obfuscation. Attackers rename their persistence registry keys to mimic legitimate entries.
Alert: renames in Run keys, Services, or security-relevant locations.
ImageCommandLineParentImageUserHashes | Tactic | Technique |
|---|---|
| Defense Evasion | Modify Registry (T1112) |
Starting points — adapt the log source, projected fields and thresholds for your environment.
Event
| where EventLog == "Microsoft-Windows-Sysmon/Operational" and EventID == 14 // Registry object renamed
// EventData holds: Image, CommandLine, ParentImage, User, Hashes
| project TimeGenerated, Computer, RenderedDescription
| sort by TimeGenerated desc
index=* sourcetype="WinEventLog:Microsoft-Windows-Sysmon/Operational" EventCode=14
| stats count earliest(_time) as first_seen latest(_time) as last_seen by ComputerName
| sort - count `# Registry object renamed — add EventData fields: Image, CommandLine, ParentImage, User`
Registry object renamed. Registry key or value was renamed.
Event 14 is written to the Microsoft-Windows-Sysmon/Operational channel by Microsoft-Windows-Sysmon. Requires Sysmon installed with a config that logs this event (e.g. SwiftOnSecurity / Olaf Hartong).
Event 14 is associated with: Modify Registry (T1112).
Alert: renames in Run keys, Services, or security-relevant locations.