Reverse engineering with REA, one real workflow at a time.

Install REA with npx rea-agents setup, connect Claude Code, Cursor or Codex over MCP, check providers and capabilities, and run your first analysis.

Confirm you install the genuine REA: the official GitHub repo and npm package, npm view checks, provenance via npm audit signatures, and where to report fakes.

Check whether your own ELF, PE and Mach-O builds have NX, PIE, full RELRO, stack canaries, ASLR, CFG and hardened runtime, with real tool output and flags.

Tell whether a Windows EXE or DLL is x86, x64 or ARM64 without running it, and why a .NET AnyCPU assembly looks 32-bit until you read its CLI flags.

Identify an ELF, PE or Mach-O file in the browser: architecture, sections with entropy, imports, exports and strings, and whether the binary is stripped.

Use REA with free Ghidra to analyze a native binary you compiled: analyze, search strings, decompile, follow xrefs and trace a feature from CLI or AI agent.

Tune REA's headless Ghidra provider: stripped binaries, language overrides, analysis seeds, MIPS limits, startup timeouts, JVM heap and snapshot reuse.

Connect IDA Pro to Claude Code and Codex through REA 6.4.0 and ida-pro-mcp: attached and headless modes, the 1.4.0 vs 2.0.0 limit, prompts and fixes.

Check if a Mac app or dylib is a universal binary, list its arm64 and x86_64 slices, and compare minimum macOS, signature and dependencies per slice, on any OS.

Analyze a macOS .app with REA: map bundle anatomy, read Info.plist, Mach-O and signing metadata, trace dylib loads, demangle Swift, decode NIBs, then decompile.

Analyze a Windows EXE or DLL you built with REA, Ghidra and an AI agent: exports, imports, PE resources, strings, decompilation and Windows host limits.

Check what your npm package or web build exposes through source maps: npm pack --dry-run, a local map viewer, a REA audit of the live site, and build fixes.

Turn a production error like app.js:1:68 into the original file, line and name: build hidden source maps, map each frame locally, and automate it with REA.

Analyze an Electron app with REA: read app.asar, map modules and imports, use source maps, follow preload and IPC channels, and hand native add-ons to Ghidra.

Turn a minified webpack bundle back into readable modules with REA: source maps, chunk recovery, Wakaru unpacking, data-flow tracing and source checks.

Find app.asar on Windows, macOS or Linux, unpack it in your browser or with npx @electron/asar, and read package.json, main, preload and IPC channels first.

Convert an AAB to a universal APK with bundletool, then unpack it with REA 6.4.0: inventory every entry, extract assets safely, decode resources, find scripts.

Analyze an open-source Android APK with REA: decompile classes with JADX, decode resources with Apktool, pull packages over ADB, identify Flutter Dart builds.

Prepare Android developer verification: get your package name and signing certificate SHA-256 from your APK or AAB, pick the right key, and see what applies.

Fix 'App not installed as app isn't compatible with your phone' in your APK: get the real INSTALL_FAILED code, then check targetSdk, native ABIs and minSdk.

Fix 'App not installed as package conflicts with an existing package' in your app: compare signing certificate SHA-256, find the installed copy, keep your key.

Check whether your APK or AAB is 16 KB page size compatible: ELF segment alignment, ZIP alignment of .so files, and 64-bit libraries, in the browser or with zipalign.

Reproduce a crash in your own Android app, read FATAL EXCEPTION from the crash buffer, find the native tombstone in a bugreport, and map frames to source with REA.

Set up headless JADX as an MCP backend for Claude Code and Codex with REA 6.4.0: JDK 17+, jadx-headless-mcp 0.7.1, env config, prompts and common errors.

Build a practice challenge, then solve it with REA and a coding agent: find the check, extract the table, write a solver and prove the flag with Evidence IDs.

Export a HAR from Chrome, Edge, Firefox or Safari, read what is inside, group requests by endpoint, find slow calls and errors, and redact it before sharing.

Use REA to capture a page, take screenshots, observe network requests, read saved HAR captures, and find the front-end code that makes each API call.

Convert WASM to WAT and read a WebAssembly module's imports, exports, memory, functions and custom sections in your browser, then confirm the result with wabt.

What WebMCP is, how a page registers tools for browser AI agents, and how to list them with REA 6.4.0 without calling them, plus a diff that catches new tools.

Inspect .NET assemblies with REA without running them: identify the PE/CLI artifact, read metadata and CIL, compare members across builds, and handle NativeAOT.

Find out which .NET version a DLL targets, its assembly and file version, and the assemblies it references, without Visual Studio: in the browser or with REA.

Patch diffing with REA 6.4.0 and an AI agent: compare_functions on two zlib builds, read changed vs unknown dimensions, and tie every claim to Evidence.

What npx rea-agents setup writes for Claude Code: the MCP entry and the bundled REA skill. Plus prompt templates and checks that REA was really used.

Use REA Evidence to compare two versions of an open-source app: save snapshots, validate and export bundles, run compare, and import historical source.

Unpack an OpenWrt image with REA's Binwalk and Unblob integration, then hand an extracted ELF to Ghidra. Covers Linux x64 limits, budgets and handoffs.

Use REA's inspect-evm-interface (bundled EVMole 0.9.3) to infer function selectors, argument types and mutability from EVM bytecode offline, then verify them.

A sourced comparison of REA with GhidraMCP, ida-pro-mcp, r2mcp and Binary Ninja MCP: coverage, backends, install, licensing and best-fit use, as of 2026-10.