Artifact Analysis: Prefetch, Shimcache, and Amcache
You'll learn how Windows tracks program execution through three critical artifacts that reveal what ran, when, and how often.
What These Artifacts Tell You
Windows maintains several databases that record application execution—think of them as automatic logbooks that Windows keeps for performance optimization, but which become goldmines for incident responders. These artifacts survive reboots and often outlive the malware itself.
The Three Key Execution Artifacts
Prefetch Files
Located in C:\Windows\Prefetch\, these .pf files optimize application loading by caching file locations. Each prefetch file contains:
- Last 8 execution timestamps (Windows 10+)
- Run count (how many times executed)
- Files and directories accessed during first 10 seconds
- Original executable path
Shimcache (AppCompatCache)
Stored in the registry at HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\AppCompatCache, this tracks executables for compatibility checking. It records:
- Full file path
- Last modified timestamp
- Execution flag (varies by Windows version)
- Can contain hundreds of entries
Amcache
Found in C:\Windows\AppCompat\Programs\Amcache.hve, this registry hive logs installed applications and executed programs:
- First execution time
- File hash (SHA1)
- File size and metadata
- Publisher information
Timeline Reconstruction Power
Together, these artifacts create a comprehensive execution timeline. Prefetch confirms execution and frequency, Shimcache shows what was present on disk, and Amcache provides installation context and hash values for threat intelligence correlation.
Key Takeaway: Prefetch, Shimcache, and Amcache form a triad of program execution evidence that persists even after malware is deleted, enabling investigators to reconstruct attacker activities and establish attribution through timestamps, paths, and file hashes.