Two Things, One Package
The RE Toolbox is a manual workbench built into FrankenCoder — five tabs you operate yourself: Hex Editor, Disassembly, Binary Analysis, Decompiler, and Debugger. Open a binary, dig through it, understand what it does. Audit your own code before you ship. Inspect a dependency. Triage a suspicious file before you run it. No external software required.
The RE Agent is a specialist AI agent with direct access to all 77+ RE tools. It doesn’t read files passively — it calls the disassembler, decompiler, and hex editor the same way you would, navigating to addresses, reading function output, renaming variables, and building its analysis step by step. And the UI keeps up: when the agent loads a file in the hex editor, the hex editor opens and shows the binary. When it navigates to an address or edits a byte, you see it happen. You’re not watching a chat log — you’re watching the tools move.
The Run — Gemma 4 31B Cracks a 3-Stage Crackme
The target was franken_crackme.exe — a three-stage crackme built specifically to test RE capabilities. The agent was given the binary and a prompt. No hints. No walkthrough. The model was Gemma 4 31B Q8, running entirely locally. No API key. No cloud call. No usage bill.
16 minutes wall clock. The video above is compressed to 1m35s.
Honest note on that 16 minutes: The file was purpose-built to be analyzed — it’s a test crackme, not a hardened production binary. The model was running on an RTX Pro 6000. I recorded exactly one demo. Run it again and it might take 5 minutes, or it might take 30. The complexity of the target, the model you choose, and your hardware all play a role.
We’re not promising any binary cracks in 16 minutes. We’re showing you that a local model with the right tools can do serious RE work autonomously. Your mileage will vary — from minutes to the heat death of the universe.
Everything Ships With FrankenCoder
The entire workbench is built in. Open the toolbox from the sidebar, point it at a binary, and start working — or hand it to the RE Agent and let it work while you do something else. No external software to install, license, or configure.
Local model, zero cloud. No API key, no usage bill, no data leaving your machine.
Or use a cloud model when you need more reasoning depth. Your choice per session, no lock-in.
16 minutes wall clock to fully analyze a three-stage binary. The agent worked autonomously from first prompt to final result.
The Decompilers
Three decompilers, built from scratch in TypeScript. They cover the languages and architectures most people actually need:
- x86/x64 native — C, C++, Rust, Go. 64-bit, ARM, and ARM64.
- JVM — Java.
.classand.jarto readable Java source. - .NET — C# with async/await, generics, LINQ, records, and nullable types.
Honest note on the decompilers: They work. They are also early stage and a work in progress. We’ve benchmarked them and seen 90%+ recompilable source rates — meaning the decompiled output compiled back successfully — but the benchmarks were run by agents, and agents lie. Take that number as directionally encouraging, not a guarantee.
What we can say honestly: they produce useful output on real binaries today, the RE Agent can work with what they produce, and they are actively being improved. If you hit a binary that trips them up, that’s expected — it’s a hard problem and we’re not done yet.
Why It Exists
I do reverse engineering work. That’s not a feature I added for the market — it’s a tool I built because I needed it. The RE Agent exists because switching between a hex editor, a disassembler, a decompiler, and an AI chat window for every question is friction. Having the agent sit inside the same environment as the tools, with direct access to call them, removes that friction entirely.
You get a specialist that already knows how to navigate a binary — because it has the same tools you do.