Going beneath NTFS: USN Journal, dfir_NTFS, and artefact-driven investigations

Hackers thought they cleaned up, but Windows kept the receipts and commenters are yelling

TLDR: The big news is that Windows can keep several hidden records of file activity, so changing dates or deleting tools may not really erase what happened. The lone community reaction is blunt and dramatic: this is essential knowledge, and commenters are treating ignorance like the real scandal.

This piece lands like a crime show plot twist: even if a sneaky intruder changes file dates, deletes tools, and wipes obvious traces, Windows may still be quietly keeping multiple backup clues. The article’s big reveal is that the system stores a file’s history in several separate places, so scrubbing one trail often leaves two more behind. In plain English: the burglar may have wiped the fingerprints off the door, but forgot the security camera, the neighbor’s Ring, and the receipt in their own pocket.

And the comment section? Instantly in full "everyone should know this" mode. The loudest reaction came from user fuzzfactor, who basically declared this required knowledge for anyone touching a computer, whether they use Windows or not. That gave the whole discussion a deliciously stern, tech-parent energy: less "wow, neat article" and more "how were you people walking around not knowing this already?"

The drama here is less a flame war and more a collective panic-laugh over how hard it really is to erase your tracks. The hottest takeaway from the crowd is that attackers who think they’re being clever by changing timestamps are apparently playing checkers while the file system is playing chess. There’s also a dark little joke running under the whole thing: every time someone thinks they’ve done the digital equivalent of cleaning the scene, Windows pops up like "actually, I wrote that down." For defenders and investigators, that’s great news. For anyone hoping a quick cleanup script makes them invisible? The comments are basically one long siren.

Key Points

  • The article says NTFS preserves multiple forensic artefacts, including the MFT, USN Journal, and $LogFile, that record different dimensions of file system activity.
  • NTFS stores two separate timestamp sets per file in $STANDARD_INFORMATION and $FILE_NAME, and standard Win32 APIs can modify one without changing the other.
  • A mismatch where $STANDARD_INFORMATION creation time predates $FILE_NAME creation time is presented as direct evidence of timestamp manipulation.
  • The USN Journal records sequential file system change events, survives file deletion, and typically retains about 20 days of activity on an active volume.
  • The article presents dfir_ntfs and MFTECmd as complementary tools and says file carving is most useful when MFT metadata is damaged or missing.

Hottest takes

"advanced stuff that nobody should be unaware of" — fuzzfactor
"whether they use Windows or not" — fuzzfactor
"nobody should be unaware" — fuzzfactor
Made with <3 by @siedrix and @shesho from CDMX. Powered by Forge&Hive.