offensive-tools/forensic/autopsy/SKILL.md
Auth/lab ref: GUI digital forensics platform built on The Sleuth Kit. For visually triage a disk image: open image, run ingest modules, search artifacts.
npx skillsauth add aeondave/malskill autopsyInstall 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.
GUI disk forensics over The Sleuth Kit — deleted files, browser artifacts, registry, keyword search, timeline.
# Windows: download MSI installer from autopsy.com (recommended)
# Linux (Kali)
sudo apt install autopsy # CLI-only version (browser-based at localhost:9999)
# Linux GUI: requires Java + dependencies
# https://www.autopsy.com/download/
# Launch (Linux CLI version)
autopsy
# Opens: http://localhost:9999/autopsy in browser
Disk Image or VM File — .dd, .raw, .E01, .vmdk, .vhdLocal Disk — live disk (write-blocker recommended)Logical Files — individual files or directories| Module | What it finds | Enable for | |--------|--------------|-----------| | Recent Activity | Browser history, downloads, searches, USB devices | Always | | Hash Lookup | Known-bad/known-good files via hash sets | Always | | File Type Identification | Magic byte file type detection | Always | | Keyword Search | Regex/literal string search across all files | Always | | Email Parser | Outlook PST/OST, mbox email artifacts | Email investigations | | Embedded File Extractor | Files inside ZIP/RAR/Office docs | Always | | EXIF Parser | GPS + metadata from images | Photo investigations | | Extension Mismatch Detector | Files renamed to hide true type | Always | | Android Analyzer | Android DB artifacts | Mobile forensics | | Interesting Files | Pre-defined suspicious file patterns | Always | | PhotoRec Carver | Carve deleted/unallocated files | Deleted file recovery |
Recommended minimal set for fast triage:
Recent Activity + File Type Identification + Keyword Search + Embedded File Extractor + PhotoRec Carver
After ingest, the left tree exposes:
Data Sources
└── disk.img
├── vol1 (NTFS, 50GB)
│ ├── $OrphanFiles ← deleted files with no parent dir
│ ├── Users/
│ ├── Windows/
│ └── ...
Results
├── Extracted Content
│ ├── Bookmarks
│ ├── Cookies
│ ├── Downloads
│ ├── History
│ ├── Installed Programs
│ ├── Recent Documents
│ ├── Recycle Bin
│ ├── Search History
│ └── Web Form Autofill
├── Extension Mismatch Detected
├── Interesting Files
├── Keyword Hits
├── Metadata
└── Tags
Views
├── File Types
│ ├── Images
│ ├── Videos
│ ├── Documents
│ └── Executables
├── Deleted Files
└── File Size
Views → Deleted Files
# or
Data Sources → vol1 → $OrphanFiles
# Sort by name, extension, or date
Right-click → Extract File(s) to recover.
Tools → Keyword Search (or press Ctrl+F)
Options:
# Common patterns to search:
flag{.*}
password:
-----BEGIN.*KEY-----
[A-Za-z0-9+/]{20,}= # base64
\b\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}\b # IP addresses
Results appear under Results → Keyword Hits. Click entry → view source file + highlighted match.
Results → Extracted Content → History
Results → Extracted Content → Downloads
Results → Extracted Content → Bookmarks
Results → Extracted Content → Cookies
Results → Extracted Content → Search History
Filter by date. Sort by timestamp to reconstruct activity sequence.
Tools → Timeline (clock icon on toolbar)
Results → Extension Mismatch Detected
Files where magic bytes don't match extension — hidden data technique.
# CLI equivalent to find mismatches
file /path/to/extracted/* | grep -v "matches"
Autopsy runs PhotoRec automatically when module enabled. Results appear under:
Results → Extracted Content → Carved Files
# or
Data Sources → vol1 → $CarvedFiles
Useful for: JPEGs/PNGs hidden in unallocated space, ZIP archives, PDF fragments.
Autopsy extracts registry hives from Windows images automatically.
Data Sources → vol1 → Windows/System32/config/
# SAM, SYSTEM, SECURITY, SOFTWARE hives available as files
# Extract hive, then analyze with:
# - RegRipper (regripper.exe / rip.pl)
# - Registry Explorer (Eric Zimmermann tools)
# - python-registry (Python parsing)
Common registry paths to check:
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run # startup
HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\Run # user startup
HKLM\SYSTEM\CurrentControlSet\Services # services
HKLM\SAM\SAM\Domains\Account\Users # user accounts
NTUSER.DAT\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\RecentDocs # recent files
NTUSER.DAT\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\RunMRU # run dialog history
# Look for unusual files in image:
Views → File Types → Images
# Sort by size — oversized images may contain hidden data
# Cross-check with steghide/zsteg/stegsolve after extraction
Results → Extracted Content (look for .zip, .7z, .rar, .veracrypt)
# or keyword search for "PK" (ZIP magic), "Rar!" (RAR magic), "7z" (7zip magic)
Autopsy doesn't surface ADS directly — use Sleuth Kit CLI:
# After finding target volume offset
fls -o 2048 disk.img | grep "::" # ADS entries have "::" in name
icat -o 2048 disk.img <inode>:<stream> > ads_content
# Export files
Right-click file → Extract File(s)
# Tag files for report
Right-click → Add File Tag → Notable Item
# Generate report
Tools → Generate Report
# Select: HTML Report / Excel / KML / etc.
# Include: Tagged files / Keyword hits / All results
# Launch web UI
autopsy &
# Access at http://localhost:9999/autopsy
# CLI: create case + add image via TSK directly (see sleuth-kit skill)
mmls disk.img
fls -r -o 2048 disk.img | grep -i "flag\|secret"
icat -o 2048 disk.img <inode> > extracted_file
| Tool | Use case |
|------|---------|
| sleuth-kit | CLI complement for scriptable extraction |
| binwalk | Analyze extracted binaries/firmware |
| volatility3 | After extracting memory dump artifact |
| wireshark | After finding .pcap in disk image |
| hashcat | Crack password hashes found in SAM/registry |
| steghide / zsteg | Check images found for steganography |
| strings | Quick scan of extracted files |
| File | When to load |
|------|--------------|
| references/ | Ingest module selection guide, registry artifact map, timeline interpretation |
development
White-box auditing methodology for AI-generated ('vibe-coded') applications. Focuses on modern stack misconfigurations (Supabase, Next.js, Vercel).
development
Hybrid AI/Deterministic SAST methodology for discovering zero-day vulnerabilities in source code. Orchestrates structural search with AI-driven data flow and sink validation.
development
Auth assessment: hardware/embedded methodology; UART/JTAG/SWD/SPI/I2C, firmware extraction, boot/debug paths, embedded OS evidence.
devops
Container methodology: Identifying containerization limits, Docker/K8s misconfigurations, and executing escapes to the host node.