mftecmd
Auth/lab ref: NTFS metadata triage with MFTECmd for $MFT/$J/$I30/$Boot artifacts.
v2026.11.13-21cd5683 installs+3 in 7 days39 StarsApache-2.0synced 10 hours ago
Install
No NotHoly CLI yet? Install it first.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install aeondave/mftecmdWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Packagee598556a…d78a810f
e598556a3c77…d0fed78a810f1 file · 1.1 KBScanLowno findings
Sourcegithub.com/AeonDave/malskill/tree/main/offensive-tools/forensic/mftecmd@21cd568
On this page
Structured extraction and timeline analysis of NTFS metadata artifacts.
When to use
- You received an
$MFT(or NTFS metadata set) and need forensic timeline answers. - You must identify deleted, hidden, copied, or modified files quickly.
- You need reproducible metadata export for filtering in Timeline Explorer/CSV tools.
Core workflow
- Parse artifact into structured output (CSV/JSON).
- Normalize timezone assumptions before interpretation.
- Filter for key flags and record metadata:
- in-use vs deleted
- hidden/system flags
- copied/renamed indicators
- entry/record number pivots
- Compare creation vs modification times for suspicious edits.
- Build concise chronology and annotate confidence.
Analyst pivots
- By
EntryNumberfor objective-driven tasks. - By filename/extension for target-object hunts.
- By timestamp deltas for post-creation tampering.
- By flags for hidden/deleted artifacts.
Practical tips
- Export first, investigate second: deterministic outputs reduce mistakes.
- Treat timestamp precision consistently (same timezone/display granularity).
- Keep system files excluded only when case requirements explicitly request it.
- Cross-check critical findings with other artifacts when available (logs, prefetch, registry).
Common pitfalls
- Confusing renamed/copied artifacts with newly created originals.
- Treating a single timestamp in isolation as full chronology.
- Ignoring metadata context (directory entries, flags, and record linkage).
Output expectations
- Artifact summary (years/periods of activity, notable paths).
- Findings table with record IDs, filename, key timestamps, relevant flags.
- Timeline segment of suspicious or investigation-relevant file operations.
Files in this version
- SKILL.md2.0 KB
Permissions
| Permission | Declared | Found by the scan |
|---|---|---|
| Reads files | No | No |
| Writes files | No | No |
| Runs shell commands | No | No |
| Uses the network | No | No |
| Uses connectors | No | No |
| Drives a browser | No | No |
Scan findings
Reviewed on Nov 13, 2026
The scan found nothing to flag in this version.
A clean scan lowers the risk but does not prove a package is safe. Read what you install.
| Version | Published | Commit | SHA-256 | Signature | Permission change |
|---|---|---|---|---|---|
| v2026.11.13-21cd568 | Nov 13, 2026 | 21cd568 | e598556a | Signed | – |
More from AeonDave
All from this publisherMore in DFIR and threat hunting
See the category- hunting-for-command-and-control-beaconingmukul975/hunting-for-command-and-control-beaconing5
- audit-context-buildingtrailofbits/audit-context-building4
- incident-response-forensicssecurityskills/incident-response-forensics3
- extracting-credentials-from-memory-dumpmukul975/extracting-credentials-from-memory-dump3
- analyzing-browser-forensics-with-hindsightmukul975/analyzing-browser-forensics-with-hindsight3
- forensics-ctfaeondave/forensics-ctf3
Ask anything your scope allows.
Create an account, add credits and ask the first question in the chat or the terminal.
- 1/3
Create the account
Individual or company. You can switch to a company later without losing balance or keys.
IndividualCompany - 2/3
Add credits
By card. Pay per token, no subscription.
$5.00minimum deposit - 3/3
Ask
In the chat, or install the CLI and run notholy login in your terminal.
$ notholy login