heroui logo

Windows Run Key Self Registration From User Writable Path

Splunk Security Content

View Source
Summary
This analytic detects a binary located in a user-writable directory (C:\Users, C:\ProgramData, or C:\PerfLogs) that registers itself for persistence by writing its own path into the CurrentVersion\Run registry key. It relies on Sysmon EventID 13 (Registry value set) and searches for registry_path patterns under Microsoft\Windows\CurrentVersion\Run. The search narrows to processes whose path resides in user-writable locations and excludes a whitelist of known legitimate software that may register in Run. It then compares the registry_value_data (the Run key value) to the actual process_path to identify potential self-registration. The results are aggregated by destination user, process, and registry details, with timestamps formatted for first and last seen, and are filtered by a post-processing macro designed to reduce false positives. Ties to malicious persistence are reinforced by reference to MITRE ATT&CK technique T1547.001 (Run Keys/Startup Folder). The rule is commonly associated with ClickFix-style installers that drop payloads into user profiles and add themselves to Run for persistence across reboots. If the event is confirmed malicious, remediation includes removing the Run key entry, restricting write access to user-writable directories, and investigating the owning process and drop location. This detection provides a concise alert surface for endpoints that may be persistently compromised through Run-key mechanisms.
Categories
  • Endpoint
  • Windows
Data Sources
  • Windows Registry
  • Process
ATT&CK Techniques
  • T1547
  • T1547.001
Created: 2026-11-16