An independent offensive research initiative.
Founder-led. Depth over volume. Every writeup ships with the code, the primitives, and the reproducer.
Make offensive security research a first-class engineering discipline — reproducible, auditable, and freely available to the people who defend the systems we all rely on.
A research archive where every claim ships with the code, the primitives, and a working reproducer.
Windows internals, exploit development, reverse engineering, and the tooling around them.
A public advisory feed, an open tooling collection, and a growing track of Windows internals and exploit-development research.
Depth over volume.
A single reproducible writeup with primitives and a working PoC is worth ten survey posts. I invest in the plumbing — symbol servers, coverage, tooling — to iterate faster on the interesting parts.
If it can be public, it will be. PoCs are published after coordinated disclosure, and fixes get upstreamed where possible.
Advisories and writeups are public, not gated behind a newsletter. No paywalls, no lead-capture.
Every writeup ends with something you can read, run, and modify. That's the deliverable.
BeaconBytes is an independent offensive security research initiative, founder-led and focused on Windows internals, exploit development, and reverse engineering. It started as a place to publish the writeups and tools I wished existed when I began. The goal is simple: build practical, reproducible security research in public, and grow the lab alongside the work.
Join the community
BeaconBytes is built in the open. If you're into offensive security research, exploit development, or reverse engineering — or you just want to follow along as tools and writeups ship — come hang out on Discord.
Researchers, learners, and lurkers all welcome.