튜토리얼 자료 · 작성자 ZookeepergameMost817

AI 리버스 엔지니어링 툴킷: 무료 도구, 에이전트, 과정, 실습 랩 — 이해하려는 대상별로 정리

에이전트 지원 리버스 엔지니어링의 시작점으로 REA를 소개하는 Reddit 리소스 지도입니다. 설정 단계, 실제 조사, 네이티브, .NET, Electron, iOS, MCP 도구 링크를 포함합니다.

ZookeepergameMost817@ZookeepergameMost817

번역 완료

이 사례에 대하여

이 게시물은 무료 리버스 엔지니어링 도구를 대상별로 정리하고 REA로 시작합니다. REA 저장소, 설치 문서, 첫 조사 가이드, Notes 내보내기, Notion 클립보드, DX-Ball, Aegis 같은 실제 사례 쇼케이스로 연결됩니다. npx rea-agents 설정 명령을 포함하고 상용 엔진과 모델 제공업체의 데이터 정책에 대한 주의를 환기한 뒤, 네이티브 바이너리, .NET, iOS, Electron/JavaScript용 MCP 브리지와 분석 도구를 나열합니다. 이는 단일 사례 연구가 아니라 교육용 리소스 모음입니다.

설정

설치 방법은 원본 출처를 확인하세요.

원문 / README

You don’t need another folder of 150 bookmarks.

You need to know which tool to open when you’re staring at a Windows binary, an Electron app, a firmware image, or an undocumented protocol.

This is a reverse-engineering resource map organized by target—not a random list of repos.

AI agents are part of it. So are disassemblers, debuggers, protocol analyzers, and free courses that teach you how to check the agent’s work.

The rule that ties everything together: evidence.

A convincing explanation is not the same as a verified reconstruction.

01 — Start with REA: connect your agent to the investigation

REA connects coding agents to tools for inspecting native binaries, JavaScript/Electron applications, .NET assemblies, websites, and runtime behavior. Results include supporting evidence and limitations.

Start here:

Setup:

npx rea-agents@latest setup

Review the proposed changes, approve the setup, and restart your agent.

Two important caveats:

REA is open source; commercial analysis engines such as IDA Pro and Hopper still require their own licenses.
REA analyzes targets locally, but tool results go to your agent. Your model provider’s data policy still matters.

02 — Follow a real investigation before inventing your own workflow

Start with one feature, not “explain this entire application.”

Notes export — follow a button through the preload bridge and IPC handler to the CSV writer. Then predict an edge case and test it.
Notion clipboard — follow a clipboard API through Electron’s process boundaries.
DX-Ball — follow a native sound calculation from original instructions to a checked reconstruction.
Aegis — explore an APK investigation focused on TOTP behavior.

The Notes exercise is a particularly good first step: the app is small, the trace is concrete, and you can check the CSV formatter’s behavior directly.

Also worth exploring: CTF Flag Checker, REA Gems, Chrome Dinosaur, and the Notes Evidence Record.

03 — AI reverse-engineering agents and MCP bridges

For connecting an agent to an analysis environment:

Also explore: Revenant, Awesome LLM Reverse Engineering, AgentRE-Bench, SRE-Bench, and Reverse Engineering Agent Skill.

Think of the agent as an investigator’s assistant—not the final authority on what a binary does.

04 — Native binaries

The core toolkit:

Keep these nearby too:

Keystone · GNU Binutils · GDB · LLDB · pwntools · ROPgadget · Detect It Easy · capa · YARA

05 — .NET applications

Start here:

Also explore:

AsmResolver · Harmony · Mono.Cecil · NativeAOT reversing helpers

06 — iOS

Documentation, practice targets, and device tooling:

Also explore:

ios-deploy · class-dump · ipsw · Objection

07 — Electron and JavaScript

For package