SCCDU // EXERCISE 03 ← back to mission list

Inspect the File

A printed photo was found on Alex's desk (see Exercise 01). The original digital copy is on file with IT, along with a recorded checksum used to confirm files haven't been altered. Your job: confirm whether the copy you've been given still matches what's on record — and if it doesn't, work out why. This is a basic introduction to digital forensics and file integrity checking.

// STEP 1 — DOWNLOAD THE EVIDENCE COPY

Download the file below. It's a normal, safe photo.

↓ Download evidence_photo_04.jpg
IT ASSET REGISTER — SHA256 ON FILE: a3f3998db07ad68cec6b3d60944cecca1007305ede37bc3b2bb8f8ddc340bfd3

// STEP 2 — VERIFY THE FILE'S CHECKSUM

A checksum (or "hash") is a short fingerprint calculated from every byte in a file. Change even one byte, and the checksum comes out completely different. Use the tool below to calculate the SHA-256 checksum of the file you just downloaded, right in your browser — nothing is uploaded anywhere.

CALCULATED SHA256:
RECORDED SHA256: a3f3998db07ad68cec6b3d60944cecca1007305ede37bc3b2bb8f8ddc340bfd3

// STEP 4 — SUBMIT THE FLAG

Once you find the hidden message, type the flag exactly as written (including the curly brackets) into the box below.

Why does this work? (click to expand)

A JPEG image file has a defined ending point in its binary data (a marker called "End Of Image"). Programs that open photos stop reading at that point, so they never notice if extra data has been added after it — the picture still looks completely normal. But because a checksum is calculated from every single byte in the file, adding anything at all — even a few lines of hidden text — changes the checksum completely. That mismatch is exactly how real investigators first notice a file has been tampered with, often before they even know what was changed.