Read an NTFS $MFT, and catch the dates that were rewritten MFT
Every NTFS file keeps two sets of dates: the ones Windows shows and a program can change, and the ones the kernel writes and almost nothing exposes. When they disagree, the file was timestomped.
1. The table
A $MFT extracted from an NTFS volume. It is read here and never written to, and nothing is uploaded.
No file open yet.
2. What it describes
How it works
Reading the two sets of dates
The columns show the $STANDARD_INFORMATION times, the ones Explorer shows and a program can set. A highlighted row is one where those disagree with the $FILE_NAME times the kernel wrote - the shown creation date is earlier than the name existed, or its sub-second precision was wiped. That is the shape of timestomping. It is a lead, not a verdict: corroborate against the change journal, the registry and the event logs, and remember a wrong clock skews every date together. Hash the copy with CHECKSUM and note its source with CHAIN first.
The guide: How to tell if a file’s dates were changed
Questions people ask about MFT
What is the $MFT and how do I get it?
The master file table is NTFS’s index of every file on a volume, one 1024-byte record each. Extract it from the volume root with a forensic imager (FTK Imager, and others, export \$MFT), and open that file here. It is often hundreds of megabytes; this reads what the browser can hold and tells you if it stopped.
How does it catch timestomping?
Each record carries timestamps in two attributes. $STANDARD_INFORMATION holds the dates Explorer shows, and a program can set them to anything. $FILE_NAME holds dates the kernel writes when the name is created, and ordinary tools cannot change them. When the shown creation date is earlier than the name-record date, the file claims to predate its own name - it was backdated. And the common tools set a round second, so a shown time with no sub-second part beside a precise name-record time is the other tell.
Does it show deleted files?
Yes. A record marked not-in-use still describes a file that was there until its record was reused, so deleted entries are read and can be shown or hidden. What it cannot do is recover the file’s contents; it reads the table, not the data.
Is it certain proof?
No single artefact is. A backdated timestamp is strong evidence of tampering but not of who or why, a wrong system clock skews everything the same way, and some legitimate operations touch these fields. Treat a suspect as a lead to corroborate against the journal ($LogFile, $UsnJrnl), the registry and the event logs.
Does anything leave my machine?
No. The $MFT is parsed in this tab. Hash the copy with CHECKSUM and record where it came from with CHAIN if it may be relied on.
Doing this often? The Sovereign Console loads disk images and Windows artefacts into one case, and puts every timestamp on one timeline. On its own, US$2 a month; with everything else, US$5 a month or US$48 a year.