Identifier / Programs / Windows
reg.exe
Performs operations on registry subkey information and values in registry entries. Windows commands reference
LOLBAS ADS, Credentials 54 Sigma rules name it 25 ATT&CK techniques 2 documented commands 12 known copies with hashes
How reg.exe is abused
ADS T1564.004 Hide Artifacts: NTFS File Attributes
export
Credentials T1003.002 OS Credential Dumping: Security Account Manager
save
Each abuse is LOLBAS's category and the options and words it uses; the full write-up is on LOLBAS's page for reg.exe.
2 documented commands
ADS T1564.004 Hide Artifacts: NTFS File Attributes User privileges
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.regIdentifyTrips no Sigma process-creation rule.
Credentials T1003.002 OS Credential Dumping: Security Account Manager Administrator privileges
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}IdentifyTrips 1 Sigma rule: highDumping of Sensitive Hives Via Reg.EXE by Teymur Kheirkhabarov, Endgame, JHasenbusch, Daniil Yugoslavskiy, oscd.community, frack113
1 of the 2 commands the identifier reads trips a Sigma process-creation rule; 1 trips none. These commands and their descriptions are from LOLBAS’s entry for reg.exe, by Oddvar Moe, at commit 2056cb766250 of 2026-09-26, under the GPL-3.0 and LOLBAS’s notice, with no warranty. Changed: Markdown is shown formatted. The source is in lolbas-gtfobins-commands.json.gz, and the full entry is on LOLBAS’s page for reg.exe. The identifier reads each with LOLBAS’s placeholders filled in: a URL as https://example.com/file, a share as \\192.0.2.10\share\file, a path as C:\Data\file and a command as calc.exe.
What detects it
And 24 more rules that name reg.exe.
Is it the real reg.exe?
C:\Windows\system32\C:\Windows\SysWOW64\12 known copies
10.0.22000.1 (WinBuild.160101.0800) · C:\WINDOWS\SysWOW64\reg.exe · signed by Microsoft Windows
1b3853a8bceaad1329463d42b2151a39eef8e008d27a8e7f05783fa80e66699410.0.22000.1 (WinBuild.160101.0800) · C:\WINDOWS\system32\reg.exe · signed by Microsoft Windows
73bfda07389c54c24805639a814009a4f295fed70b6a46b63f630ed7df564bb410.0.19041.1 (WinBuild.160101.0800) · C:\Windows\SysWOW64\reg.exe · signed by Microsoft Windows
224a746aee2957c3fca376f4457cfc044c1ec99e75756195b27cab396174e2db10.0.19041.1 (WinBuild.160101.0800) · C:\Windows\system32\reg.exe · signed by Microsoft Windows
c0e25b1f9b22de445298c1e96ddfcead265ca030fa6626f61a4a4786cc4a3b7d10.0.18362.1 (WinBuild.160101.0800) · C:\WINDOWS\SysWOW64\reg.exe · signed by Microsoft Windows
45eff48450c110b8a6d2a4c0fe31323423851298f6dadf32d73df91df7ecb79710.0.18362.1 (WinBuild.160101.0800) · C:\WINDOWS\system32\reg.exe · signed by Microsoft Windows
4ed2a27860fa154415f65452ff1f94bd6af762982e2f3470030c504dc3c8a35410.0.17763.1 (WinBuild.160101.0800) · C:\Windows\system32\reg.exe · signed by Microsoft Windows
19316d4266d0b776d9b2a05d5903d8cbc8f0ea1520e9c2a7e6d5960b6fa4dcaf10.0.17763.1 (WinBuild.160101.0800) · C:\Windows\SysWOW64\reg.exe · signed by Microsoft Windows
e3046d83040d114af09c6b7738f69b14ec180ece999573489a7d3386e4ababb510.0.14393.0 (rs1_release.160715-1616) · C:\Windows\system32\reg.exe · signed by Microsoft Windows
9e28034ce3aeea6951f790f8997df44cfbf80beff9fb17413dba317016a716ad10.0.14393.0 (rs1_release.160715-1616) · C:\Windows\SysWOW64\reg.exe · signed by Microsoft Windows
cbb9f8d012cb0af2ca87ac74abb5c77a7743c64697c8d92104d3eba27a699ab06.3.9600.16384 (winblue_rtm.130821-1623) · C:\windows\system32\reg.exe · not signed
849f54dc526ea18d59abaf4904cb11bc15b982d2952b971f2e1b6fbf8c974b396.3.9600.16384 (winblue_rtm.130821-1623) · C:\windows\SysWOW64\reg.exe · not signed
b0bea6e6254f069b22fe9b6af14a316587dfd4b6642134677de5901744f4a08eFrom the file’s version info and the copies recorded by xCyclopedia (MIT). A copy in another folder, signed by someone else or with another hash is not necessarily malicious, but it is worth a closer look. In Ceplin, "<sha256>".whatis() says which known copy a hash is.