Registry Run Keys
Also called Run/RunOnce keys, ASEP.
Registry locations that auto-launch programs at logon or boot.
What it is
Registry values under keys such as Run, RunOnce, and related auto-start extensibility points that cause specified programs to execute automatically when Windows boots or a user logs on.
Where it lives
HKLM/HKCU\Software\Microsoft\Windows\CurrentVersion\Run and \RunOnce
Why it matters
They are among the most common persistence mechanisms, so reviewing run keys across the SOFTWARE and NTUSER hives quickly surfaces malware set to relaunch after reboot, and the entry's path and value name often identify the implant.
In practice
A Run value pointing at a renamed binary in the user's AppData folder revealed how the backdoor survived every reboot.
What to look for
- Entries under Run and RunOnce pointing at user folders.
- Values with encoded commands or script hosts.
- New entries that appear right after an intrusion.
Common mistake
Checking only HKLM. Per-user Run keys in NTUSER.DAT are just as common.
Use it in CyberKit
In the field
Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.
-
CrowdStrike Falcon Commercial
An EDR agent that records process, file and network activity on each host and flags this kind of behavior.
-
Microsoft Defender for Endpoint Commercial
Microsoft's EDR, with advanced hunting tables you can query for this activity across Windows, macOS and Linux.
-
Velociraptor Open source
Collects and hunts for artifacts across many hosts at once, often during live response. Our notes.
-
Sysmon Free
Free Windows logging of process starts, network connections and more, which many detections rely on. Our notes.
Read next
- Registry Hives: On-disk files backing the Windows registry, each holding distinct forensic value.
- Scheduled-Task Artifacts: On-disk task definitions and registry entries used for execution and persistence.
- AmCache: Registry hive recording executed/installed programs with hashes and timestamps.