Suspicious Script Interpreter Command Recorded in Explorer RunMRU History (via registry_set)

PremiumReviewedSigma · Medium · v1
Product
windows
Category
registry_set
Author
HuntRule
Published
2026-05-26
Updated
2026-08-28

ATT&CK techniques

Execution
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Persistence

  5. Priv Esc

  6. Defense Evasion

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule detects the Windows Run dialog history under the Explorer RunMRU registry key recording a script-interpreter command such as mshta, powershell, or curl, the residual artifact left when a victim pastes a ClickFix command during this Booking.com themed phishing campaign. Adversaries drive users to run attacker-supplied commands via the Run dialog, so an interpreter invocation captured in RunMRU is a reliable sign of ClickFix-style execution.

Related detections9 linkedT1059.001 — drag to rearrange
Suspicious PowerShell Launched by MSIX StartingScriptWrapper From WindowsApps via Process Creation (via process_creation)
Suspicious PowerShell Remote TXT Payload Download Spawned by Shortcut via LNK (via process_creation)
Suspicious Script Interpreter Spawned by OneNote via Embedded Attachment (via process_creation)
Suspicious ClickFix Command Execution via RunMRU Registry Key
Suspicious PowerShell Download Spawned From Explorer via ClickFix (via process_creation)
Suspicious Lampion ClickFix PowerShell Download and Execute via Run Dialog
Suspicious cmd.exe Launching Encoded PowerShell From Shortcut File
Suspicious Encoded PowerShell Spawned from Explorer via ClickFix
Malicious Office Application Spawning Command Interpreter
Suspicious Script Interpreter Command Recorded in Explorer RunMRU History (via registry_set)
Pivot detection · T1059.001 · 9 related

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