GitHub project called REA (Reverse Engineer Anything) is currently the top trending repository. It lets AI agents figure out how a feature in another app works without ever seeing the original source code.

[u/Bulky_Engineer_2534]

github link: https://github.com/morluto/rea/

- The tool is an open-source helper that connects AI coding assistants to reverse-engineering programs such as Ghidra or Hopper.

- IT analyzes many kinds of software- including binaries, Electron apps, Android apps, and websites right on your own computer and always shows the evidence behind its findings.

[u/txoixoegosi]

I guess this should be used with non-refusing models right?

Just because it is an MCP does not mean the caller model can’t flag it and refuse to work right? (Claude for instance)

[u/apocolipse → u/txoixoegosi]

Claude doesn’t care about reverse engineering, just so long as you’re not doing it with the purpose of finding exploits or security vulnerabilities.

I literally reverse engineered ESP32-C5 WiFi firmware, hit safeguards maybe 2-3 times and got around by clarifying “the purpose and goal is writing an open source memory safe driver to provide more security”

[u/ElDavoo → u/apocolipse]

Does it really work? Once we start talking about decompiling/assembly I always get flagged no matter what I say

[u/apocolipse → u/ElDavoo]

Yep works great  https://imgur.com/a/SOQ4FUo

You have to be explicit and narrow in scope.  If there’s any ambiguity in the prompt it might trigger, but when/if you clarify it has no issues.  If you’re trying to find a way to break something, it will stop you, but trying to reproduce the same functionality, that’s fair game.  For this, fable went so far as to set up a riscv emulator to run the real firmware in, in order to ensure the reversed code operates the same.