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
Malicious Web Browser Spawning Command or Script Interpreter
Suspicious Python Inline Exec Execution in STARKVEIL Chain
Malicious TELEPUZ ClickFix Stager via Hidden PowerShell Grab Endpoint
Suspicious Hidden PowerShell Retrieving VBScript from mcdir.me by Millenium RAT (via process_creation)
Suspicious Command in RunMRU Registry Indicating ClickFix Execution (via registry_set)
Suspicious Edge Update Setup Spawning PowerShell via ClearFake
Suspicious PowerShell Locating and Running MSBuild Project (via process_creation)
Malicious Excel Macro Spawning Scripting Interpreter Downloader (via process_creation)
Suspicious PowerShell ReadAllBytes and Expand-Archive Payload Staging (via process_creation)
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.