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

How to check an AI's claims about a binary before trusting them with Reverify

Turn an AI's guesses about a binary into VERIFIED or REFUTED verdicts with evidence.

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

Reverse engineering. The README says Reverify is for authorized reverse engineering only, such as malware analysis, CTF, interoperability research, and software you own or are permitted to analyze.

Who it is forA reverse engineer or security analyst who has asked an AI to describe a function, struct, or offset in a binary and needs to know which claims are real.

The problemLanguage models confidently invent offsets, sizes, and function behavior when reading binaries, and there is no easy way to tell which statements are true.

The outcomeEach claim is returned as VERIFIED, REFUTED, or INCONCLUSIVE with the bytes the tools observed, and only verified claims are kept.

What you need first

  • Python installed
  • Install with pip install reverify
  • A binary or source file you are authorized to analyze

Steps

  1. Run pip install reverify to install the CLI and MCP server.
  2. Run reverify auto sample.bin --json to get the tool-derived view of the file.
  3. Write each AI claim as a JSON object, for example kind instructions with an offset and a list of mnemonics.
  4. Run reverify verify sample.bin --claim '{"kind": "instructions", "offset": 4096, "mnemonics": ["push", "mov", "sub"], "note": "function prologue"}' and read the verdict. (inferred, check the README)
  5. For many claims, save them to claims.json and run Reverify verify with --claims-file, then check the exit code, which is non-zero if anything is refuted.

Prompt for your agent

Using the reverify repo at 2akouwu/reverify, check each claim you made about <target binary> with reverify verify and its --claim JSON format. Report each claim as VERIFIED, REFUTED, or INCONCLUSIVE with the evidence bytes, and do not state any claim as fact unless the tool returned VERIFIED.

Caveat. The README reports its benchmark numbers on Windows system files, so accuracy on other binaries is not promised by the README.

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