DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to reuse confirmed findings on a new binary with Ablation

Replay stored finding descriptions and successful queries against a later target.

Authorization notice. Ablation is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.

Reverse engineering. Reusing vulnerability patterns across products should stay within the scope of software you are authorized to analyze.

Who it is forA researcher who has already analyzed one firmware product and now has a related product from a different vendor.

The problemPatterns found in the first target have to be rediscovered by hand on each new binary.

The outcomeStored finding descriptions and search queries are replayed on the new target, producing candidate matches to verify.

What you need first

  • A local clone of the Ablation repository at ~/ablation, as the README's launch step assumes
  • Claude Code or Codex installed and signed in with model access
  • A binary, firmware image, or source repository you are authorized to analyze
  • Familiarity with reverse engineering concepts such as ELF, callgraphs, and taint tracking

Steps

  1. Run cd ~/ablation && claude to start a session.
  2. Run /model claude-sonnet-4-6 to set the model.
  3. Ask the agent to replay stored confirmed findings and successful semantic queries against <new binary path>.
  4. Ask the agent to list each match with the stored finding it came from.

Prompt for your agent

In the Ablation repo at ~/ablation, replay the stored confirmed finding descriptions and successful semantic queries against <new binary path>. Output each candidate match with the source finding it came from and a similarity note. Verify that every candidate is checked in the disassembly before it is reported as a finding.

Caveat. The README says findings and queries persist between sessions, so this use case only works after you have already built up a stored library from earlier analyses.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page