Windows Registry: Monitor PendingFileRenameOperations changes from suspicious images

Alerts on registry tampering of PendingFileRenameOperations by processes running from suspicious image paths.

FreeReviewedSigma · Medium · v1
Product
windows
Category
registry_set
Author
frack113 (SigmaHQ), DRL 1.1
Published
2023-01-27
Updated
2026-07-30

ATT&CK techniques

Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule flags updates to the PendingFileRenameOperations registry value under the Session Manager key when the originating Image path matches uncommon, suspicious locations. Attackers can use this mechanism to stage file renames or deletions after reboot while reducing the need for immediate disruption. It relies on Windows registry set telemetry, including TargetObject and the process Image that performed the change, to identify potentially tampering activity.

Related detections9 linkedT1036.003 — drag to rearrange
Renamed Autohotkey Binary
Suspicious Masqueraded Rundll32 with Mismatched Original Filename (via process_creation)
Suspicious Renamed git Binary gcmd.exe Execution (via process_creation)
Renamed Execution of a Renamed Windows System Utility (via process_creation)
Suspicious Renamed Pythonw Interpreter Execution via XWorm Loader (via process_creation)
Suspicious PowerShell Masquerading as Windows Terminal via process_creation
Windows Schtasks Execution with Renamed schtasks.exe Binary
Windows RMM Tool MeshAgent Execution with Renamed MeshServiceName
macOS Process Creation: MeshAgent renamed execution via --meshServiceName
Windows Registry: Monitor PendingFileRenameOperations changes from suspicious images
Pivot detection · T1036.003 · 9 related

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