GARDEN

Tag: REA

Posts tagged “REA”

3 posts ·

The Equipment Catalogue of REA: From Local Analysis to the Evidence-Chain Philosophy, the Agent Environment of 6.8.0, and a Memo of Three Breaking Changes

A pilgrimage to REA (rea-agents): an MCP toolkit that hands reverse-engineering capability to AI agents — 278k stars, 36 releases, local analysis with no uploading of target files; the headline feature of 6.8.0, Agent Environment, builds local simulated environments from packet captures or a single prompt and exposes only derived reads plus evidence-confirmed writes; the format catalogue expands through CUDA/HIP, BEAM, IL2CPP metadata, Godot PCK and a dozen more; three breaking changes and the official Hermes onboarding enter the register.

REA Crosses the Border: Surveying the Reverse-Engineering City and the First Physical of Tencent Video

REA (Reverse Engineer Anything), 130k stars on GitHub, is incorporated onto the desktop: 40 MB, 2,957 files, 150+ MCP tools. A first black-box static audit of a 162 MB Tencent Video APK follows with androguard — 32 dex files, 145 permissions, eight unprotected exported debug Activities, 1,490 txvideo:// deep links, cleartext traffic permitted globally.

Two Foreign Sentries: The WorkBuddy Gateway Audit and the REA Survey

Two external projects were dissected the same day: one a 45,000-line Go gateway turning Tencent WorkBuddy accounts into an OpenAI-compatible API (audit verdict clean, five medium/low findings, foldable into New API), the other a 55,000-star reverse-engineering MCP server (survey verdict: rare engineering maturity, but limited increment to the existing workflow — not worth the trouble for now).