--- name: analyzing-mft-for-deleted-file-recovery-37d49a201727 description: Analyze the NTFS Master File Table ($MFT) with MFTECmd, analyzeMFT, and X-Ways Forensics to recover metadata and content of deleted files by examining MFT record entries, $LogFile, $UsnJrnl, and MFT slack space. Use when recovering evidence of deleted files, reconstructing NTFS file-system timelines, or detecting anti-forensic timestomping during a Windows forensic examination. domain: cybersecurity subdomain: digital-forensics tags: - mft - ntfs - deleted-files - file-recovery - mftecmd - usn-journal - logfile - mft-slack-space - file-system-forensics - dfir version: '1.0' author: mahipal license: Apache-2.0 nist_csf: - RS.AN-03 - DE.AE-02 - RS.MA-01 mitre_attack: - T1070.004 - T1070.006 - T1005 --- # Analyzing MFT for Deleted File Recovery ## Overview The NTFS Master File Table ($MFT) is the central metadata repository for every file and directory on an NTFS volume. Each file is represented by at least one 1024-byte MFT record containing attributes such as $STANDARD_INFORMATION (timestamps, permissions), $FILE_NAME (name, parent directory, timestamps), and $DATA (file content or cluster run pointers). When a file is deleted, its MFT record is marked as inactive (InUse flag cleared) but the metadata remains until the entry is reallocated by a new file. This persistence makes MFT analysis a primary technique for recovering deleted file evidence, reconstructing file system timelines, and detecting anti-forensic activity such as timestomping. ## When to Use - When investigating security incidents that require analyzing mft for deleted file recovery - When building detection rules or threat hunting queries for this domain - When SOC analysts need structured procedures for this analysis type - When validating security monitoring coverage for related attack techniques ## Prerequisites - Forensic disk image (E01, raw/dd, VMDK, or VHDX format) - MFTECmd (Eric Zimmerman) or analyzeMFT (Python-based) - FTK Imager, Arsenal Image Mounter, or similar for image mounting - Timeline Explorer or Excel for CSV analysis - Python 3.8+ for custom analysis scripts - Understanding of NTFS file system internals ## MFT Structure and Record Layout ### MFT Record Header Each MFT record begins with the signature "FILE" (0x46494C45) and contains: | Offset | Size | Field | |--------|------|-------| | 0x00 | 4 bytes | Signature ("FILE") | | 0x04 | 2 bytes | Offset to update sequence | | 0x06 | 2 bytes | Size of update sequence | | 0x08 | 8 bytes | $LogFile sequence number | | 0x10 | 2 bytes | Sequence number | | 0x12 | 2 bytes | Hard link count | | 0x14 | 2 bytes | Offset to first attribute | | 0x16 | 2 bytes | Flags (0x01 = InUse, 0x02 = Directory) | | 0x18 | 4 bytes | Used size of MFT record | | 0x1C | 4 bytes | Allocated size of MFT record | | 0x20 | 8 bytes | Base file record reference | | 0x28 | 2 bytes | Next attribute ID | ### Key MFT Attributes | Type ID | Name | Description | |---------|------|-------------| | 0x10 | $STANDARD_INFORMATION | Timestamps, flags, owner ID, security ID | | 0x30 | $FILE_NAME | Filename, parent MFT reference, timestamps | | 0x40 | $OBJECT_ID | Unique GUID for the file | | 0x50 | $SECURITY_DESCRIPTOR | ACL permissions | | 0x60 | $VOLUME_NAME | Volume label (volume metadata files only) | | 0x80 | $DATA | File content (resident if <700 bytes) or cluster run list | | 0x90 | $INDEX_ROOT | B-tree index root for directories | | 0xA0 | $INDEX_ALLOCATION | B-tree index entries for large directories | | 0xB0 | $BITMAP | Allocation bitmap for index or MFT | ## Deleted File Recovery Techniques ### Technique 1: MFT Record Analysis with MFTECmd ```powershell # Extract $MFT from forensic image using KAPE or FTK Imager # Parse the $MFT with MFTECmd MFTECmd.exe -f "C:\Evidence\$MFT" --csv C:\Output --csvf mft_full.csv # Filter for deleted files (InUse = FALSE) in Timeline Explorer # Look for entries where InUse column is False ``` **Identifying Deleted Files in CSV Output:** - `InUse` = False indicates a deleted or reallocated record - `ParentPath` shows original file location before deletion - `FileSize` shows the original size (may still be recoverable) - Timestamps in `$STANDARD_INFORMATION` and `$FILE_NAME` attributes persist ### Technique 2: USN Journal ($UsnJrnl:$J) Analysis The USN Journal records all changes to files on an NTFS volume, including creation, deletion, rename, and data modification events. ```powershell # Parse USN Journal with MFTECmd MFTECmd.exe -f "C:\Evidence\$J" --csv C:\Output --csvf usn_journal.csv # Key USN reason codes for deletion evidence: # USN_REASON_FILE_DELETE = 0x00000200 # USN_REASON_CLOSE = 0x80000000 # USN_REASON_RENAME_OLD_NAME = 0x00001000 # USN_REASON_RENAME_NEW_NAME = 0x00002000 ``` ### Technique 3: $LogFile Transaction Analysis The $LogFile stores NTFS transaction records that can reveal file operations even after the USN Journal has been cycled. ```powershell # Parse $LogFile with LogFileParser LogFileParser.exe -l "C:\Evidence\$LogFile" -o C:\Output # Look for REDO and UNDO operations indicating file deletion: # - DeallocateFileRecordSegment # - DeleteAttribute # - UpdateResidentValue (clearing InUse flag) ``` ### Technique 4: MFT Slack Space Analysis MFT slack space exists between the end of the used portion of an MFT record and the end of the allocated 1024 bytes. This area may contain remnants of previous file records. ```python import struct def parse_mft_slack(mft_path: str, output_path: str): """Extract and analyze MFT slack space for deleted file remnants.""" with open(mft_path, "rb") as f: record_size = 1024 record_num = 0 slack_findings = [] while True: record = f.read(record_size) if len(record) < record_size: break # Verify FILE signature if record[:4] != b"FILE": record_num += 1 continue # Get used size from offset 0x18 used_size = struct.unpack(" 0x20 and c < 0x7F for c in slack[:50]): slack_findings.append({ "record": record_num, "used_size": used_size, "slack_size": record_size - used_size, "slack_preview": slack[:100].hex() }) record_num += 1 return slack_findings ``` ## Correlation with Supporting Artifacts ### Cross-Reference MFT with $Recycle.Bin ```powershell # Parse Recycle Bin with RBCmd RBCmd.exe -d "C:\Evidence\$Recycle.Bin" --csv C:\Output --csvf recycle_bin.csv # Correlate: $I files contain original path and deletion timestamp # Match MFT entry numbers from $R files back to original MFT records ``` ### Cross-Reference MFT with Volume Shadow Copies ```powershell # List volume shadow copies vssadmin list shadows # Mount shadow copies and extract $MFT from each # Compare MFT records across shadow copies to track file changes over time ``` ## Forensic Value - **Deleted file metadata recovery**: Original filename, path, size, and timestamps - **Timeline reconstruction**: File creation, modification, access, and deletion events - **Timestomping detection**: Comparing $SI vs $FN timestamps - **Data carving guidance**: MFT cluster runs point to file content on disk - **Anti-forensic detection**: Identifying wiped or manipulated MFT records ## References - NTFS MFT Advanced Forensic Analysis: https://www.deaddisk.com/posts/ntfs-mft-advanced-forensic-analysis-guide/ - MFT Slack Space Forensic Value: https://www.sygnia.co/blog/the-forensic-value-of-mft-slack-space/ - MFTECmd Documentation: https://ericzimmerman.github.io/ - SANS FOR500: Windows Forensic Analysis ## Example Output ```text $ MFTECmd.exe -f "C:\Evidence\$MFT" --csv /analysis/mft_output MFTECmd v1.2.2 - MFT Parser ============================== Input: C:\Evidence\$MFT (Size: 384 MB) Total MFT Entries: 395,264 Parsing MFT entries... Done (12.4 seconds) --- Deleted File Recovery Summary --- Total Entries: 395,264 Active Files: 245,832 Deleted Files: 149,432 Recoverable: 87,234 (resident data or clusters not reallocated) Partially Recoverable: 31,456 (some clusters overwritten) Unrecoverable: 30,742 (all clusters reallocated) --- Recently Deleted Files (Incident Window: 2024-01-15 to 2024-01-18) --- MFT Entry | Filename | Path | Size | Deleted (UTC) | Recoverable ----------|-----------------------------------|------------------------------------|-----------|-----------------------|------------ 148923 | exfil_tool.exe | C:\ProgramData\Updates\ | 1,258,496 | 2024-01-17 02:45:12 | YES 148924 | exfil_tool.log | C:\ProgramData\Updates\ | 45,312 | 2024-01-17 02:45:14 | YES 149001 | passwords.txt | C:\Users\jsmith\Desktop\ | 2,048 | 2024-01-17 02:50:33 | YES 149150 | scan_results.csv | C:\Users\jsmith\AppData\Local\Temp | 892,416 | 2024-01-17 03:00:01 | PARTIAL 149200 | mimikatz.exe | C:\Windows\Temp\ | 1,250,816 | 2024-01-18 01:15:22 | YES 149201 | sekurlsa.log | C:\Windows\Temp\ | 32,768 | 2024-01-18 01:15:25 | YES 149302 | .bash_history | C:\Users\jsmith\ | 4,096 | 2024-01-18 03:00:00 | NO 149400 | ClearEventLogs.ps1 | C:\Windows\Temp\ | 1,536 | 2024-01-18 03:01:12 | YES --- $STANDARD_INFORMATION vs $FILE_NAME Timestamp Analysis (Timestomping Detection) --- MFT Entry | Filename | $SI Created | $FN Created | Delta | Verdict ----------|---------------------|----------------------|----------------------|-----------|---------- 148923 | exfil_tool.exe | 2023-06-15 10:00:00 | 2024-01-15 14:34:02 | -214 days | TIMESTOMPED 149200 | mimikatz.exe | 2022-01-01 00:00:00 | 2024-01-16 02:30:15 | -745 days | TIMESTOMPED Recovered files exported to: /analysis/mft_output/recovered/ Full CSV report: /analysis/mft_output/mft_analysis.csv (395,264 rows) Timeline CSV: /analysis/mft_output/mft_timeline.csv ``` --- Source attribution: hironow Original project: https://github.com/hironow/cyber/blob/20efb3a6a2a9e7ebbde38ed32325979866110540/.agents/skills/analyzing-mft-for-deleted-file-recovery/SKILL.md License: Apache-2.0 License information: https://www.apache.org/licenses/LICENSE-2.0 Original upstream instructions; downloaded from Mega AI Hub. ## Upstream license notice Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to the Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by the Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding any notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. Please do not remove or change the license header comment from a contributed file except when necessary. Copyright 2026 mukul975 Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. # Mega AI Hub resource metadata Creator / publisher: hironow Original project: https://github.com/hironow/cyber/blob/20efb3a6a2a9e7ebbde38ed32325979866110540/.agents/skills/analyzing-mft-for-deleted-file-recovery/SKILL.md Attribution basis: Source repository record Fields of work: Content & Media, Data & Analytics Roles: Data Analyst, Technical Writer Specialties: API, Testing Tools: Mftecmd, Analyzemft, Timeline Explorer, Ftk Imager Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: e15d8c57094f23f892817e4a58a9b483e7b9f2aa95fd7a88ae771a1308c199eb