Overview
The challenge provides an archive at hxxp://54[.]72[.]82[.]22:8500/downloads/field-notes.zip. The objective: “Identify the documented departure and return its collection receipt.” The receipt format is specified in submission.txt.
Prerequisites / Setup
wget/curl,unzip,sha256sum- The archive contains:
camera-metadata.json,civic-directory.json,pier-note.txt,submission.txt,tide-station.csv,voyages.json
Recon
Step 1 — Download and extract the field notes
Goal: Obtain the puzzle files.
wget "hxxp://54[.]72[.]82[.]22:8500/downloads/field-notes.zip"
unzip field-notes.zip
Archive contents: camera-metadata.json, civic-directory.json, pier-note.txt, submission.txt, tide-station.csv, voyages.json.
Step 2 — Examine the camera metadata
Goal: Extract vessel, bearing, time, and offset.
camera-metadata.json:
{
"local_time": "2026-06-04T21:00:00",
"utc_offset": "+02:00",
"compass_degrees": 11,
"vessel_mark": "vessel-3"
}
- Local time:
21:00 - UTC offset:
+02:00 - Compass bearing:
11° - Vessel:
vessel-3
Convert local time to UTC:
21:00 − 02:00 = 19:00 UTC
So UTC time = 19:00Z.
Step 3 — Examine the pier note
Goal: Extract the tide measurement.
pier-note.txt:
At the exposure, the gauge was 219 cm. Clock and compass had both been serviced that morning.
Tide = 219 cm.
Three identifying pieces:
Vessel: vessel-3
Bearing: 11°
Tide: 219 cm
UTC: 19:00Z
Enumeration
Step 4 — Find the matching voyage
Goal: Search voyages.json for the combination of vessel, tide, bearing, and UTC hour.
Match on vessel-3, tide_cm = 219, bearing = 11, utc_hour = 19:
{
"ref": "d0b36031a079e290",
"vessel": "vessel-3",
"station": "5255073ff2",
"utc_hour": 19,
"tide_cm": 219,
"bearing": 11
}
This identifies the documented departure:
voyage_ref = d0b36031a079e290station_ref = 5255073ff2UTC_time = 19:00Z
Step 5 — Determine the receipt format
Goal: Read the exact hash formula from submission.txt.
submission.txt:
Receipt format: SHA256(voyage_ref|station_ref|UTC_time), lowercase hex. UTC_time uses HH:MMZ.
String to hash:
d0b36031a079e290|5255073ff2|19:00Z
printf '%s' 'd0b36031a079e290|5255073ff2|19:00Z' | sha256sum
a037d4fd49143de5d5abbe38b536198ba777879089dd3b44dec83ac1b962c845
Exploitation
Step 6 — Submit the receipt
Goal: Submit the SHA-256 receipt through the Collection receipt form on the challenge page.
The challenge accepts the submission and returns:
{
"message": "safctf{REDACTED}",
"ok": true
}
Flag
safctf{REDACTED}
Returned after submitting receipt a037d4fd49143de5d5abbe38b536198ba777879089dd3b44dec83ac1b962c845.
Mitigations
- Apply proper input validation and sanitization for all user-supplied data.
- Use parameterized queries or prepared statements for database operations.
- Implement proper authentication and authorization checks.
- Follow the principle of least privilege for all application components.
Lessons / Takeaways
- Combine independent clues (time conversion, vessel, bearing, tide) to identify a single record rather than guessing.
- Convert local time to UTC using the stated offset before matching.
- Read the required output format (
submission.txt) before computing the answer.
Techniques
- OSINT
References
n/a — all sources were the challenge-provided field-notes archive.

