I publish REE, and I get paid to break licence checks before your customers do. This folder
is the other half of that: what REE actually does, in the order it does it, and which fixes
make its output worthless.
!! THE ONE THING TO UNDERSTAND !!
A check that runs on the customer's machine is a speed bump, not a lock.
REE reads your binary, finds the branch that decides "licensed", and flips two bytes.
Every control in this folder assumes that already happened. The only question that matters
is: when the client lies, does your server believe it?
WHAT REE DOES, IN ORDER
- Triage. File type, packer signatures (UPX, VMProtect, Themida), section map. A packed target changes the attack, not the outcome.
- Strings, tagged. Anything that reads like
AUTH, LICENS, INVALID, EXPIRED, TRIAL gets collected, because those literals sit next to the decision. - Branch candidates. It disassembles the region around each tagged string and keeps conditional jumps the disassembler confirms. No guessing from raw offsets.
- Patch. Two bytes on the conditional jump, or a NOP run. Same file length, so nothing about the container changes.
- Verify. Byte-level diff of the original against the patched copy, so the change is evidence rather than a claim.
- Source recovery. .NET, Electron ASAR, JAR, APK and PyInstaller bundles get read back to something close to source. Native code gets decompiled functions, not a rebuild.
- Dynamic confirm. The patched copy runs in an isolated guest with no network, so behaviour is observed, not inferred.
THE FIVE PAGES