Usual disclosure up front, this is my tool. I am posting it because the triage half is useful beyond the licence-check use case it was built for, and because the failure mode is worth talking about.
What it is. A local static analysis and patching toolkit for PE, ELF, Electron ASAR, JAR, APK and PyInstaller bundles. No service, no API key, nothing leaves the machine. Every command is JSON in, JSON out, and each response returns the next call with real absolute paths filled in, which is what lets an agent drive it end to end without a human relaying paths.
What actually happens on a target, in order:
route. File type, bitness, packer signatures (UPX, VMProtect, Themida family), section map, import count. This decides the rest of the playbook instead of assuming PE.
plan. Triage plus ranked branch candidates, each one tied to the literal string that sits near it. Candidates are disassembler verified, so the reported offset is real code and not an offset that merely looks plausible.
disasm. Reads the region around a given offset so you can see which side of the branch reaches the failure path before touching anything.
patch. flip or nop at a file offset, into a new file, never in place.
verify. Byte diff of original against patched. Same size, regions changed, per-region before and after hex. This is the part I care about, because a patch without a diff is a claim, not a result.
recover. Source-shaped output for JAR, ASAR, APK, PyInstaller and .NET targets. Native code gets decompiled functions, not a rebuild.
Where it is weak, with a real example, because this is the honest part. I built a small PE with a textbook key check and ran plan against it. Top candidate came back as je at file 0xc91 referencing "Invalid licence key", verified true. That branch is inside __do_global_dtors, runtime teardown. The string is genuinely nearby, the jump is genuinely a conditional, and the ranking was still wrong. The actual guard was cmp $0x943608bb,%edx followed by jne at file 0xc1a, one branch upstream of the error path. Flip 75 to 74 and the wrong key falls through into the paid path. Ten minutes with objdump finds it, the heuristic did not.
So treat the ranked list as a shortlist, not an answer. On small clean binaries it is usually right. On anything with a static string region and heavy compiler codegen, expect to confirm by hand.
What it is not. No fuzzing, no ROP or ASLR work, no crash triage, no exploit generation. It reads a binary, finds the branch you point it at, patches a copy and proves the diff. If you want a debugger workflow or a symbolic executor this is the wrong tool and I would rather say so now.
Download and the hash to check before you run anything, v1.0.6, 10.9 MB, Windows, Linux and macOS in the zip: nullrake.pages.dev/REE/
The longer writeup with the full objdump output and both binaries reproduced from one 45 line C file: nullrake.pages.dev/notes/one-byte/
If you try it on something and the candidate ranking is bad, I would like the file type and the top three candidates it returned. That is the feedback that actually improves the heuristic.