---
title: "this is f*cking dangerous REA lets your agent read any closed-source app on your"
url: "https://reamcp.dev/en/cases/this-is-f-cking-dangerous-rea-lets-your-agent-read-any-close-7fce59"
source: "https://x.com/i/status/2111427421958185262"
source_type: "x"
author: "NO1ennn"
author_handle: "N01ennn"
stars: 0
category: "App feature recreation"
categories: ["app-recreation"]
tags: ["closed-source-analysis", "electron", "ghidra", "jadx", "mcp", "reverse-engineering"]
added: "2026-10-19T02:07:31.545Z"
updated: "2026-10-17T12:01:40.000Z"
locale: "en"
content_locale: "en"
---

# this is f*cking dangerous REA lets your agent read any closed-source app on your

this is f*cking dangerous

REA lets your agent read any closed-source app on your laptop, down to the binary

here's what happens when you ask it one question:

> you ask: what happens when I click Export?
> your agent calls REA, one MCP server, running on your machine
> REA picks the engine: Ghidra, IDA, JADX, a browser, or none at all
> it traces the click: renderer -> preload -> IPC -> main
> findings come back with the code, the evidence and the unknowns
> your agent explains how the feature works
> then builds your own version and tests it

MIT. runs locally. #1 repo of the day on GitHub.

npx rea-agents setup

## Original README

this is f*cking dangerous

REA lets your agent read any closed-source app on your laptop, down to the binary

here's what happens when you ask it one question:

> you ask: what happens when I click Export?
> your agent calls REA, one MCP server, running on your machine
> REA picks the engine: Ghidra, IDA, JADX, a browser, or none at all
> it traces the click: renderer -> preload -> IPC -> main
> findings come back with the code, the evidence and the unknowns
> your agent explains how the feature works
> then builds your own version and tests it

MIT. runs locally. #1 repo of the day on GitHub.

npx rea-agents setup