Case EE51B1 · Blue team / DFIR · L2 Practitioner
Prefetch, Amcache and Shimcache
- 01 What is it?
- 02 How is it abused?
- 03 How do you stop it?
What a strong answer covers
Try it out loud first. Then check yourself:
- Prefetch (.pf in C:\Windows\Prefetch): run count and up to 8 last run times on Win8+; often disabled by default on servers.
- Amcache.hve records path, SHA1 and metadata of programs present or run; strong for hashes, weaker as proof of execution.
- Shimcache (AppCompatCache, SYSTEM hive) shows a file existed; on Win10+ it does not prove execution and writes at shutdown.
- Attackers delete .pf files, rename tools and timestomp; deletion itself leaves gaps you can spot in $UsnJrnl and SRUM.
- Corroborate across artifacts (BAM, UserAssist, 4688, EDR) and collect early; one artifact alone rarely proves execution.
If the interviewer pushes back
- Shimcache lists a renamed psexec on a server where Prefetch is off. How do you prove whether and when it ran?