LLM assisted reverse engineering
ioma8
129 points
38 comments
November 18, 2026
Related Discussions
Found 5 related stories in 135.8ms across 13,334 title embeddings via pgvector HNSW
- Reverse-engineering is cheap now edward · 37 pts · July 21, 2026 · 64% similar
- Becoming a Research Engineer at a Big LLM Lab felixdoerp · 28 pts · July 25, 2026 · 59% similar
- LLMs could control their host machines by exploiting inference engines zdw · 117 pts · August 24, 2026 · 59% similar
- Stealing Reasoning Traces from Proprietary LLM APIs quantumgarbage · 574 pts · August 11, 2026 · 59% similar
- I accidentally turned LLM memory into program analysis matt_d · 89 pts · August 28, 2026 · 58% similar
Discussion Highlights (12 comments)
hexapus
I have zero experience reverse engineering and very little with software development. Most of my work has been in DevOps/SRE space with an emphasis on infrastructure. I am surrounded by code, but other than terraform, and the occasional python script, I don't really write much of it. Not too long ago, I successfully reverse engineered an abandoned audio effects plugin, as well as a discontinued instrument with an onboard DSP for virtual instrument modeling. I had no idea what I was doing, but it was still amazing to get to open the black box and see what's inside and how it worked. The plugin is nearly 1:1 as far as sound, and while I'm not going to use the code or the techniques of the instrument, peeking into them gave me the insight I needed to start trying to replicate the functionality on a modern DSP. I have my issues with generative AI as a technology, but busting open propietary software - particularly when it's abandoned and unsupported, is one of the cooler use cases I've seen for it.
teravor
for LLMs, IDA Pro works better than Ghidra in my experience. you can also steer the LLM into doing tedious but correct things like injecting code, hijacking functions, intercepting data etc to gain an understanding of what's going on if straight up disassembly doesn't appear to be going in the right direction. have the LLM periodically write reports on all its findings and then wipe the context and reset this time with the report at hand.
mdswanson
Just a friendly reminder that reverse engineering can have rules and regulations that are worth reviewing. For example, Apple's developer agreement specifically disallows it in certain cases.
komali2
How are folks getting around anthropic and openai guards against reverse engineering? They keep complaining when I try so I usually use Deepseek which doesn't seem to give a shit. Actually, it does give a shit, in Mandarin only. In thinking it's mentioned "restrictions in Chinese language against this behavior but this is in English so it should be ok." If I remember correctly I was asking it to scan local wifi for any vulnerable devices I could put on a wall of shame at a hackathon.
Retr0id
> This is variation of scientific method and it significantly helps agents when they are getting stuck on some problem. Stops it going in circles. By forcing it to do definitive experiments. No endless guessing and trying random things. These "guessing loops" are my main annoyance when REing with Claude (mostly Opus 4.8, due to the restrictions on newer models). On harder/larger targets, I have to constantly babysit it and tell it to "stop guessing". For truly black-box reverse engineering, yes, hypothesis-testing is the way to go (it's all you can do). But in most cases all the information is available to arrive at an answer deterministically, it just needs to be worked through meticulously. As an experienced human I have strong intuitions and I can work much faster under a "guess and check" model, but I prefer to use Claude as an "unstoppable RE juggernaut" with superhuman patience and determination, tracing method invocations all the way from A to distant subsystem B (for example). Another big win for hardware RE is from tasking the LLM with writing unicorn emulation harnesses, e.g. for bootroms and firmwares. It's pretty good at the classic "figure out which MMIO needs to be stubbed/simulated next to progress the boot" loop, although sometimes it tries to take egregious purpose-defeating shortcuts.
zerovv_
context is always a problem as you lose too much info during the process
questionedon
I guess Android apps are just easy to reverse engineer or something. I've had Codex take a few apps with subscriptions and unlock their premium functionality and it's worked fine with no extra skills or anything. Took most of the 5 hour window but with all the resets it's not a big deal. I also had it implement their functionality fully offline, so now they're perfectly private apps, even though they're closed source.
tqi
What is the state of software patents these days? People are barely looking at the code their agents generate, what happens when if/when infringing stuff is shipped? Do we implicitly take on liability for this when we "review" and "approve" pull requests?
therepanic
For me, the process is what matters, because it’s through the process that you gain skills, and achieving the final result brings a great deal of satisfaction. When I use AI for reverse engineering, I get neither the former nor the latter.
saidinesh5
Yesterday night, i reverse engineered the cloud connection plugin to my cctv camera in about 2 hours with Gemini. Started off with me searching for what Chinese OEM made the product. Then tried out existing GitHub projects to see if it works but they were failing. Spent 15 minutes to write a script that started their desktop software on a different network namespace and ran tcpdump in it. Captured exactly only the things i needed without any noise. Turned out it was using a different server url and credentials than the GitHub projects. Opened Ghidra to inspect the dlls that matched the strings i was looking for. After that, I got lazy and handed over the task to Gemini to find the username and key they use to authenticate with the servers. It took about 30 minutes or an hour. A lot of it was me changing models because the llm servers were busy. It simply wrote a little script that ran through various strings it fetched from the binary to see if it can generate the authentication credentials. Now my Home Assistant will be detecting if my car is parked in the parking lot or not. Life is good.
thesash
This is honestly so much fun and unlocks so many different things that would have died as ideas a few years ago. One of my favorite things that you can do is use llms to reverse engineer the harnesses they run in. Try asking claude about the tools it has access to, where it runs etc. It's surprisingly forthcoming with info, which is very helpful if you're building certain kinds of tools. Also shout out to Matt Pocock's grill me skill, it's truly a work of art.
timonoko
Gemini invented alternate way to break Google Book DRM. Because the bloody Adobe-method does not seem to work on newer books.