Launched this week
Kong: Agentic Reverse Engineering
The world's first fully-autonomous reverse engineer.
10 followers
The world's first fully-autonomous reverse engineer.
10 followers
Kong is the world's reverse engineering agent. Point Kong at any binary (including stripped and obfuscated binaries), and it will return a fully decompiled output with functional naming, deobfuscation, and explanation for every function, organized by complexity and domain. Currently supports decompiling to C on x86/ARM64 architectures. More support coming via additional triaging and Ghidra extensions.
Congrats on the launch! The fact that it handles stripped and obfuscated binaries is where this gets really interesting.
One thing I'd love to see on the roadmap: some kind of pattern/library fingerprinting layer. Basically before diving into full decompilation, Kong identifies known libraries, crypto implementations, or common frameworks embedded in the binary and labels them. That way you skip re-analyzing code that's just statically linked OpenSSL or zlib and focus on the actual custom logic.
Either way, this looks like a massive time saver. Nice work!
Also, the game preservation use case here is huge. Projects like the Mario 64 and Zelda OoT decompilations took communities thousands of hours to produce readable C from old console binaries. Kong could compress that timeline dramatically. Native PC ports of retro games just got way more accessible.
@maks_bilski Thank you so much for the comment!
Yes, a triaging/fingerprinting Rust crate is actually on the way! This would run ahead of Kong and identify language/framework, then use a heuristic/lightweight LLM-based router to point the binary into the decompilation/disassembler tool embedded within Kong for the most efficient analysis. Right now only Ghidra is implemented via Pyghidra bindings, but angr (Capstone+VEX) is on the way, and I'm thinking of a way to integrate Hopper and Radare2. The more the merrier!
The re-analysis optimization you mention is actually a feature already implemented, though extremely minor right know. In `kong/kong/signatures/`, I have an internal "database" (two .jsons) containing standard lib functions, crypto functions, etc. This is super hacky right now but is definitely an optimization I want to build on for the future!