Forensics Utilities: Free, fast, zero-storage forensic analysis tools for cybersecurity and digital investigation
Home / Tools / UserAssist & ROT13 Decoder
Execution Evidence // NTUSER.DAT Forensics

Windows UserAssist & ROT13 Decoder

Decode ROT13 obfuscated executable paths and extract critical evidence of execution from Windows Registry UserAssist keys. Parses 72-byte binary structures to recover execution counts, user focus duration, and exact 64-bit FILETIME last execution timestamps.

ROT-13 Path Unmasking & KnownFolder GUID Resolution
Run Count, Focus Count & Duration Extraction
64-Bit FILETIME UTC Timestamp Reconstruction
> NTUSER.DAT REGISTRY WIN 7 - 11 // 72B
Rot13: pzq.rkr → cmd.exe
Exec Count: 14 runs (Focus: 8m 42s)
• FILETIME: 2026-10-18 14:22:09 UTC

Paste UserAssist .REG Export, Registry Snippet, or Binary Hex Bytes

Supports Windows Registry Editor Version 5.00 format, comma-separated hex:, and raw byte dumps. 0 characters
TOTAL ARTIFACTS
0
SUSPICIOUS / LOTL
0
TOTAL PROGRAM RUNS
0
MOST RECENT EXECUTION
--
EXECUTION ARTIFACTS

Decoded Program Execution Timeline

0 Entries
# Program / Executable Path Run Count Focus Count Focus Duration Last Executed (UTC) Local System Time Classification

UserAssist Forensic Analysis Deep Dive

In Windows endpoint forensics, establishing proof of program execution is essential for reconstructing an attacker's lateral movement, credential access, or data exfiltration activities. The UserAssist registry keys provide investigators with conclusive evidence that a specific executable or shortcut was launched by an interactive user.

How Microsoft UserAssist Works in Windows 7, 10, and 11

UserAssist records reside in each user's personal registry hive: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\UserAssist\{GUID}\Count. The two common sub-GUIDs are {CEBFF5CD-ACE2-4F4B-9178-9926F47FB9BA} (for applications and executables) and {F4E57C4B-2036-45F0-A9AB-443BCFE33D9F} (for shortcut files).

1. The ROT-13 Obfuscation Mechanism

Windows obfuscates the value names of the UserAssist Count key with standard ROT-13 substitution. For example, pzq.rkr translates to cmd.exe, and cbjrefuryy.rkr translates to powershell.exe.

2. Win7–Win11 72-Byte Binary Structure

Bytes 4–7 hold the Run Count, Bytes 8–11 hold the Focus Count, Bytes 12–15 hold Focus Time in milliseconds, and Bytes 60–67 store the exact Last Execution Time as a 64-bit Windows FILETIME.

3. KnownFolder GUID Redirection

Windows replaces system directories with KnownFolder GUIDs inside UserAssist: {1AC14E77-...} resolves to C:\Windows\System32, and {D65231B0-...} resolves to System32\WindowsPowerShell\v1.0.

4. Anti-Forensic Tampering & NoLog

Adversaries may attempt to delete the Count subkey or set a DWORD named NoLog = 1 in the UserAssist root to disable tracking. In such cases, examiners correlate with Prefetch, Amcache, and Shimcache.

UserAssist Binary Layout Specification

Byte Offset Data Type Field Name Forensic Significance
0x00 - 0x03 DWORD (4 Bytes) Session ID Tracks the GUI logon session identifier.
0x04 - 0x07 DWORD (4 Bytes) Run Count Total number of times the program was executed by the user.
0x08 - 0x0B DWORD (4 Bytes) Focus Count Number of times the user switched focus to the window.
0x0C - 0x0F DWORD (4 Bytes) Focus Duration Total time (in milliseconds) the program had active user focus.
0x3C - 0x43 FILETIME (8 Bytes) Last Execution Timestamp 64-bit UTC timestamp recording the exact last launch time.

Frequently Asked Questions (FAQ)

UserAssist records reside in each user's personal registry hive: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\UserAssist\{GUID}\Count. The two common sub-GUIDs are {CEBFF5CD-ACE2-4F4B-9178-9926F47FB9BA} (for applications and executables) and {F4E57C4B-2036-45F0-A9AB-443BCFE33D9F} (for shortcut files).

No. UserAssist only records the executable name or shortcut path, execution count, focus time, and the last launch timestamp. To recover exact command-line arguments (such as malicious PowerShell flags or base64 encoded scripts), examiners must inspect Security Event ID 4688, Sysmon Event ID 1, or PowerShell Script Block Logging (Event ID 4104).

No. ForensicsInsider tools operate 100% in local browser memory. All ROT-13 unmasking, binary byte-slicing, and 64-bit FILETIME mathematical conversions execute client-side. Zero bytes leave your machine.