Skip to content

ShulkwiSEC/bb-huge / skills/curated/windows-prefetch-analysis

windows-prefetch-analysis

Unverified

Analyze Windows prefetch files (.pf) to determine evidence of program execution. This skill details how to extract execution times, run counts, and the paths of files accessed by a program, which is critical for incident response and malware timeline reconstruction.

Windows Prefetch Analysis

When to Use

  • When investigating a compromised Windows system to answer the question: "Did the attacker actually run this tool/malware?"
  • To build a timeline of threat actor activities by examining execution timestamps and accessed files.
  • When an attacker has deleted their malware, but the prefetch file remains as evidence.

Prerequisites

  • Forensic image or live access to the affected system(s)
  • Forensic workstation with analysis tools (Autopsy, Volatility, Timeline Explorer)
  • Chain of custody documentation initiated for evidence handling
  • Write-blocker for disk forensics or memory acquisition tool (e.g., DumpIt, WinPmem)

Workflow

Phase 1: Locating and Understanding Prefetch Files

Prefetch files are typically located at C:\Windows\Prefetch. They are named ending with .pf (e.g., CMD.EXE-4A81B364.pf).

Note: Prefetch is enabled by default on Windows Client OS architectures but may be disabled on Windows Servers.

Phase 2: Offline Analysis with PECmd (Eric Zimmerman's Tools)

# Concept: Parse a single prefetch file PECmd.exe -f "C:\Windows\Prefetch\MIMIKATZ.EXE-53D22409.pf"

# PECmd.exe -d "C:\Windows\Prefetch\" -q --csv "C:\Forensics\Output" --csvf "prefetch_timeline.csv"

Phase 3: Interpreting the Output

When examining the parsed output, focus on:

  • Run Count: How many times was the binary executed?
  • Execution Times: Up to 8 previous execution timestamps (depending on OS version). Last execution time is crucial for timeline building.
  • Files/Directories Accessed: The directories and files the program loaded (e.g., DLLs, configuration files, text files the attacker interacted with).

Phase 4: Basic Live System Check (Powershell)

# Get-ChildItem -Path "C:\Windows\Prefetch" | Where-Object { $_.Name -match "MIMIKATZ|PSEXEC|NC.EXE" } | Select-Object Name, LastWriteTime

Decision Point πŸ”€

flowchart TD
    A[Locate Prefetch Folder ] --> B{Prefetch Enabled? ]}
    B -->|Yes| C[Extract .pf Files ]
    B -->|No| D[Check ShimCache/Amcache ]
    C --> E[Parse with PECmd ]

πŸ”΅ Blue Team Detection & Defense

  • Monitor Deletion of Prefetch Files: Centralized Forensics Collection: Threat Hunting via File Paths: Key Concepts | Concept | Description | |---------|-------------|

Output Format

Windows Prefetch Analysis β€” Assessment Report
============================================================
Target: [Target identifier]
Assessor: [Operator name]
Date: [Assessment date]
Scope: [Authorized scope]
MITRE ATT&CK: [Relevant technique IDs]

Findings Summary:
  [Finding 1]: [Severity] β€” [Brief description]
  [Finding 2]: [Severity] β€” [Brief description]

Detailed Results:
  Phase 1: [Phase name]
    - Result: [Outcome]
    - Evidence: [Screenshot/log reference]
    - Impact: [Business impact assessment]

  Phase 2: [Phase name]
    - Result: [Outcome]
    - Evidence: [Screenshot/log reference]
    - Impact: [Business impact assessment]

Risk Rating: [Critical/High/Medium/Low/Informational]
Recommendations:
  1. [Immediate remediation step]
  2. [Long-term hardening measure]
  3. [Monitoring/detection improvement]

πŸ“š Shared Resources

For cross-cutting methodology applicable to all vulnerability classes, see:

References

reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 464kUpdated Claude CodeCodexVerifiedInstall
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 464kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why β€” repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" β€” or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 318kUpdated Claude CodeCodexUnverifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 318kUpdated Claude CodeCodexUnverifiedInstall