★ ☆ ★   W E L C O M E   T O   M Y   H O M E P A G E   ★ ☆ ★

NULLRAKE'S PAGE

last updated: NOV 19 2026  ·  hosted on a Pentium 133  ·  28.8k friendly
  *** WELCOME 2 MY HOMEPAGE *** IF U R SEEING THIS, THE PAGE LOADED OK *** DO NOT ENTER KEYS U DONT OWN *** SIGN MY GUESTBOOK *** BEST VIEWED IN NETSCAPE NAVIGATOR 4.0 @ 800x600 *** TELL UR FRIENDS *** THIS SITE IS ALWAYS UNDER CONSTRUCTION ***
AI CONTROLLED  —  point an agent at the file and say go

This is the feature. REE is built to be driven by an AI agent, not clicked by a human. Unpack it, point an agent at the folder, say go. It does the rest and hands back the file.

> this exe rejects my licence key.
> patch a copy, prove it stopped firing, show me the diff.
WHAT THE AGENT DOES WITH THAT
  1. Reads AGENTS.md — the full manual ships inside the bundle, so the agent teaches itself. guidance lets it pull one section at a time instead of the whole file.
  2. Calls route to decide what the file actually is: native PE, packed PE, .NET, Electron ASAR, JAR, APK, PyInstaller, ELF.
  3. Runs that playbook: triage → strings tagged by proximity to the licence check → disassembler-verified branch candidates → patched copy → byte diff.
  4. Stops only when the patch is proven, not when a report is written.
WHY IT ACTUALLY WORKS AS AN AGENT TOOL
  • JSON in, JSON out. Every call returns the next call with the real paths already filled in, so the agent chains steps without a human relaying anything.
  • No API key, no service. It runs on your machine. The agent never sends the binary anywhere.
  • The deliverable is the artifact. The patched copy plus the diff that proves what changed — not a summary of what it would change.
  • Works with any agent that has a shell — Claude Code, Codex, or a script you wrote yourself.
./install.sh
python3 ree_ai.py route '{"path":"/abs/target.exe"}'
python3 ree_ai.py workflow '{"id":"crack_licence","path":"/abs/target.exe","failure":"Invalid licence key"}'
python3 ree_ai.py verify '{"orig":"/abs/target.exe","new":"/abs/target_patched.exe"}'
Prefer a mouse? The cockpit does the same job by hand — that is what the screenshots are. The agent is just the version that does not need you in the room.
REE — reverse engineering bundle v1.0.6

AI-controlled reverse engineering toolkit. Point an AI agent at the folder, say go, and it does the work: route the file, triage it, tag the strings beside the licence check, disassemble the branch candidates, write the patched copy and diff the bytes to prove what changed. Ships the GUI cockpit, a JSON-in/JSON-out command line, and an operating manual the agent reads for itself. Static triage, source recovery and an isolation harness included; Windows, Linux and macOS installers in the zip. v1.0.5 points the agent one-pager at this page and at /REE/latest, which always resolves to the current build.

REE-bundle-v1.0.6.zip
10.9 MB · published 2026-11-19
[ ▼ DOWNLOAD ]
DOWNLOADS SERVED
000000
every build, summed
SHA256 — CHECK THIS BEFORE YOU RUN IT
b69521c3722fdd0bd33b042f794abd2ee6311d13bdd32c51ae2c901f737b134b
https://nullrake.pages.dev/poc/ree/REE-bundle-v1.0.6.zip
shipping software yourself?
This tool is the offence. The defence is documented in the same place: how to protect your software from REE. Five pages, ranked by what actually stops a licence patch and what is theatre.
[ ▼ HOW TO PROTECT ]
what this is not
  • Not a crack. A proof-of-concept build from a scoped engagement, published as evidence the work happened.
  • No client name, no contract number, no third-party vendor named on this page.
  • Nothing here comes with a licence to redistribute. If you did not commission the test, you may read about it, not rebrand it.
[ CASES ] [ CONTACT ]

✉ tip me (crypto) · notes & messages (SimpleX) · contact me · telegram bot · services
NETSCAPE NOW! IE 3.0 800x600 HTML 3.2
© 1997-2026 nullrake // this page is best viewed on a CRT // sign my guestbook