Ground rules
- Always work on a copy. Keep the original image (and its SHA-256) untouched, and explore a duplicate. If you break the copy, just make another.
- Read-only wherever possible. Mounting an image read-write lets your operating system quietly change it.
- Recover to a different place. Save recovered files to another folder or disk, never back into the image.
- Be respectful. These drives belonged to real people. Treat what you find with care.
Mounting an image read-only
Mounting lets you browse the files in an image like a normal disk. On Linux:
sudo losetup --find --show --read-only --partscan drive.img # prints e.g. /dev/loop0
lsblk /dev/loop0 # shows partitions such as loop0p1
sudo mkdir -p /mnt/drive
sudo mount -o ro /dev/loop0p1 /mnt/drive
When you're done: sudo umount /mnt/drive and sudo losetup -d /dev/loop0. On macOS:
hdiutil attach -readonly -imagekey diskimage-class=CRawDiskImage drive.img
macOS can read FAT and (read-only) NTFS natively, but not many older filesystems. On Windows, FTK Imager's File → Image Mounting or the free Arsenal Image Mounter can mount raw images read-only. Mounting only shows files that still exist; for deleted files, read on.
TestDisk and PhotoRec
Both are free, run on Windows, macOS and Linux, and work directly on image files. Run them against your copy:
testdisk drive-copy.img
photorec drive-copy.img
- TestDisk analyses the partition table and filesystems. It can find lost partitions and, for FAT, NTFS and ext filesystems, list and copy out deleted files that are still referenced. Choose Advanced → Undelete or List to browse, and copy files out. Avoid Write, which changes the partition table.
- PhotoRec ignores the filesystem and carves files by recognising their headers (JPEG, PDF, DOC, ZIP and hundreds more) in the raw data. It finds files even after formatting, but loses names and folders. Tell it to save into an empty folder outside the image.
The Sleuth Kit and Autopsy
The Sleuth Kit is a set of command-line forensic tools; Autopsy is a free graphical program built on it, available for Windows, Linux and macOS. In Autopsy, create a case, add your image as a Disk Image data source and let it analyse: you'll get a file tree including deleted files, a timeline, keyword search, file type views and more.
A few Sleuth Kit commands to try:
mmls drive.img # partition layout and start offsets (in sectors)
fsstat -o 63 drive.img # filesystem details for the partition starting at sector 63
fls -r -o 63 drive.img # list files recursively; deleted ones are marked with *
icat -o 63 drive.img 1234 > out # extract the file with inode/entry number 1234
Replace 63 with the start sector mmls shows for your partition.
Hex editors
A hex editor shows the raw bytes of the image. It's how you look at boot sectors, slack space and file
fragments that no tool understands. Good free options are HxD (Windows),
ImHex (cross-platform) and xxd or hexdump on the command line:
xxd -s 0 -l 512 drive.img # the first sector: the MBR, ending in 55 AA
strings -n 8 drive.img | less # readable text anywhere in the image
Open images read-only in your hex editor (HxD and ImHex both have an option) so a stray keypress can't change anything.
CTF challenges on DriveArchive
Some drives in the archive carry challenges: something to find in the image, written by the contributor or a reviewer. It might be a recovered password, the text of a deleted letter, the name of a program that was once installed or the hash of a carved file. Each challenge is worth points, and there's a leaderboard.
- Find a drive with challenges and download it (it costs download credit like any other drive).
- Read the challenge on the drive page carefully: it says what form the answer takes.
- Explore the image with the tools above until you find it.
- Submit your answer on the drive page. Answers ignore upper/lower case and extra spaces, so
Hunter2andhunter2count the same.
Please don't share answers or post step-by-step solutions; it spoils the challenge for everyone else. Talking about tools and general techniques is fine.
If you find personal data
Reviewers check drives before publishing, but things can slip through. If you come across someone's personal information (identity documents, medical or financial records, private photos or correspondence) in a drive on the archive:
- Don't copy, post or spread it, and don't use it as a CTF answer.
- Report it with the drive and, if you can, the file path or offset, so reviewers can deal with it.
- Delete any copies you made of the personal data.