performing-windows-artifact-analysis-with-eric-zimmerman-tools

Parse Windows forensic artifacts with EZ Tools including MFT, prefetch, registry hives, and event logs.

954|172|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/xalgord/xalgorix --skill performing-windows-artifact-analysis-with-eric-zimmerman-tools
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: performing-windows-artifact-analysis-with-eric-zimmerman-tools
Source: https://github.com/xalgord/xalgorix/tree/main/internal/tools/skills/data/digital-forensics/performing-windows-artifact-analysis-with-eric-zimmerman-tools
Command: npx skills add https://github.com/xalgord/xalgorix --skill performing-windows-artifact-analysis-with-eric-zimmerman-tools

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Windows forensic investigations require parsing dozens of low-level artifacts like the Master File Table, registry hives, prefetch files, and event logs, each with its own binary format. This Skill guides the use of Eric Zimmerman's EZ Tools suite to collect, parse, and correlate these artifacts into structured CSV output for timeline analysis.

Core Features & Use Cases

  • Automated Collection and Processing: Use KAPE to collect triage artifacts from forensic images or live systems and process them with the full EZ Tools parser suite.
  • Artifact Parsing: Parse $MFT and USN Journal with MFTECmd, prefetch files with PECmd, registry hives with RECmd, event logs with EvtxECmd, LNK files with LECmd, jump lists with JLECmd, and shellbags with SBECmd.
  • Timeline and Anti-Forensics Analysis: Load CSV output into Timeline Explorer to build chronological views and detect timestomping by comparing $STANDARD_INFORMATION and $FILE_NAME timestamps.
  • Use Case: During an incident response engagement, collect a KAPE triage image from a compromised workstation, process it with the !EZParser module, and correlate prefetch, Amcache, MFT, and Security 4688 events to prove whether a suspicious binary actually executed.

Quick Start

Use this skill to collect a KAPE triage image from the mounted forensic drive and process it with the EZ Tools parsers for timeline analysis.

Frequently Asked Questions about performing-windows-artifact-analysis-with-eric-zimmerman-tools

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I parse Windows prefetch files for evidence of execution?

Use PECmd with the -d flag pointing at the Prefetch directory to parse all .pf files into CSV, or -f for a single file. Add -k with keywords like powershell or cmd to filter for suspicious executions, and cross-reference results with Amcache and MFT records.

How to detect timestomping in NTFS with MFTECmd?

Parse the $MFT with MFTECmd and compare the Created0x10 ($STANDARD_INFORMATION) and Created0x30 ($FILE_NAME) columns in Timeline Explorer. When $SI predates $FN, the file timestamps were likely backdated, since $FN times resist user-mode manipulation.

What is the difference between KAPE targets and modules?

KAPE targets (.tkape files) define which artifacts to collect from a source drive, such as registry hives or event logs. Modules (.mkape files) define which tools, like MFTECmd or EvtxECmd, run against the collected data to produce parsed output.

Does ShimCache prove a program was executed?

No. ShimCache (AppCompatCache) entries only prove a binary existed or was referenced on the system, not that it ran. Confirm execution by correlating with Prefetch, Amcache, MFT creation records, and Security Event ID 4688 or Sysmon Event ID 1.

What are the limitations of prefetch and event log analysis?

Prefetch retains only about the last 1024 executions and may be disabled on servers or SSDs, while EVTX logs roll by size and can be cleared (Event ID 1102). Recover deleted records from Volume Shadow Copies and treat single-artifact findings as leads, not conclusions.