Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.
When investigating user activity on a Windows system during an incident
For identifying autorun/persistence mechanisms used by malware
When tracing installed software, USB devices, and network connections
During insider threat investigations to reconstruct user actions
For correlating registry timestamps with other forensic artifacts
Detection Gaps & Validation
ShimCache (AppCompatCache) proves presence, not execution, and lags. Entries are written to the SYSTEM hive only at shutdown, so recent activity is missing until the next reboot, and an entry only means the binary was seen by the system. Pair it with Amcache/Prefetch for execution.
Dirty hives need transaction-log replay. If you parse SYSTEM/NTUSER.DAT without applying .LOG1/.LOG2, RegRipper/python-registry may return stale or truncated data. Always collect and replay the logs (RECmd/EZ tools do this).
Last Write Time is per-key, not per-value. A key timestamp tells you the most recent value change, not which value changed. Do not attribute a single value's age to the key timestamp.
UserAssist is ROT13-encoded and counts focus/run from Explorer only; CLI-launched programs are absent. BAM/DAM (bam\State\UserSettings\<SID>) gives Win10+ last-run times worth checking separately.
Timezone: apply SYSTEM\...\TimeZoneInformation (bias) before placing registry timestamps on a UTC timeline.
Anti-forensics: Run-key/value deletion, key timestamp manipulation, and RegDelNull-style hidden keys. Carve deleted keys from hive slack / unallocated and check VSS copies.
Validate / cross-corroborate: confirm execution and persistence against Amcache, Prefetch, Security.evtx (4688/4697/4698), and Scheduled Tasks XML. USBSTOR serials should reconcile with MountedDevices and NTUSER MountPoints2.
Prerequisites
Forensic image or extracted registry hive files
RegRipper, Registry Explorer (Eric Zimmerman), or python-registry
Access to registry hive locations (SAM, SYSTEM, SOFTWARE, NTUSER.DAT, UsrClass.dat)
Understanding of Windows Registry structure (hives, keys, values)
SIFT Workstation or forensic analysis environment
Workflow
Step 1: Extract Registry Hives from the Forensic Image
Detailed execution history including SHA-1 hashes of executables
BAM/DAM
Background/Desktop Activity Moderator tracking program execution in Win10+
Last Write Time
Timestamp on registry keys indicating when they were last modified
Transaction logs
Journal files allowing recovery of registry state after improper shutdown
Tools & Systems
Tool
Purpose
RegRipper
Automated registry artifact extraction with plugin architecture
Registry Explorer
Eric Zimmerman GUI tool for interactive registry analysis
python-registry
Python library for programmatic registry hive parsing
RECmd
Eric Zimmerman command-line registry analysis tool
yarp
Yet Another Registry Parser for Python-based analysis
AppCompatCacheParser
Dedicated ShimCache/AppCompatCache parser
AmcacheParser
Dedicated AmCache.hve analysis tool
ShellBags Explorer
Specialized tool for analyzing ShellBag artifacts
Common Scenarios
Scenario 1: Malware Persistence Investigation
Extract SOFTWARE and NTUSER.DAT hives, check all Run/RunOnce keys for unauthorized entries, examine services for suspicious additions, check scheduled tasks registry keys, correlate autorun timestamps with malware execution timeline.
Scenario 2: User Activity Reconstruction
Analyze UserAssist for program execution history, examine RecentDocs for accessed files, check TypedPaths for Explorer navigation, extract ShellBags for folder access patterns, build a timeline of user activity around the incident window.
Scenario 3: Unauthorized Software Detection
Parse Uninstall keys for all installed applications, compare against approved software baseline, check BAM/DAM for recently executed programs not in approved list, examine AppCompatCache for execution evidence even after uninstallation.
Scenario 4: USB Data Exfiltration Investigation
Extract USBSTOR entries from SYSTEM hive for connected devices, correlate device serial numbers with MountedDevices, check NTUSER.DAT MountPoints2 for user access to removable media, examine SetupAPI logs for first-connection timestamps.