Build a connected evidence trail
Distribute clues across package-manager logs, shell history, and the systemd journal. These sources establish the sequence of events around the package installation.
Digital forensics · BeeCTF / 2026
A forensic challenge built around a compromised Arch Linux package. Players reconstruct what happened from evidence left across the system.
Authored the scenario, forensic evidence trail, and reference writeup for BeeCTF.
The challenge models a malicious AUR package and asks players to connect artifacts rather than recover a flag from a single file. It was written as a simulated investigation for BeeCTF 2026.
Distribute clues across package-manager logs, shell history, and the systemd journal. These sources establish the sequence of events around the package installation.
Use ELF analysis and extended file attributes to continue the investigation beyond the logs and recover the encrypted flag.
Write a reference solution covering both a command-line investigation using WSL2 and an alternative GUI workflow using FTK Imager.
Delivered a digital forensics challenge and its reference writeup for BeeCTF. The scenario is a simulation, not a report of an incident on a production system.
A CTF scenario has a deliberately constructed evidence trail and a known answer. Real investigations may have missing logs, uncertain timelines, and incomplete evidence.
Want to discuss this project?
Email me