CHFI (312-49) Digital Forensics Simulation
Learn how to analyze Windows application compatibility artifacts to determine initial execution timelines during ransomware investigations. This scenario focuses on identifying reliable execution artifacts when standard file system timestamps are suspect.
Investigation Scenario
A major healthcare organization has been compromised by a ransomware strain, encrypting critical patient databases and mapped network drives. The security team has contained the infected endpoints, but the digital forensics unit must identify the initial access vector and patient zero.
During the examination of a compromised domain controller, analysts locate a highly suspicious executable named win_update_svc.exe in the C:\Windows\Temp\ directory. However, the NTFS MAC (Modified, Accessed, Created) timestamps on the file are anomalous and appear to have been intentionally altered (timestomped) by the threat actor to blend in with OS installation dates. Investigators need an alternative artifact to prove if and when this file was executed.
Evidence Collected
- Acquired Image: DC01_Disk0.E01 (SHA-256 Verified)
- Target File: C:\Windows\Temp\win_update_svc.exe
- Extracted Registry Hives: SYSTEM, SOFTWARE, NTUSER.DAT
- Memory Dump: DC01_memdump.raw (Provides volatile state prior to shutdown)
Question
A healthcare organization was hit by ransomware. The investigator needs to determine the initial access method. Which Windows artifact provides information about when an unusual executable was first run?
Expert Analysis
1. What the Evidence Shows
The core issue is that standard file system (NTFS) timestamps are unreliable due to suspected timestomping. The investigator must rely on deep operating system artifacts that record the execution history of binaries independently of the file system's MAC timestamps.
2. Forensic Stage
Examination & Analysis: Parsing registry hives and correlating system execution artifacts to reconstruct a timeline of malicious activity.
3. Why the Correct Answer is Correct
(A) ShimCache (AppCompatCache): The Application Compatibility Cache (ShimCache) is a component of the Application Experience service in Windows. It tracks executables to resolve compatibility issues with legacy applications. Crucially for forensics, it records the file's full path, its last modified time (prior to execution), and is highly resilient against file system-level timestomping. Finding an entry for the suspicious executable in the ShimCache proves the file was present and typically indicates it was executed by the operating system.
4. Why Others Are Wrong
(B) Recycle Bin: Contains files deleted by the user through the GUI. It does not track application execution.
(C) Windows Update logs: (e.g., WindowsUpdate.log) Track the downloading and installation of official Microsoft patches and updates, not the execution of arbitrary or malicious third-party executables.
(D) Desktop Wallpaper settings: Stored in the registry or user profile, these settings only relate to user interface personalization and provide zero forensic value regarding binary execution.
5. Real-World Forensic Action
An investigator would extract the SYSTEM registry hive from the evidence image. Navigating to SYSTEM\CurrentControlSet\Control\Session Manager\AppCompatCache, the investigator would use a specialized tool like Eric Zimmerman's AppCompatCacheParser to parse the raw hex data into a readable CSV. They would search this output for win_update_svc.exe to identify its true execution timeline, bypassing the manipulated NTFS timestamps.
6. MINI LESSON: Windows Execution Artifacts
Threat actors frequently alter file MACB timestamps (timestomping) to hide their tracks. A competent forensic investigator knows never to rely solely on the file system. Instead, they look for "Execution Artifacts." These include: ShimCache (tracks executable paths and last modified times), Amcache (tracks application installations, loaded drivers, and SHA-1 hashes of executed files), Prefetch (tracks the first 10 seconds of application execution to speed up future load times), and UserAssist (tracks GUI-based execution). Correlating these artifacts paints an irrefutable picture of attacker activity.
Master Digital Forensics
Ready to tackle more realistic CHFI scenarios?
Explore more CHFI simulations