>Reg.exe

Used to manipulate the registry

Default Executable Paths

C:\Windows\System32\reg.exe
C:\Windows\SysWOW64\reg.exe

Integrity & Metadata

Category Count: 2 weaponized patterns
Forensics & Triage Insight

Documented in LOLBAS project by Oddvar Moe.

Detection Engineering Notes

Monitor process creation events where FileName is "Reg.exe" or command line references known attack arguments.

Executive Summary & AI Quick Reference

High-Fidelity Telemetry Profile

Reg.exe is a native utility pre-installed on Windows systems. Threat actors and red teams abuse Reg.exe as a Living-off-the-Land Binary (LOLBin) to achieve Defense Evasion, Credential Dump without triggering traditional antivirus file-hash alerts. Legitimate system administrators use it for routine administration, making behavioral command-line telemetry essential for differentiation.

Primary Abused Tactics
Defense Evasion, Credential Dump
Minimum Privilege
User
Key Telemetry Source
Sysmon 1 / 4688
ATT&CK Mapping
T1564.004, T1003.002

Weaponized Parameters & Proof-of-Concepts

Documented attack commands, parameter flags, and privilege prerequisites.

2 documented methods
Filter Purpose:
Defense EvasionPrivileges: User
T1564.004: Technique T1564.004

Export the target Registry key and save it to the specified .REG file within an Alternate data stream.

reg export HKLM\SOFTWARE\Microsoft\Evilreg {PATH_ABSOLUTE}:evilreg.reg
Credential DumpPrivileges: Administrator
T1003.002: Technique T1003.002

Dump registry hives (SAM, SYSTEM, SECURITY) to retrieve password hashes and key material

reg save HKLM\SECURITY {PATH_ABSOLUTE:.1.bak} && reg save HKLM\SYSTEM {PATH_ABSOLUTE:.2.bak} && reg save HKLM\SAM {PATH_ABSOLUTE:.3.bak}

SIEM & EDR Detection Rules

Production telemetry rules configured for Microsoft Defender, Sigma, and Splunk.

Telemetry & SIEM Detection Suite (Reg.exe)

Validated against MITRE T1564.004, T1003.002
Reg.exe Microsoft Defender Querykql
1// Microsoft Defender XDR / Microsoft Sentinel
2// Tactic: Defense Evasion
3DeviceProcessEvents
4| where FileName =~ "Reg.exe"
5| where ProcessCommandLine has_any ("Reg")
6| project
7 Timestamp,
8 DeviceName,
9 AccountName,
10 InitiatingProcessParentFileName,
11 InitiatingProcessFileName,
12 InitiatingProcessCommandLine,
13 FileName,
14 FolderPath,
15 ProcessCommandLine,
16 MD5,
17 SHA256
18| sort by Timestamp desc

Mitigation, Hardening & Prevention

Recommended defensive controls to block or constrain Reg.exe abuse.

Application Whitelisting

Enforce Windows Defender Application Control (WDAC) or AppLocker publisher rules to prevent execution outside approved enterprise administration scripts.

Attack Surface Reduction

Enable ASR rules: Block executable content from email client and webmail and Block Office applications from creating child processes spawning Reg.exe.

Behavioral Alerting

Deploy the KQL, Sigma, and Splunk detection queries below. Alert on anomalous child processes, web requests to unrated external IPs, or encoded payload strings.

Frequently Asked Questions (FAQ) • Reg.exe

Key operational questions and defensive answers about Reg.exe LOLBin tradecraft.

What is Reg.exe and why is it classified as a LOLBin?

Reg.exe is a legitimate, pre-installed or trusted utility on Windows. It is classified as a Living-off-the-Land Binary (LOLBin) because adversaries abuse its built-in functionality to perform malicious operations—such as Defense Evasion, Credential Dump—without dropping custom malware binaries on disk.

How do threat actors abuse Reg.exe in cyber intrusions?

Adversaries leverage Reg.exe to execute stealthy actions while evading signature-based security controls. For example, attackers execute commands like "reg export HKLM\SOFTWARE\Microsoft\Evilreg {PATH_ABSOLUTE}:evilreg.reg" to achieve Defense Evasion, Credential Dump, masquerading behind legitimate system process lineage.

How can SOC analysts detect suspicious Reg.exe activity?

Detection engineers monitor process creation events (Windows Event ID 4688 or Sysmon Event ID 1; Linux auditd EXECVE; macOS Endpoint Security) inspecting anomalous command line arguments, unusual parent-child process relationships (e.g. Office apps or web servers spawning Reg.exe), and unexpected network connections.

What MITRE ATT&CK techniques does Reg.exe map to?

Reg.exe maps to MITRE ATT&CK technique(s): T1564.004, T1003.002. These techniques cover adversary actions across tactics such as Defense Evasion, Execution, Persistence, and Command and Control.

How can organizations mitigate and restrict Reg.exe?

Mitigation strategies include implementing Application Control policies (AppLocker or Windows Defender Application Control - WDAC), enforcing Attack Surface Reduction (ASR) rules, configuring strict privilege separation (disallowing standard users from running sensitive switches), and alerting on execution from non-standard directories.

Sharon Ben Moshe
Curated & Verified by
Sharon Ben Moshe
Cybersecurity Researcher & Detection EngineerCheck Point