CyberKit

Event IDs

Sysmon event 14

RegistryEvent (Key and Value Rename)

Channel: Microsoft-Windows-Sysmon/Operational. Category: Registry.

What it records

Logs registry key and value rename operations, recording the new name of the renamed key or value.

Why it matters

Renaming keys/values is sometimes used to relocate or obscure persistence entries, so tracking it closes a gap that create/delete/value-set monitoring alone can miss.

What triggers it

Uncommon in normal operation; occasional software migrations rename keys, while malware may rename registry entries to evade name-based detection rules.

Fields that carry the answer

Key fields
FieldWhat it tells you
ImageThe process that performed the rename, which identifies what relocated or renamed the key or value.
TargetObjectThe original path of the key or value before the rename, which anchors what was moved.
NewNameThe new name given to the key or value. Compare against TargetObject to see if a persistence entry was deliberately relabeled to look benign or evade name-based detections.

In practice

A dropped loader running as C:\Users\jdoe\AppData\Local\Temp\svc32.exe renames its own persistence entry from TargetObject HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run\Setup to NewName WindowsUpdateHelper, relabeling a suspicious-looking value to something that blends in with legitimate Windows naming, which an analyst spots by comparing the rename timing against the original Event 13 SetValue for the same key.

Sample record

Registry object renamed:
RuleName: technique_id=T1112,technique_name=Modify Registry
EventType: RenameKey
UtcTime: 2024-01-15 14:47:40.901
ProcessGuid: {A1B2C3D4-E5F6-4A5B-8C9D-0E1F2A3B0007}
ProcessId: 2200
Image: C:\Windows\System32\reg.exe
TargetObject: HKU\S-1-5-21-1111111111-2222222222-3333333333-1001\Software\Microsoft\Windows\CurrentVersion\Run\Updater
NewName: HKU\S-1-5-21-1111111111-2222222222-3333333333-1001\Software\Microsoft\Windows\CurrentVersion\Run\WindowsUpdateHelper
User: CORP\jsmith

ATT&CK techniques

Sources

Paste a record into Event XML or open a log in EVTX Reader.