First look # This challenge shipped a bzImage, an initramfs.cpio.gz, and a remote VM that dropped into a BusyBox shell. That immediately made me think “driver challenge,” so I unpacked the initramfs before spending time on the remote instance.
First look # requiem is a stripped Rust ELF, which usually means a lot of disassembly noise before you get to the part that matters.
First impression # forge looked much worse than it really was.
First look # This one came with a very on-theme setup: a tiny CHALL.EXE DOS program and a floppy image containing the same executable. A quick strings pass already told me it was a flag checker:
Status # This page was originally just a template, and I do not have enough real solve artifacts in the repo to turn it into a proper writeup without inventing details.
Setup # The challenge came with a Python-based ><> (Fish) interpreter and a one-line Fish program that checked the input against one huge constant.
ReezS # First wrong turn # My first read on this binary was completely wrong. It looked like a normal flag checker, so I did what I usually do for that kind of challenge: identify the comparison logic, lift the constants, and script the inverse.
This set had two Android reversing challenges. Both of them became much easier once I stopped staring at the default UI and followed the data that the APK already exposed.
These are cleaned-up contest notes rather than polished full writeups. Buzzing has a complete solve path, but Checker and Dutchman_app are intentionally kept as partial notes because the missing final artifacts are not preserved in this repo. I would rather leave those gaps visible than pretend I remember more than I actually do.