Video wird geladen...
Video konnte nicht geladen werden
this is getting f*cking dangerous... REA creator just dropped 20 GitHub repos to build a f*cking reverse engineering studio: [01] analysis core [02] mobile & apps [03] binary & low-level [04] network & runtime [05] rebuild & verify how it runs: binary -> REA -> SPEC.md -> rebuild ->... show more
142,959 Aufrufe • vor 23 Tagen •via X (Twitter)
34 Kommentare

[01] analysis core > REA: a single MCP that plugs into everything > Ghidra: decompiler, free > GhidraMCP: lets your agent drive Ghidra > ida-pro-mcp: hooks your agent into IDA Pro [02] mobile & apps > jadx: turns Android APKs back into Java > Apktool: take APKs apart and put them back together > Frida: hook into apps while they run > ILSpy: decompiles .NET [03] binary & low-level > radare2: RE framework that lives in your terminal > x64dbg: debugger for Windows > ImHex: hex editor with its own pattern language > angr: symbolic execution engine [04] network & runtime > mitmproxy: sits in the middle and reads the traffic > dnSpy: debug and edit .NET apps > rizin: the radare2 fork > raddebugger: the debugger from Epic Games [05] rebuild & verify > awesome-ai-reverse-engineering: 122 repos, every one graded > awesome-reverse-engineering: curated by the guy who made REA > REA workflows: ready-made investigation prompts, ship with REA > clean-room loop: SPEC.md, oracles and checks until it matches

这套能不能跑通,就看生成的 SPEC.md 靠不靠谱了

spec md is going to cook or get cooked

20 repos in 5 buckets. the useful one is [05] rebuild & verify. that's where you find out if the SPEC.md actually reproduces the binary behavior or just sounds confident. which repo has the diff harness?

It's about time people start cloning paid browser extensions. No more paywalls behind video downloader helper.

@0xDeniAi watch out for file permissions & sandboxing. People often ignore them and end up with messy security issues.

This isn't just reverse engineering anymore; it’s digital archaeology at warp speed. We’ve officially moved from "AI writing simple code" to "AI waking up inside a black box, dissecting its skeleton, and rebuilding it in a clean room." Software security obscurity is officially dead. The compiler is no longer a wall; it’s an open door.

These accounts post so much fake shit cool gfx

Useful information, thanks

Nice

Curious how it handles apps where the heavy lifting (like Uber’s matching/pricing algorithms) happens entirely server-side. Can it reverse-engineer backend logic just from API traffic patterns? The traffic handling alogs and many more?

But can it rebuild Claude ai so I can use it endlessly ? That’s the real question

20 repos is a lot of surface. SPEC.md step is the only bit I care about — does the rebuild verify byte-for-byte or just eyeball it?

this clowns cool if keeping on otherwise narrow but parked city 40 min uphill

This is insane.

😮😮

Lol

binary -> REA -> SPEC.md is a clean pipeline on paper. The rebuild-and-verify step is where these demos usually fall apart — did anyone post a run where the output didn't match?

你这个终端好酷啊 哪里能下载ヽ(゚Д゚)ノ

wow... this is insane

20 repos in a numbered list and zero runs shown. binary -> REA -> SPEC.md is a diagram, not a demo. which one did you actually run end to end?

binary -> REA -> SPEC.md is a clean pipeline shape. the 20 repos is where I'd expect half of them to be unmaintained. did you actually run the chain end to end?

20 repos sorted into analysis core / binary / rebuild-verify and not one of 'em tells me what the accuracy looks like on a stripped binary. 'dangerous' is doing a lot of lifting here.

That’s a serious toolkit. Putting analysis, reverse engineering, and verification together opens up some wild possibilities.

20个repo凑一套RE流程,听着唬人,实际能跑的估计就两层。binary→SPEC那步我之前试过类似的,反编译出来的东西语义丢失严重,最后还是要人肉补。

WOW DANGEROUS HOLY SHIT WOW

i am one of the 99% 🤣

감사합니다

逆向这活儿法律风险比技术风险大十倍,收藏归收藏,真拿去rebuild别人的付费功能迟早要出事😅

20 repos is the easy part. binary -> REA -> SPEC.md only means something if the rebuilt spec actually compiles and runs. is there a verify step that diffs behavior, or is 'rebuild & verify' just a repo name?

20 repos, 5 categories, zero links in the post. file access or it's a list of ideas tbh

Add jev into the team make the powerpuffgirls. Ur welcome 😇

20 repos in 5 buckets. binary -> REA -> SPEC.md. before I wire anything I want to know: does the rebuilt spec diff clean against the original behavior, or do I just get a plausible-looking SPEC?

20 repos, five categories, zero links in the tweet. half this list is probably a fork of someone's weekend project. where's the actual index, I just want to read the binary → SPEC.md step once.
