Back Original

LLM assisted reverse engineering

I have been hacking both hardware and software for 2 decades. Previously manually. But in 2026 with the help of AIs the proccess is greatly sped up. Below I will describe my proccess briefly or how I do it.

Set Up

Tools which I mostly use are these:

Process

What I basically do nowadays is just point the agent at the binary to be analysed and use my set of dedicated agent skills. Rest usually takes care of itself. But putting the skills besides, the flow is basically this.

  1. Find binary type, platform, build etc - based on this using appropriate decompiler (note - current AIs do fairly well with just disassembly . ie pure x86 or ARM instructions).
  2. Command agent to document all findings along the way to MD files. This serves several purposes. They become notes for your own understanding. They help the agent not lose the track after compaction / handoff to different agent. And last but not least, it helps the agent work more effectively, not get lost in circles etc. More about this later.
  3. Ask the agent to analyse basic structure. Main functions, main branching, imported functions etc of given binary. By binary I mean whatever. Desktop executable, website or firmware image.

Once I have this basic overview I can usually proceed any way I need to do modifications to the original binary or build mods or just help me understand it better.

On some occasions some things are not easily resolvable by simple disassembly or decompilation. In those cases you can do:

SKILLS

Here are some of my major skills I use frequently.

Matt Pottock - Grill me

It gives you several questions when your input might be valuable. I usually use it with this prompt:

text
Use skill /grill-me to ask me up to 5 questions
whose answers are crucial for your further progress.
Ask only one question at a time.

mattpocockskillsShellSkills for Real Engineers. Straight from my .agents directory.Open repo Opens in a new tab.

Ghidra / other RE tooling skill

It helps a ton to have a skill where your specific reverse engineering tooling is described. Ie to use radare2 or kuna. Or description of how to use the MCP Ghidra bridge and for what. Without such a skill, agents often give up too quickly getting lost, not knowing how to do the actual disassembly / decompilation.

ioma8ghidra-decompile-skillJavaAgent skill + 22 Ghidra scripts for fast targeted decompilation, and the fix for GhidraMCP extension/Ghidra version mismatches.Open repo Opens in a new tab.

Hypothesis debugging

That is also my own skill. Its related to how I wrote earlier how important it is to make the agent document everything into MD files. This skill forces agent who is getting stuck to follow this loop:

  1. Make a hypothesis of why / how something works. Write it down into CSV table of hypotheses, saved on disc.
  2. Design experiment (probe, logging, ...) which will definitively prove or disprove this hypothesis.
  3. Record the result.
  4. Repeat.

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. This one is crucial in my opinion. I made it public too, so other can benefit from it.

ioma8hypothesis-debuggingAgent skill for hypothesis-driven debugging — one testable hypothesis at a time, logged and validated in a CSV loop.Open repo Opens in a new tab.

Implementation of hacks and probes

For implementing anything I basically go for 2 toolings.

  1. Python but with UV tooling. UV tooling allows to make custom envs super quickly and portably. Also allows to make single-file, inline dependencies scripts. Python is great for prototyping or quickly making probes or even decompilation helpers.
  2. Rust for actual implementation of given hack. Whenever it is possible I am using rust for this. It has many reasons but he two main are:

My hacking successes

With the AI assisted reverse engineering I was able to achieve such crazy reverse engineering succeses, in the last 6 months, which would take me years each on its own, if done by hands.

Sometimes its a thin boundary between reverse engineering and software development. Sometimes you just decipher the proprietary save file format of the ugly paid app and then move into the clean software development phase of building your new, totally unique editor, to work with these files. (yes I made custom Photoshop too and its not the ArtCraft suite - I did it about a year before them, just for me).

Final thoughts

Reverse engineering and hacking into old softwares or devices has always been a hobby for me. I understand assembly, I understand hardware. But it was long and tedious process.

With the cheap accesibility to smart LLM tools in these days, this hobby took dramatic turn for me. I do not miss manually analyzing the assembly instructions. But I love quickly getting the results. Yes my long experience helps me steer the agents the correct way. But that is also fun. And I am learning a ton of things along the way.

I wish everyone would try to do some hacks of his own. For me the hobby is driven by curiosity. And LLMs didn't take that away. They gave me turbo boost to my wonderings and explorations. Let's free our minds!