#reverse-engineering

Intermediate tutorial: have your AI agent install REA, an open-source reverse-engineering tool. Point it at an app and a feature, and it takes the feature apart without the source code, explaining the workflow with evidence. Once you understand the principle, it writes its own version from scratch in your project and adds one improvement. Includes 3 copy-paste prompts.

The open source reverse engineering tool REA lets an AI agent take apart an app without its source code. Point it at a niche Android app and have it map only the user roles, flows, core data, and pricing points. Then build your own version from that brief. Includes a ready prompt and a note on install steps and infringement risk.

Someone has put together 10 reverse-engineering Skills and integration solutions for Agents: comprehensive analysis, scenario routing, Android interfaces, product analysis, lightweight command line, CTF, IDA assistance, JS signatures, and an all-in-one lab. We have added all of them to our site's Skill pages, with selection advice, license differences, and authorization reminders.

Use when a user wants to understand how an app, binary, or Electron program implements a feature and has no source code. Based on the open-source REA (MIT): connects analysis tools for native binaries, JavaScript/Electron, .NET, and websites via MCP. Analysis runs locally, and conclusions come with evidence and limitations. Only for your own targets or targets you are authorized to analyze. Use case: Have the agent work out how a feature of an app without source code is implemented, and provide evidence and limitations.

Use when a user hands over an APK, a binary, front-end encrypted JS, a CTF challenge or an authorized penetration-testing target, and is unsure which method and tools to use. Based on the open-source reverse-skill (MIT): routes to a suitable method, checks the local tools, confirms the authorized scope, then executes the workflow and produces a report. Use case: Have the agent first determine what kind of target it is, then choose the matching method, toolchain and report workflow.

Use when a user wants to decompile an APK, XAPK, JAR, or AAR, and extract an app's HTTP endpoints, authentication methods, and code structure. Built on the open-source android-reverse-engineering-skill (Apache-2.0): fingerprint first, then decompile with jadx and similar tools, with support for recovering Kotlin class names after R8 obfuscation. Only analyze apps you are authorized to analyze. Use case: Have an agent decompile an Android app and map the APIs it calls and its code structure.

Use when a user wants to reverse-engineer Electron, native binaries, Go, APK, WASM, firmware or websites with command-line tools already installed locally, without installing an MCP server. Based on the open-source leanrea (MIT): tells the Agent the fastest command and common pitfalls for each type of target, and conclusions must be labeled as seen or inferred. Use case: Let the Agent call local reverse-engineering command-line tools directly, skipping MCP and complex configuration.

Use when a user has already exported decompilation results from IDA and wants an agent to name function symbols, recover data structures, generate Frida or Unicorn scripts, or write IDAPython. Based on the open-source reverse-skills, with 8 skills in total; unpacking and shelling are only for apps you own or are authorized to analyze. Use case: Have the agent work from IDA decompilation output to name symbols, recover structures, and generate dynamic instrumentation scripts.

Use when a user needs to analyze frontend signatures, encrypted parameters, dynamic cookies, obfuscated JS or WASM, or when API collection keeps failing. Based on the open-source hello_js_reverse_skill (the repository does not declare a license): draw conclusions through controlled experiments and layered evidence, and only work on your own targets or targets you are authorized to test. Do not bypass paywalls, login protection, or CAPTCHAs. Use case: Have the Agent locate the origin of frontend signatures and cookies through controlled experiments, and reach conclusions backed by evidence.

Use when a user wants a ready-to-run reverse engineering workspace: analyzing samples with tools like Ghidra and Frida, doing CTF work, and producing evidence reports. Based on the open-source Open-ReverseLab (GPL-3.0): 180+ knowledge base articles plus 100+ MCP tools, with tools installed by board. Only for your own samples, lab targets, and authorized testing. Use case: Let an agent analyze samples and produce evidence reports in one workspace, using the knowledge base and over a hundred tools.

Use when a user needs to locate front-end encryption functions (login passwords, request signing, response decryption) and wants the results turned into reusable JSRPC, a Flask service and Burp autoDecoder configuration. Based on the open-source js-reverse-automation--skill (Apache-2.0), connecting to a real browser via chrome-devtools-mcp. Only for your own targets or targets you are authorized to test; shut down the services when done. Use case: Let the agent find front-end encryption entry points in a real browser and deliver callable services and Burp configuration.

Want to recreate a video? First decide whether you want to learn how it was made or rebuild an editable copy of it. REA-Video is open source and free, breaking down each shot into visuals, subtitles, editing and sound. HyperFrames reverse-any-video is a Pro feature that rebuilds an editable project and compares it frame by frame with the original. Includes tool selection, hands-on steps and FAQ.