offensive-tools/forensic/ftk-imager/SKILL.md
FTK Imager: forensic acquisition and image viewing tool for disk images, logical files, and memory. Use to open and browse .dd/.E01/.img/.vmdk disk images without Autopsy, acquire memory dumps, convert image formats, export specific files from images, and verify integrity with hash verification. Also provides a free CLI version (ftkimager) for scriptable acquisition.
npx skillsauth add aeondave/malskill ftk-imagerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Disk image browser + acquisition tool — open images, extract files, acquire memory, verify hashes.
# Windows: download FTK Imager from exterro.com/ftk-imager (free registration)
# Install .exe → launches as GUI
# CLI version (Windows + Linux)
# ftkimager.exe (Windows) / ftkimager (Linux) — same flags
# Download: https://accessdata.com/product-download
# Linux CLI: also available as part of some forensic distros (DEFT, REMnux)
File → Add Evidence Item
→ Select Image File
→ Browse to .dd / .E01 / .img / .vmdk / .vhd
→ Image mounts in Evidence Tree on left
Navigate the tree to browse partitions and file systems. FTK Imager shows:
Right-click file or folder in Evidence Tree
→ Export Files...
→ Choose destination
Batch export: right-click a directory → Export Files → exports entire subtree.
Browse to partition root → scroll or look for entries with red X icon
# OR
File → Add Evidence Item → right-click partition → Export Files → includes deleted
File → Verify Drive/Image
→ Select image → runs MD5 + SHA1 hash → compare with acquisition record
File → Create Disk Image...
→ Source: Existing image
→ Select .dd as output → converts E01 → raw dd
→ or select E01 → converts dd → E01
# Acquire physical disk to E01 image
ftkimager \\.\PhysicalDrive0 output_case --e01 --verify --case-number "2024-001" --examiner "Dave"
# Acquire to raw .dd
ftkimager \\.\PhysicalDrive0 output.dd --verify
# Acquire specific partition
ftkimager \\.\PhysicalDrive0 output --e01 --partition 2
# Verify existing image
ftkimager output.E01 --verify
# List physical devices (Windows)
ftkimager --list-drives
# Acquire memory (volatile RAM dump)
ftkimager \\.\PHYSICALMEMORY memdump.raw --verify
# Export specific file from image by path
ftkimager image.dd --export --data-path "Users\Dave\Desktop\secret.txt" --export-path .
# GUI
File → Capture Memory → select output path → capture
# CLI (Windows, run as admin)
ftkimager \\.\PHYSICALMEMORY memdump.raw --verify
# Output: memdump.raw (raw memory dump)
# Feed to Volatility3 immediately:
python3 vol.py -f memdump.raw windows.pslist
| Format | Extension | Notes |
|--------|-----------|-------|
| Raw/DD | .dd, .raw, .img | No compression, universally supported |
| EnCase | .E01, .Ex01 | Compressed, metadata-rich, industry standard |
| SMART | .s01 | Older EnCase format |
| VMware | .vmdk | VM disk — open directly |
| VirtualBox | .vhd, .vhdx | VM disk |
| AFF | .aff | Advanced Forensics Format |
Conversion priority: FTK Imager handles all → export to .dd for widest tool compatibility.
# After acquisition, FTK Imager generates:
# image.E01 (or .dd)
# image.E01.txt — case notes with MD5/SHA1
# Verify from CLI
ftkimager image.E01 --verify
# Manual hash check
md5sum image.dd
sha256sum image.dd
# Compare with hash in acquisition notes
File → Image Mounting
→ Select image
→ Mount Type: Physical & Logical Read Only
→ Drive Letter assigned automatically
Now accessible as F:\ (or assigned letter) — open in Explorer or analyze with tools.
# Mount raw .dd image
sudo losetup -f disk.dd
sudo losetup -a # find loop device (e.g., /dev/loop0)
sudo mount -o ro,offset=$((2048*512)) /dev/loop0 /mnt/image
# Mount E01 with ewf-tools
sudo apt install libewf-dev ewf-tools
sudo ewfmount image.E01 /mnt/ewf/
sudo mount -o ro,offset=$((2048*512)) /mnt/ewf/ewf1 /mnt/image
# Unmount
sudo umount /mnt/image
sudo ewfunmount /mnt/ewf/
# Create E01 from raw dd (using ewfacquire)
ewfacquire -t output_case disk.dd
# Read/convert E01 to dd (using ewfexport)
ewfexport image.E01 -t image -f raw
# Verify E01 integrity (using ewfverify)
ewfverify image.E01
# Mount E01 (ewfmount)
sudo ewfmount image.E01 /mnt/ewf/
GUI: File → Add Evidence Item → Image File → select image
CLI: mount to /mnt/image then use standard tools
# GUI: navigate to file → right-click → Export Files
# CLI:
ftkimager image.dd --export --data-path "path/to/file.txt" --export-path ./extracted/
# Windows (admin)
ftkimager \\.\PHYSICALMEMORY memdump.raw --verify
# → feed to volatility3
python3 vol.py -f memdump.raw windows.pslist
# Using FTK CLI
ftkimager image.E01 converted.dd
# Using ewfexport
ewfexport image.E01 -t converted -f raw
# Output: converted.raw
mv converted.raw converted.dd
| Tool | Use case |
|------|---------|
| autopsy | GUI investigation after image acquisition |
| sleuth-kit | CLI file system analysis on acquired image |
| volatility3 | Memory analysis after RAM acquisition |
| hashcat | Crack hashes found after extraction |
| binwalk | Analyze extracted binary artifacts |
| strings / xxd | Quick file content inspection |
| File | When to load |
|------|--------------|
| references/ | E01 acquisition parameters, multi-image cases, hash verification workflow |
data-ai
Scoped routing: Linux operator; hosts, sessions, users, services, packages, logs, containers, SSH, network paths, privilege evidence.
development
Offensive methodology for ICS/OT/SCADA environments in authorized industrial penetration testing and red team operations. Use when assessing PLCs, RTUs, HMIs, engineering workstations, historians, or field devices running Modbus, DNP3, EtherNet/IP, S7comm/S7+, Profinet, IEC 60870-5-104, BACnet, or OPC-UA. Covers passive OT network enumeration, protocol-level device interrogation, PLC coil/register read-write attacks, HMI session exploitation, historian and engineering workstation compromise, and safe escalation rules for critical infrastructure scope. Does not cover: general IT network exploitation (network-technique), physical hardware interfaces UART/JTAG/SPI (hardware-technique), wireless sensor network attacks (wireless-technique), RF/SDR signal analysis (hardware-ctf or wireless-technique), or CTF-framed ICS lab tasks (ics-ctf).
tools
Offensive methodology for authorized game security assessments, game client security research, and game-adjacent penetration testing in real-world engagements. Use when assessing game clients for cheating vulnerabilities, testing anti-cheat effectiveness, auditing game server protocols for score manipulation or economic fraud, reverse engineering game DRM or license validation, analyzing game save file protection, or assessing game mod/plugin security. Covers: process memory scanning and manipulation (Cheat Engine methodology), game binary reversing for license and DRM bypass, game network protocol analysis and packet replay, anti-cheat mechanism analysis, save file format reversing and tampering, speed hack and value injection techniques. Does NOT cover: CTF game challenges (game-ctf), game engine source code auditing (web-exploit-technique or vuln-search-technique for the backend), or general binary exploitation (pwn-ctf or reversing-technique).
development
Auth assessment: hardware/embedded methodology; UART/JTAG/SWD/SPI/I2C, firmware extraction, boot/debug paths, embedded OS evidence.