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

How to map a Windows PE binary's protections and key functions with Seep Reverse Lab

Get architecture, protections, and a function list for a PE file in one agent session.

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

Reverse engineering. Only triage binaries you are authorized to analyze, and keep the samples inside the workspace.

Who it is forA reverse engineer who has received a suspicious or third-party Windows executable and needs a fast first look.

The problemOpening a binary cold means checking architecture, bitness, and protections across several tools before the real analysis can begin.

The outcomeA short summary of architecture, bitness, DEP, ASLR, canary, and PIE status, plus a list of functions and imports to focus on.

What you need first

  • Windows machine with PowerShell (the README's one-click installer is install.ps1)
  • A supported agent such as Claude Code or Codex, or Pi Agent, DeepSeek Harness, or OpenCode
  • Written authorization to test the target application or binary
  • A connected Android device or emulator for Frida-based PoC runs (the demo runs on a connected device)

Steps

  1. Run check.bat once to confirm Radare2 and the knowledge base are ready.
  2. Open the Seep project folder in your agent of choice.
  3. Ask the agent to run the binary info, function list, and summary decompile on the target file.
  4. Read the protections summary and pick the functions the agent flags as most relevant.

Prompt for your agent

Using the seep MCP tools in the Seep Reverse Lab workspace, triage <path-to-pe-file> with seep_r2_info, seep_r2_functions, and seep_r2_decompile in summary mode. Expected output: architecture, bitness, protection flags, and the top functions by interest. Verify that the protection flags match the seep_r2_info output.

Caveat. The README names the Radare2 tools but does not describe the output format, so check the first results against the binary before relying on them.

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