Lewis WangandClaude Opus 5.5 af0d69ee91 fix(har): keep Chromium DevTools captures that report an empty server address (#13027)
Chromium DevTools writes serverIPAddress from NetworkRequest.remoteAddress(),
which starts as "" and stays empty when a request has no remote endpoint,
such as a refused connection, an aborted request or an internal redirect.
har-schema requires an IPv4 or IPv6 value, so inspect_web_network_capture
refused the whole export at the first such entry.

For the declared WebInspector 537.36 profile, an empty serverIPAddress is
omitted from the validation copy only, as bracketed IPv6 already is. Reported
Evidence keeps the empty value, and the record gains a limitation that the
server address is unknown. Other producers' empty addresses still fail
validation.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-21 19:42:16 +01:00

English · 简体中文 · 繁體中文 · 日本語 · 한국어 · Türkçe · Русский · Tiếng Việt · ไทย · Deutsch · Español · Français · Українська · Polski · Português (Brasil) · العربية · فارسی · Bahasa Indonesia · Italiano · Ελληνικά · മലയാളം · Roman Urdu · Română · Български

REA: Reverse Engineer Anything

One MCP for reverse engineering across binaries, applications, and runtime behavior.

See a feature you like. Understand how it works, down to the binary level.

GitHub stars Monthly npm downloads MIT license Join the REA Discord Follow REA on X Supported platforms: macOS, Windows, and Linux skills.sh

Website · Guides · Showcases

Join the REA community on Discord

Quick start · Showcases · How REA works · What you can analyze · Build RL environments · FAQ · Documentation

npx rea-agents setup

Important

Get REA from morluto/rea, rea.tools, or the rea-agents npm package. Follow the installation and release links from these official sources. A similar repository name or copied README does not establish that a download is official.


REA launching its analysis bridge inside Hopper while inspecting a native binary



Discord
Join the Reverse Engineering Community

Discord · Q&A · Show and Tell


See a feature in an app that you want in your own product? Ask your agent to investigate it with REA. It can inspect the app without its source code, explain how the feature works, show the evidence, and build a version for your project.

REA connects your agent to tools for inspecting native binaries, JavaScript and Electron apps, .NET assemblies, and websites. You can also use the same tools from your terminal. Analysis runs locally, and results include the evidence and limitations behind each conclusion.

Setup registers REA with your agent and installs matching workflow instructions. Native analysis can use an existing Hopper, Ghidra, IDA or Kuna installation; setup can optionally install Hopper with approval. Static JavaScript analysis needs no native analysis engine.

Quick start

Get started at rea.tools for step-by-step instructions by operating system, agent, and analysis provider.

Connect your agent (MCP)

With Node.js and npm installed, run this from a trusted directory outside the project you plan to analyze.

npx rea-agents setup

Choose your agent, review and approve the setup plan, then restart your agent. Setup backs up existing configuration and adds REA's MCP connection and investigation skill. See the installation guide for supported clients, plugins, manual registration, and troubleshooting.

Try asking your agent:

Understand how search works in the Notes app, show me the evidence, and build a
similar feature for my project.

Replace Notes with your target app and the feature you want to understand.

Use REA from the terminal (CLI)

Inspect an extracted JavaScript/Electron app directory or ASAR:

npx -y rea-agents@latest analyze-javascript-application /absolute/path/to/app --json

The result includes modules, imports, Electron boundaries and their evidence. Replace the path with your target, such as "D:/apps/example" on Windows.

To install the rea command for regular use:

npm install --global rea-agents
rea --help

For native analysis, configure a provider first. The CLI and Evidence guide covers provider selection, native commands, snapshots, and scripting. For Linux prerequisites, see the installation guide.

Update REA

For a global npm or Bun installation, run the updater and follow its setup instructions.

rea update

If you use npx, refresh your agent setup with:

npx rea-agents@latest setup

Review the setup changes and restart your agent. See update and uninstall instructions for package runner options and troubleshooting.

Showcases

Illustrations of the DX-Ball sound-pan, Notion clipboard-bridge, and TH04 bullet-ring showcases

DX-Ball: reconstruct a sound-pan calculation

Recover a position-to-pan helper from x86 instructions and verify the C reconstruction against 3,205 original-x86 cases and all 63 compiled function bytes.

Read the case study · Reconstruction repository

Notion: trace the Electron clipboard bridge

Follow the renderer’s clipboard API through preload and IPC into the main process to see how Notion handles rich clipboard data.

Read the case study

TH04: recover a DOS bullet-ring calculation

Recover fixed and aimed angle calculations from the PC-98 game’s 16-bit instructions and compare the reconstructed C++ with historical compiler output.

Read the case study · Reconstruction repository

If you've used REA on something interesting, we'd love to see it. Share your case in an issue or a pull request, including the target, your question, how REA helped, and what you found.

How REA works

Your agent uses REA through MCP to inspect a target and trace the relevant code. It can use the evidence REA returns to ask follow-up questions, explain behavior, or build and test an implementation. The CLI uses the same workflows.

REA investigation flow: your agent asks about a local target, REA inspects and traces it using analysis tools, and the agent uses the returned code, references and unknowns to explain, implement and test.

Open the full-size figure.

What you can analyze

REA covers native binaries, JavaScript and Electron apps, websites, .NET assemblies, Android apps, firmware, and recorded runtime and network activity.

Supported targets and requirements

For native decompilation, choose a provider that supports your target format and host OS. See choosing a deep analysis provider.

Build RL environments

Build a local environment from a recorded web session or a Linux desktop app so an agent can practice a task and check its result. Build an RL environment with REA.

FAQ

Which agents can use REA?

Any agent that supports local MCP servers. Setup configures the supported agents; other clients can use manual MCP registration.

Do I need a native analysis engine?

Deep native analysis uses Hopper, Ghidra, IDA or Kuna, depending on the target and operation. Static JavaScript and .NET inspection work without a native analysis engine. Setup can install Hopper after approval; Ghidra, IDA and Kuna use your existing installations. See provider setup for the options and their supported targets.

Do I need to start Hopper first?

REA starts Hopper when an operation needs it. On macOS, a first-run dialog may ask you to choose demo mode or activate your license. Complete that prompt in the same user session before your first CLI/MCP operation or unattended job. Open Hopper manually if needed. See Hopper startup and troubleshooting.

What does installing the skill from skills.sh do?

The skill supplies investigation instructions for your agent. Use npx rea-agents setup to register REA's MCP server and install the matching instructions, then restart your agent. See skill-only installation.

What code does REA return?

Native analysis returns pseudocode and assembly. JavaScript/Electron analysis recovers modules and their relationships. Your agent uses these findings to write and test an implementation; the showcases give worked examples.

Does REA upload my app?

REA analyzes targets locally. Your agent receives the tool results, and its model provider has its own data policy.

What should I do if I hit a bug?

Update first; a recent release may already fix it.

For a CLI installed with npm install --global or bun add --global:

rea update

For agent setup through npx:

npx rea-agents@latest setup

If you're using an agent, complete the setup refresh and restart it. Retry the same task. If the problem persists, open an issue with your REA version, target type, steps to reproduce and error output.

Documentation

Start with the website's worked guides. For exact options, prerequisites and result contracts:

Report vulnerabilities through SECURITY.md.

Community & Support

  • Discord — Ask questions and share what you’re investigating with our passionate community of over 50,000 reverse engineers and builders! Join the REA Discord
  • Twitter / X — Follow @reatools for updates and announcements.
  • Feedback & Ideas — Want a new feature or support for a file format? Open a GitHub issue or join our Discord and let us know.

Star history

🎉 400,000 GitHub stars — thank you!

Thanks to everyone using REA, reporting bugs, requesting features, testing builds, and contributing fixes.

REA contributors REA GitHub star history

Contributing

We'd love your help with REA! Open an issue to report a bug or suggest a feature, or send a pull request to improve the code or docs.

See CONTRIBUTING.md for development setup and checks. See the testing guide for verification lanes.

Disclaimer

See DISCLAIMER.md for responsible-use guidance.

The project's position on illegal or unauthorized use covers all REA versions, distribution channels, and platforms; each copy retains its applicable licenses.

REA is for lawful research, education, interoperability, software preservation, and analysis of software you own or are authorized to examine.

License

MIT

REA-authored code is licensed under MIT. Third-party material retains its own licenses and copyright notices; see Third-party notices for the dependency inventory, preserved license texts, and external-tool terms.

You must legally obtain and be authorized to use commercial tools, including IDA Pro / Hex-Rays decompilers, Hopper, and JEB, under their applicable licenses. REA grants no tool license, key, or activation entitlement. Trials and demos remain subject to vendor terms, including user, feature, automation, and output sharing restrictions. Cracked copies, stolen keys, unauthorized key sharing, and bypassing license restrictions are not authorized. This guidance does not amend MIT or third-party licenses.

Languages
TypeScript 91.3%
JavaScript 5.1%
Python 1.2%
HTML 1.1%
Java 0.9%
Other 0.1%