calculator

Reverse Engineer Anything: The Open-Source Tool That Turns Any Binary Into a Readable Spec (And Why Big Tech Won’t Love It) Closed source has always leaned on an unstated assumption: reading someone else's compiled code is slow. REA, short for Reverse Engineer Anything, is an MIT-licensed project built to make that assumption false. It showed up in a year when tech companies cut jobs at a pace TechCrunch's running tally put at around 120,000 by early July, with AI the most-cited reason. I'll cover what REA does and what it changes for companies. Then I'll give you my read on why it exists now, and you're free to disagree with it. The Problem It's Solving The tools for taking software apart already exist. Ghidra is free, Hopper is cheap, and IDA Pro is the long-standing commercial standard. What was missing is someone to drive them. An analyst picks the tool, learns its quirks, moves evidence between programs, and decides what to look at next. That takes skill, and it takes time. REA hands the driving to a coding agent. The pitch on rea.tools is simple: ask your agent how a feature in some app works, and REA gives it the tools to inspect the code behind the answer. The README goes further and says the agent can then build a version of that feature for your own project. How REA Actually Works REA is an MCP server plus a CLI. You run npx rea-agents setup, review the proposed changes, approve them, and restart your agent. Setup registers the server and installs matching workflow instructions, with backups of your existing config. The supported agents list includes Claude Code, Codex, Cursor, Gemini CLI and Grok Build. From there the agent calls REA like any other tool. REA inspects the target and returns findings along with the evidence and limitations behind each conclusion. The agent uses them to explain the behavior or write and test an implementation. According to the README, analysis runs locally. Your agent still receives the tool results, so your model provider's data policy applies to whatever it sees. The target list is long. Native binaries go through Hopper, Ghidra or IDA. Offline inspection can use GNU objdump or Rizin that you supply yourself. JavaScript and Electron applications get static analysis of modules, imports, source maps, routes and IPC with no native engine needed. Android APKs go through JADX. The README table also lists .NET assemblies, Flutter apps, firmware, Unity IL2CPP metadata, Godot archives, WASM, SQLite files, packet captures and live websites. One correction to the hype. REA is not a new decompiler, and it doesn't hand back original source code. A fact-check from October 14 makes the same point. REA returns pseudocode, assembly, modules and the relationships between them. The new piece is the agent working the loop. What Developers Are Actually Using It For The showcases show the work best, because each one asks a narrow question about software the author didn't write. On the site's Calculator example, the question is why Windows Calculator turns 200 + 10% into 220. The agent reads the percent handler's x64 instructions, finds that after addition the percent applies to the first operand, and checks the result against Microsoft's public source. In the dinosaur game example, it pulls the speed rule out of the running script: start at 6, add 0.001 per update, stop at 13. Then it rebuilds the game with a speed slider. The longer case studies go deeper. The Notion study traces the Electron clipboard bridge from the renderer through preload and IPC into the main process. The DX-Ball study recovers a 1996 game's sound-pan math as C, and the README says the reconstruction passes 3,205 original-x86 cases and reproduces all 63 compiled function bytes. The Aegis study follows an authenticator's six-digit code through its APK, and the TH04 study recovers bullet-ring angles from a PC-98 game. The site also lists bigger prompts as examples: clone this website, or reconstruct this game from its executable. So the project isn't pretending this stops at education. Why This Is a Bigger Deal Than It Looks Reading binaries was never impossible. It was expensive. REA lowers the cost, and that shifts a few things for companies. Shipped desktop and mobile apps are easier to study than they were. The README and site describe analyzing installed apps, Electron bundles, APKs and website scripts, all without source access. Anything a company ships to a user's machine can be inspected on that machine. The "we never looked at their code" defense gets harder to make. In a classic clean-room setup, one team analyzes and writes a spec while another team implements from the spec. REA's own example prompt asks one agent to investigate, show the evidence and build a similar feature, all in one session. That doesn't make it illegal. It does make independent development harder to demonstrate. This is my reading, and I'm not a lawyer. The law is older than the tooling. In Sega v. Accolade, the Ninth Circuit held in 1992 that disassembly for interoperability was fair use, and DMCA §1201(f) added an interoperability exception. EFF's reverse engineering FAQ treats contract law as its own separate risk, which matters because plenty of EULAs forbid reverse engineering. REA's DISCLAIMER says the project won't help with circumventing DRM, building cheats, bypassing authentication, or copying proprietary software and its protected code and assets. It also puts responsibility for authorization on the user. There's a tension there. The README advertises building a feature you saw in someone else's app, and the disclaimer rules out copying proprietary software. Where "learn how it works" ends and "copy it" begins is up to the person typing the prompt. Security cuts both ways. The README says runtime workflows execute or interact with the target under your user permissions, and the disclaimer says to use an appropriate environment for untrusted targets. The project has also had a supply-chain scare. The fact-check reports that on October 13 someone flagged a fake copy under an organization called rea-tools, advertising a "Windows Standalone .exe". It also reports that Microsoft Defender classified the file as a trojan and that 8 of 45 VirusTotal engines flagged it as a dropper. The official README now says to download only from the repo, rea.tools or the rea-agents npm package. The star count deserves a caveat too. The repo was created on April 14, 2026. The fact-check counted about 234,000 stars on October 14, and the repo page showed roughly 348,000 when I loaded it a week later. The fact-check says nobody can tell how many stars come from real readers, and I can't either. I'd treat the number as attention, not proof of adoption. My Take: Engineers Got Laid Off, Then Got Agents This section is opinion. Where I state a fact, there's a source next to it. Start with what is on record. Amazon announced 16,000 cuts on January 28, and Networkworld reports it posted record revenue of $716.9 billion for 2025. Meta cut roughly 8,000 jobs in May while guiding 2026 capex as high as $135 billion. Block's CEO tied its cuts to AI, per the same Newsweek piece. Microsoft cut 4,800 in July. Per Nairametrics, its CFO said headcount would keep falling as spending moves to AI infrastructure, while TechCrunch's tally quotes Microsoft saying those roles aren't being replaced by AI. The FT counts about 140,000 US tech jobs cut so far this year, about 50,000 of them at Amazon, Oracle, Meta and Microsoft. Trackers disagree on the totals, but every count is large. Now the part nobody can prove. I don't know who built REA, and nothing in the repo says they were laid off. So I'm not claiming that. My claim is narrower. Companies cut people while spending more on AI, and the same AI now sits in the hands of anyone with a free weekend. I believe many of the people cut were strong engineers. The trackers don't measure that and I can't prove it. But an engineer who is good at their job doesn't lose the skill when the badge stops working. That's where I think the energy is going. An MIT-licensed repo, under a year old, with nearly 4,000 commits, hundreds of open issues and pull requests, and an active Discord, did not come from nowhere. Someone cared enough to build it in public and give it away. I think a lot of developers right now are asking the same question: if my employer can decide my work is replaceable, why would I keep building closed things for them? Look at the other open-source moves this year, and be precise about each one. The Claude Code leak was an accident, not a protest. On March 31, a source map in an npm package exposed about 512,000 lines of Anthropic's TypeScript, and Anthropic confirmed it was unintentional. Google's decision to ship Gemma 4 under Apache 2.0 was a corporate licensing choice, the first Apache release in the Gemma line. REA is the odd one out: independent, deliberate, and aimed at everyone else's closed code. I'd say the three together point one direction, and only one of them is a revolt. So here is my actual prediction. The next few years will favor whoever ships in the open and lets people look inside. Companies that depend on nobody reading their code will have a harder time. What could make me wrong? Some of these layoffs may be ordinary cost cutting wearing an AI label. Microsoft's own statement points that way. REA's users may be mostly hobbyists, students and security researchers. Stars can be inflated. Agent output can be wrong, and REA's disclaimer says as much. Understanding how Notion bridges its clipboard does not give you Notion. And one repo doesn't make a movement. I'm still watching it, because I think the direction is right. Availability and Access REA is free and MIT-licensed. It needs Node.js 22.x (22.19 or later), 24.x (24.11 or later) or 26+, plus npm. npx rea-agents setup Native analysis needs Hopper, Ghidra or IDA already installed. REA grants no keys or licenses for commercial tools, so you need to obtain those legally yourself. Static JavaScript, Electron and .NET analysis need no native engine. Install the CLI with npm install --global rea-agents and keep it current with rea update. Get it only from morluto/rea, rea.tools, or the npm package. There's also a Discord for questions. Closed source has leaned on reading being slow. REA is one more sign, among several this year, that the slowness is going away. Follow for more coverage on MCP, agentic AI, and AI infrastructure.

REA + Claude Code: la IA que abre cualquier programa (tutorial) REA (Reverse Engineer Anything) es el repositorio de GitHub que conecta a Claude Code, Codex o Cursor con Ghidra, IDA y Hopper para hacer ingeniería inversa con IA. Te explico qué hace de verdad, lo que la gente ya consiguió y cómo usarlo paso a paso. En este video: • Qué es la ingeniería inversa (sin tecnicismos) • Qué es REA y qué NO es: no te da el código fuente original • Casos reales: el dinosaurio de Chrome, Aegis, DX-Ball y Notion • Lo que hicieron Eric Tech, MG, SoftsWeb y Korben • Instalación en Windows paso a paso (Node, setup, doctor, Ghidra) • Una investigación real con Claude Code + REA, y cómo comprobarla • El método para preguntarle bien (y una plantilla) • Tres avisos: la copia falsa con troyano, los binarios trampa y lo legal ⏱️ CAPÍTULOS 0:00 Intro: 200 + 10 % = 220 1:04 La caja negra 2:06 Qué es REA (y qué no) 3:44 Expedientes: lo que ya se logró 6:58 Cómo usarlo, paso a paso 8:57 Cómo preguntarle bien 9:42 La letra pequeña 10:54 ¿De verdad lo necesitas? 🧪 PLANTILLA DE PREGUNTA (cópiala en tu agente) Usa REA para investigar [una función] de [la app], que está en [ruta] y está hecha con [Electron / .exe / APK / web]. Primero dame un resumen corto. Marca cada hallazgo como VISTO, DEDUCIDO o DESCONOCIDO, con su evidencia (archivo, línea o dirección). No escribas código hasta que apruebe el plan. 🛠️ COMANDOS DEL VIDEO (Windows, PowerShell) node -v winget install --exact --id OpenJS.NodeJS.LTS npx rea-agents@latest setup npx rea-agents@latest doctor --client claude_code --json (si PowerShell bloquea los scripts: npx.cmd en vez de npx) Ejemplo de notas: rea.tools ⚠️ Instala REA SOLO desde npm (rea-agents), github.com/morluto/rea o rea.tools. No existe un .exe oficial. Úsalo con programas tuyos, de código abierto o que tengas permiso para analizar. Esto no es asesoría legal. 📚 FUENTES • REA, repositorio oficial: morluto/rea • REA, web y guía de inicio: rea.tools • Casos oficiales (dinosaurio, calculadora, Aegis, DX-Ball, Notion): rea.tools • Paquete npm rea-agents: npmjs.com • Aviso legal del proyecto (DISCLAIMER.md): github.com/morluto/rea/blob/main/DISCLAIMER.md • Aviso de la copia falsa con troyano (issue #2424, 13 oct 2026): rea#2424 • Versión 6.0.0 (8 oct 2026): github.com/morluto/rea/releases/tag/rea-agents-6.… • Ranking de estrellas de GitHub (consultado el 17 oct 2026): github.com/search • Calculadora de Windows, la regla del % en su código abierto: github.com/microsoft/calculator/blob/d125246a4e19… • Juego del dinosaurio (versión de wayou, derivada de Chromium, BSD): wayou/t-rex-runner • Aegis Authenticator (código abierto): beemdevelopment/Aegis • Korben, «REA - Probé la ingeniería inversa con un agente de IA» (14 oct 2026): korben.info • Eric Tech, «How To Use REA To Clone Any Software In Minutes»: youtube.com • MG, «How to Reverse Engineer Anything in Claude Code»: youtube.com • SoftsWeb, «REA + Claude Code Reverse Engineered a Real App in 22 Minutes»: youtube.com • Nate Herk, «I Tested the Viral Reverse Engineer Anything Skill» (método de 5 pasos): youtube.com • Bruno, cliente de APIs de código abierto: usebruno/bruno • Crawford, Phillips y McClure, «Automatically Attacking Software Reverse Engineering AI Agents» (arXiv, 28 may 2026): arxiv.org • ByteIota, análisis de REA y su crecimiento: byteiota.com • Pasquale Pillitteri, verificación de cifras (14 oct 2026): pasqualepillitteri.it • Post de @Voxyz_ai sobre el #1 en tendencias (11 oct 2026): x.com • Anthropic, Model Context Protocol (nov 2024): anthropic.com • Ghidra (NSA): NationalSecurityAgency/ghidra • IDA, historia (Hex-Rays): hex-rays.com 🧾 Notas: las cifras de estrellas cambian cada día (302,432 el 17 oct 2026, según la API de GitHub). Los casos de rea.tools los publica el propio proyecto. Las cifras de Eric Tech, MG, SoftsWeb y Korben son de sus propios videos y artículos. La terminal del capítulo 4 es una sesión real en mi PC (Claude Code 2.1 + REA 6.5.0, 17 oct 2026), resumida. #IA #Claude #ClaudeCode #REA #IngenieriaInversa #CtrlAltDev [ar] REA + Claude Code: الذكاء الاصطناعي الذي يفكك أي برنامج (شرح تعليمي) REA (الهندسة العكسية لأي شيء) هو مستودع GitHub الذي يربط بين Claude Code وCodex وCursor مع Ghidra وIDA وHopper لإجراء الهندسة العكسية باستخدام الذكاء الاصطناعي. سأشرح بالتفصيل وظيفة هذا المستودع، وما حققه المستخدمون بالفعل، وكيفية استخدامه خطوة بخطوة. في هذا الفيديو: • ما هي الهندسة العكسية (بدون مصطلحات تقنية معقدة) • ما هو برنامج OER وما ليس هو: فهو لا يوفر لك شفرة المصدر الأصلية • أمثلة واقعية: برنامج Chrome Danour، وAegis، وDX-Ball، وNotion • ما فعله كل من Eric Tech وMG وSoftsWeb وKorben • تثبيت برنامج OER على نظام Windows خطوة بخطوة (Node، setup، doctor، Ghidra) • تحقيق عملي باستخدام Claude Code وبرنامج OER، وكيفية التحقق منه • طريقة طرح الأسئلة الصحيحة (مع نموذج) • ثلاثة تحذيرات: النسخة المزيفة التي تحتوي على حصان طروادة، والملفات الثنائية الخادعة، وما هو قانوني ⏱️ الفصول 0:00 مقدمة: 200 + 10% = 220 1:04 الصندوق الأسود 2:06 ما هو برنامج OER (وما ليس هو) 3:44 الملفات: ما تم إنجازه بالفعل 6:58 كيفية استخدامه، خطوة بخطوة الخطوة 8:57 كيفية طرح الأسئلة الصحيحة 9:42 الحرف الصغير 10:54 هل أنت بحاجة إليه حقًا؟ 🧪 نموذج السؤال (انسخه إلى وكيلك) استخدم الموارد التعليمية المفتوحة (OER) للتحقق من [ميزة] في [التطبيق]، الموجود في [المسار] والمبني باستخدام [Electron / .exe / APK / web]. أولًا، قدم لي ملخصًا موجزًا. حدد كل نتيجة على أنها مرئية أو مستنتجة أو غير معروفة، مع ذكر الدليل (ملف، سطر، أو عنوان). لا تكتب أي كود حتى أوافق على الخطة. 🛠️ أوامر من الفيديو (ويندوز، باور شيل) node -v winget install --exact --id OpenJS.NodeJS.LTS npx rea-agents@latest setup npx rea-agents@latest doctor --client claude_code --json (إذا حظر باور شيل البرامج النصية: استخدم npx.cmd بدلاً من npx) ملاحظات توضيحية: rea.tools ⚠️ ثبّت REA فقط من npm (rea-agents)، أو github.com/morluto/rea، أو rea.tools. لا يوجد ملف .exe رسمي. استخدمه مع برامجك الخاصة، أو البرامج مفتوحة المصدر، أو البرامج التي لديك إذن بتحليلها. هذه ليست نصيحة قانونية. ... 📚 المصادر • الموارد التعليمية المفتوحة، المستودع الرسمي: morluto/rea • الموارد التعليمية المفتوحة، الموقع الإلكتروني ودليل البدء: rea.tools • العروض التوضيحية الرسمية (ديناصور، آلة حاسبة، إيجيس، دي إكس-بول، نوشن): rea.tools • حزمة npm المسماة rea-agents: npmjs.com • الإشعار القانوني للمشروع (DISCLAIMER.md): github.com/morluto/rea/blob/main/DISCLAIMER.md • تحذير من وجود برامج ضارة (المشكلة رقم 2424، 13 أكتوبر 2026): rea#2424 • الإصدار 6.0.0 (8 أكتوبر 2026): github.com/morluto/rea/releases/tag/rea-agents-6.… • تصنيف النجوم على GitHub (تمت زيارته في 17 أكتوبر 2026): github.com/search • آلة حاسبة ويندوز، قاعدة النسبة المئوية في شفرتها المصدرية المفتوحة: github.com/microsoft/calculator/blob/d125246a4e19… • لعبة الديناصورات (إصدار Wayou، مشتق من Chromium، مرخصة بموجب ترخيص BSD): wayou/t-rex-runner • تطبيق Aegis Authenticator (مفتوح المصدر): beemdevelopment/Aegis • كوربن، "REA - اختبرتُ الهندسة العكسية باستخدام وكيل ذكاء اصطناعي" (14 أكتوبر 2026): korben.info • إريك تك، "كيفية استخدام REA لاستنساخ أي برنامج في دقائق": youtube.com • إم جي، "كيفية إجراء الهندسة العكسية لأي شيء باستخدام كود كلود": youtube.com • سوفت ويب، "REA + كود كلود: هندسة عكسية لتطبيق حقيقي في 22 دقيقة": youtube.com • نيت هيرك، "اختبرتُ مهارة الهندسة العكسية الفيروسية لأي شيء" (طريقة من 5 خطوات): youtube.com • برونو، عميل واجهة برمجة تطبيقات مفتوح المصدر: usebruno/bruno • كروفورد، فيليبس، وماكلور، "الهجوم التلقائي على وكلاء الذكاء الاصطناعي الذين يقومون بالهندسة العكسية للبرمجيات" (arXiv، 28 مايو 2026): arxiv.org • بايت إيوتا، تحليل الهندسة العكسية المفتوحة ونموها: byteiota.com • باسكوالي بيليتيري، التحقق من الحقائق (14 أكتوبر 2026): pasqualepillitteri.it • منشور بواسطة @Voxyz_ai حول الموضوع الأكثر رواجًا (11 أكتوبر 2026): x.com • أنثروبيك، بروتوكول سياق النموذج (نوفمبر 2024): anthropic.com • غيدرا (وكالة الأمن القومي): NationalSecurityAgency/ghidra • آي دي إيه، التاريخ (هيكس-رايز): hex-rays.com 🧾 ملاحظات: يتغير عدد النجوم يوميًا (302,432 في 17 أكتوبر 2026، وفقًا لواجهة برمجة تطبيقات GitHub). يتم نشر حالات rea.tools من قِبل المشروع نفسه. أما أرقام Eric Tech وMG وSoftsWeb وKorben فهي من مقاطع الفيديو والمقالات الخاصة بهم. الطرفية المذكورة في الفصل الرابع هي جلسة حقيقية على جهازي (Claude Code 2.1 + REA 6.5.0، بتاريخ 17 أكتوبر 2026)، وهي ملخصة. #الذكاء_الاصطناعي #Claude #ClaudeCode #REA #الهندسة_العكسية #Ctr... [en-US] REA + Claude Code: The AI That Opens Any Program (Tutorial) REA (Reverse Engineer Anything) is the GitHub repository that connects Claude Code, Codex, or Cursor with Ghidra, IDA, and Hopper for reverse engineering with AI. I'll explain what it actually does, what people have already achieved, and how to use it step by step. In this video: • What reverse engineering is (without technical jargon) • What OER is and what it ISN'T: it doesn't give you the original source code • Real-world examples: the Chrome dinosaur, Aegis, DX-Ball, and Notion • What Eric Tech, MG, SoftsWeb, and Korben did • Step-by-step Windows installation (Node, setup, doctor, Ghidra) • A real investigation with Claude Code + OER, and how to verify it • The method for asking the right questions (and a template) • Three warnings: the fake copy with a Trojan, the trap binaries, and what's legal ⏱️ CHAPTERS 0:00 Intro: 200 + 10% = 220 1:04 The black box 2:06 What OER is (and what it isn't) 3:44 Files: what has already been achieved 6:58 How to use it, step by step 8:57 How to ask the right questions 9:42 The letter small 10:54 Do you really need it? 🧪 QUESTION TEMPLATE (copy it into your agent) Use OER to investigate [a feature] of [the app], which is located at [path] and is built with [Electron / .exe / APK / web]. First, give me a short summary. Mark each finding as SEEN, INFERRED, or UNKNOWN, with its evidence (file, line, or address). Don't write any code until I approve the plan. 🛠️ COMMANDS FROM THE VIDEO (Windows, PowerShell) node -v winget install --exact --id OpenJS.NodeJS.LTS npx rea-agents@latest setup npx rea-agents@latest doctor --client claude_code --json (If PowerShell blocks scripts: use npx.cmd instead of npx) Example notes: rea.tools ⚠️ Install REA ONLY from npm (rea-agents), github.com/morluto/rea, or rea.tools. There is no official .exe. Use it with your own programs, open-source software, or programs you have permission to analyze. This is not legal advice. 📚 SOURCES • OER, official repository: morluto/rea • OER, website and getting started guide: rea.tools • Official showcases (dinosaur, calculator, Aegis, DX-Ball, Notion): rea.tools • npm package rea-agents: npmjs.com • Project legal notice (DISCLAIMER.md): github.com/morluto/rea/blob/main/DISCLAIMER.md • Notice of counterfeit copy with Trojan (issue #2424, October 13, 2026): rea#2424 • Version 6.0.0 (October 8, 2026): github.com/morluto/rea/releases/tag/rea-agents-6.… • GitHub Star Ranking (accessed October 17, 2026): github.com/search • Windows Calculator, the % rule in its open source code: github.com/microsoft/calculator/blob/d125246a4e19… • Dinosaur game (Wayou version, derived from Chromium, BSD): wayou/t-rex-runner • Aegis Authenticator (open source): beemdevelopment/Aegis • Korben, "REA - I Tested Reverse Engineering with an AI Agent" (Oct 14, 2026): korben.info • Eric Tech, "How To Use REA To Clone Any Software In Minutes": youtube.com • MG, "How to Reverse Engineer Anything in Claude Code": youtube.com • SoftsWeb, "REA + Claude Code Reverse Engineered a Real App in 22 Minutes": youtube.com • Nate Herk, "I Tested the Viral Reverse Engineer Anything Skill" (5-step method): youtube.com • Bruno, open-source API client: usebruno/bruno • Crawford, Phillips, and McClure, “Automatically Attacking Software Reverse Engineering AI Agents” (arXiv, May 28, 2026): arxiv.org • ByteIota, analysis of OER and its growth: byteiota.com • Pasquale Pillitteri, fact-checking (October 14, 2026): pasqualepillitteri.it • Post by @Voxyz_ai about the #1 trending topic (October 11, 2026): x.com • Anthropic, Model Context Protocol (Nov 2024): anthropic.com • Ghidra (NSA): NationalSecurityAgency/ghidra • IDA, History (Hex-Rays): hex-rays.com 🧾 Notes: Star counts change daily (302,432 on Oct 17, 2026, according to the GitHub API). Cases for rea.tools are published by the project itself. The figures for Eric Tech, MG, SoftsWeb, and Korben are from their own videos and articles. The terminal in Chapter 4 is a real session on my PC (Claude Code 2.1 + REA 6.5.0, October 17, 2026), summarized. #AI #Claude #ClaudeCode #REA #ReverseEngineering #CtrlAltDev [pt-BR] REA + Claude Code: a IA que abre qualquer programa (tutorial) REA (Reverse Engineer Anything) é o repositório do GitHub que conecta Claude Code, Codex ou Cursor com Ghidra, IDA e Hopper para engenharia reversa com IA. Vou explicar o que ele faz, o que as pessoas já conseguiram e como usá-lo passo a passo. Neste vídeo: • O que é engenharia reversa (sem jargões técnicos) • O que é OER e o que NÃO é: não fornece o código-fonte original • Exemplos do mundo real: o dinossauro do Chrome, Aegis, DX-Ball e Notion • O que Eric Tech, MG, SoftsWeb e Korben fizeram • Instalação passo a passo no Windows (Node, setup, doctor, Ghidra) • Uma investigação real com Claude Code + OER e como verificá-la • O método para fazer as perguntas certas (e um modelo) • Três alertas: a cópia falsa com um Trojan, os binários de armadilha e o que é legal ⏱️ CAPÍTULOS 0:00 Introdução: 200 + 10% = 220 1:04 A caixa preta 2:06 O que é OER (e o que não é) 3:44 Arquivos: o que já foi alcançado 6:58 Como usar, passo a passo Etapa 8:57 Como fazer as perguntas certas 9:42 A letra pequena 10:54 Você realmente precisa disso? 🧪 MODELO DE PERGUNTA (copie para o seu agente) Use o OER para investigar [um recurso] de [o aplicativo], que está localizado em [caminho] e foi desenvolvido com [Electron / .exe / APK / web]. Primeiro, forneça um breve resumo. Marque cada descoberta como OBSERVADA, INFERIDA ou DESCONHECIDA, com sua respectiva evidência (arquivo, linha ou endereço). Não escreva nenhum código até que eu aprove o plano. 🛠️ COMANDOS DO VÍDEO (Windows, PowerShell) node -v winget install --exact --id OpenJS.NodeJS.LTS npx rea-agents@latest setup npx rea-agents@latest doctor --client claude_code --json (Se o PowerShell bloquear scripts: use npx.cmd em vez de npx) Exemplos de notas: rea.tools ⚠️ Instale o REA SOMENTE a partir do npm (rea-agents), github.com/morluto/rea ou rea.tools. Não há um .exe oficial. Use-o com seus próprios programas, software de código aberto ou programas que você tenha permissão para analisar. Isto não constitui aconselhamento jurídico. 📚 FONTES • REA, repositório oficial: morluto/rea • REA, site e guia de primeiros passos: rea.tools • Exemplos oficiais (dinossauro, calculadora, Aegis, DX-Ball, Notion): rea.tools • Pacote npm rea-agents: npmjs.com • Aviso legal do projeto (DISCLAIMER.md): github.com/morluto/rea/blob/main/DISCLAIMER.md • Aviso de cópia falsificada com Trojan (problema nº 2424, 13 de outubro de 2026): rea#2424 • Versão 6.0.0 (8 de outubro de 2026): github.com/morluto/rea/releases/tag/rea-agents-6.… • Classificação por estrelas do GitHub (acessado em 17 de outubro de 2026): github.com/search • Calculadora do Windows, a regra % em seu código aberto: github.com/microsoft/calculator/blob/d125246a4e19… • Jogo do dinossauro (versão Wayou, derivado do Chromium, BSD): wayou/t-rex-runner • Autenticador Aegis (código aberto): beemdevelopment/Aegis • Korben, "REA - Testei Engenharia Reversa com um Agente de IA" (14 de outubro de 2026): korben.info • Eric Tech, "Como usar o REA para clonar qualquer software em minutos": youtube.com • MG, "Como fazer engenharia reversa de qualquer coisa com o Claude Code": youtube.com • SoftsWeb, "REA + Claude Code fizeram engenharia reversa de um aplicativo real em 22 minutos": youtube.com • Nate Herk, "Testei a habilidade viral de engenharia reversa de qualquer coisa" (método de 5 etapas): youtube.com • Bruno, cliente de API de código aberto: usebruno/bruno • Crawford, Phillips e McClure, “Ataques automáticos a agentes de IA de engenharia reversa de software” (arXiv, 28 de maio de 2026): arxiv.org • ByteIota, análise de OER e seu crescimento: byteiota.com • Pasquale Pillitteri, verificação de fatos (14 de outubro de 2026): pasqualepillitteri.it • Postagem de @Voxyz_ai sobre o tópico nº 1 em alta (outubro) 11 de outubro de 2026): x.com • Anthropic, Protocolo de Contexto de Modelo (novembro de 2024): anthropic.com • Ghidra (NSA): NationalSecurityAgency/ghidra • IDA, Histórico (Hex-Rays): hex-rays.com 🧾 Observações: A contagem de estrelas muda diariamente (302.432 em 17 de outubro de 2026, de acordo com a API do GitHub). Os casos para rea.tools são publicados pelo próprio projeto. Os números para Eric Tech, MG, SoftsWeb e Korbe...

REA 不到 10 天衝上 23 萬星：叫 AI 拆開任何軟體，它讀得到什麼、讀不到什麼 加入頻道會員，新片提早 24 小時看：youtube.com GitHub 上一個叫 REA 的逆向工程工具，2026 年 10 月初不到 10 天從約 6,869 顆星衝到 23 萬多顆（10 月 15 日上午 236,869）。爆紅期間，X 上一篇被看了 120 多萬次的長文教學開頭說你每個月付費訂閱的軟體，功能早就躺在你自己的電腦裡，標題寫成用它能免費拿到任何東西。這句話只對了一半。這支片講 REA 實際做什麼、官網示範為什麼多半挑原始碼公開或能拿原程式核對的對象、官方部落格的東方 Project 重建案例和它自己記下的錯誤，再用我自己研究一款語音輸入 App、另做一個版本的經驗，講逆向工程讀得到什麼、讀不到什麼，最後是台灣著作權法和營業秘密的界線。 章節 00:00 不到 10 天衝上 23 萬顆星 00:39 這句話只對了一半 00:52 逆向工程與 REA 01:27 官網的計算機示範 01:52 示範的前提 02:14 為什麼挑開源軟體 02:38 東方文花帖的重建 03:02 抓錯的測試也會出錯 03:28 我也走過一遍 04:00 電腦這一端與伺服器 04:20 自己做的版本 ripless 04:43 AI 犯過的錯 05:10 REA 讀不到的那一半 05:31 轉貼途中掉了但書 06:07 免責聲明 06:24 拿來保護自己 06:39 台灣著作權法 07:25 營業秘密 07:47 頻道會員 08:12 看懂之後能不能公開 08:38 收尾 說明 星數是 2026 年 10 月 15 日上午從 GitHub API 讀到的數字，之後仍在增加。官網示範的計算機是 Windows 計算機，微軟 2019 年起以 MIT 授權公開原始碼；官網其他示範約一半是開源軟體或公開的解題挑戰，另一半像 Notion 是封閉軟體，拿實際程式與它的表現交叉核對。「四步流程」是那篇 X 教學作者整理的說法，不是 REA 官方定義。《東方文花帖》697 個函式、696 個通過初步比對出自 REA 官方部落格，負責重建的人也是 REA 主要開發者之一；比對工具沒核對寫死數值、在 5 個函式找出 12 個錯誤引用，是同一篇文章記下的前一個專案（TH08《東方永夜抄》）。親身段那款語音輸入 App 刻意不點名，片中只講方法與心得，沒有破解加密、沒有碰它與伺服器之間的通訊；錯字率、時間與成本是我自己的測試，不是公開評測。片中法律內容是整理條文與判決，不是法律意見；還原工程例外的三個條件出自經濟部認定要點。RimWorld 的段落是開發商在下架通知裡的主張，GitHub 處理時註記反規避主張的資訊不足、其他著作權主張成立。 主要來源 REA 官網：rea.tools REA GitHub：morluto/rea REA 免責聲明：github.com/morluto/rea/blob/main/DISCLAIMER.md REA 官方部落格〈The industrial revolution in reverse engineering〉：rea.tools REA Notion 個案：rea.tools Windows 計算機原始碼：microsoft/calculator X 教學原文（@0xCodila）：x.com 被加上社群註記的轉貼（@firesidealpha）：x.com ArtCraft（storytold）：github.com/storytold PS1 靜態重編譯（1379.tech，2026-03-11）：1379.tech RimWorld 下架通知：github.com/github/dmca/blob/master/2026/10/2026-1… 著作權法第 80 條之 2：law.moj.gov.tw 著作權法第 96 條之 1：law.moj.gov.tw 最高法院 110 年度台上字第 3193 號判決（司法院公報）：judicial.gov.tw 經濟部〈著作權法第八十條之二第三項各款內容認定要點〉：law.moea.gov.tw 畫面來源 網頁畫面為各網站頁面截圖（2026-10-15 擷取），畫面右上逐段標示出處。ripless 畫面為預覽模式的假資料。 訂閱電子報《狐說八道》 anduril.tw #逆向工程 #AI #REA [en-US] REA Hits 230,000 Stars in Under 10 Days: Using AI to Deconstruct Any Software—What It Can and Can... A reverse engineering tool called REA on GitHub saw its star count surge from approximately 6,869 to over 230,000 in less than 10 days in early October 2026 (reaching 236,869 by the morning of October 15th). During this period of explosive popularity, a long tutorial on X, which received over 1.2 million views, began by claiming that the functions of the software you subscribe to monthly are already stored on your computer, and the title stated that it could provide access to anything for free. This statement was only half true. This video explains what REA actually does, why its official demonstrations mostly focus on publicly available source code or objects that can be verified with the original code, the Touhou Project reconstruction case on its official blog, and the errors it records. It then uses my own experience researching a voice input app and creating a different version to explain what reverse engineering can and cannot reveal, and finally, the boundaries between Taiwanese copyright law and trade secrets. Chapter 00:00 Reaching 230,000 Stars in Less Than 10 Days 00:39 This Statement is Only Half True 00:52 Reverse Engineering and REA 01:27 Official Computer Demonstration 01:52 Prerequisites for the Demonstration 02:14 Why Choose Open Source Software? 02:38 Reconstructing the Touhou Project 03:02 Mistakes in Testing Can Also Lead to Errors 03:28 I've Gone Through It Too 04:00 The Computer Side and the Server 04:20 My Own Ripless Version 04:43 Mistakes AI Has Made 05:10 The Half You Can't Read in REA 05:31 A Prohibition Was Lost During Reposting 06:07 Disclaimer 06:24 Using It to Protect Yourself 06:39 Taiwan Copyright Law 07:25 Trade Secrets 07:47 Channel Membership 08:12 Can I Share It After Understanding It? 08:38 Conclusion Note: The star count is from the GitHub API as of the morning of October 15, 2026, and has been increasing since. The computer used for the official demonstration is a Windows computer, and Microsoft has released the source code under the MIT license since 2019. About half of the other demonstrations on the official website are open-source software or public problem-solving challenges, while the other half, like Notion, are closed software. Their performance is cross-checked against actual programs. The "four-step process" is a term compiled by the author of the X tutorial, not an official REA definition. Of the 697 functions in *Touhou Bunka Shoujo*, 696 passed the initial comparison from the official REA blog; the person responsible for the reconstruction is also one of REA's main developers. The comparison tool failed to check hard-coded values ​​and found 12 incorrect references in 5 functions; this was from a previous project (TH08 *Touhou Eiyashou*) recorded in the same article. The video deliberately avoids naming the voice input app used in the demonstration, only sharing methods and experiences without addressing encryption cracking or the communication between the app and its server. The error rate, time, and cost figures are from my own testing, not a public review. The legal content is a compilation of articles and judgments, not legal advice. The three conditions for the engineering exception are based on the Ministry of Economic Affairs' criteria. The RimWorld section reflects the developer's claims in the removal notice; GitHub noted insufficient information regarding anti-circumvention claims and the validity of other copyright claims. Main Sources REA Official Website: rea.tools REA GitHub: morluto/rea REA Disclaimer: github.com/morluto/rea/blob/main/DISCLAIMER.md REA Official Blog "The Industrial Revolution in Reverse Engineering": rea.tools REA Notion Case Study: rea.tools Windows Computer Source Code: microsoft/calculator X Original tutorial (@0xCodila): x.com Repost with community annotation (@firesidealpha): x.com ArtCraft (storytold): github.com/storytold PS1 static recompiler (1379.tech, 2026-03-11): 1379.tech RimWorld removal notice: github.com/github/dmca/blob/master/2026/10/2026-1… Article 80 of the Copyright Law 2: law.moj.gov.tw Article 96-1 of the Copyright Act: law.moj.gov.tw Supreme Court Case No. 3193, 2011 Judgment No. [Number] (Judicial Yuan Gazette): judicial.gov.tw Ministry of Economic Affairs' "Key Points for Determining the Content of Each Paragraph of Article 80-2, Paragraph 3 of the Copyright Act": law.moea.gov.tw Image Source: The webpage images are screens...

This is lowkey CRAZY: In the official Microsoft github section for the calculator, they have a bunch of fucking coins for different planets??? They refer to all these as "Space Coins" its fucking crazy, check it out: github.com/microsoft/calculator/blob/d125246a4e19… x.com t.co

INSANE NARRA!?!? But this is literally the SYMBOL of the COIN github.com/microsoft/calculator/blob/d125246a4e19… x.com t.co

@davepl1968 BTW, the windows calculator is open source. Is there any chance the AI just reused the source code as it's publicly available and made it look like it created the clone from the binary you provided? microsoft/calculator

And the BTW, the windows calculator is open source. Is there any chance the AI just reused the source code as it's publicly available and made it look like it created the clone from the binary you provided? microsoft/calculator