DEDUPEDWhat do you want to do?
4 use cases
-
Audit an app feature gate for CWE-602 authorization flaws
Decide whether a client-side premium or feature check is local or enforced by the server.
- Seep Reverse Lab
- Claude Code
- Codex
- Security and science
- Intermediate
View prompt
Using the Seep Reverse Lab workspace, audit the premium check in <path-to-apk> for CWE-602 authorization issues, but only for the app I am authorized to test. Expected output: a short report that says whether the gate is local or server-authoritative, with the evidence. Verify that the airplane-mode confirmation was run and recorded.
-
Map a Windows PE binary's protections and key functions
Get architecture, protections, and a function list for a PE file in one agent session.
- Seep Reverse Lab
- Claude Code
- Codex
- Security and science
- Intermediate
View prompt
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.
-
Map an APK's control flow without flooding the agent context
Decompile an Android APK to a control-flow skeleton to save tokens during analysis.
- Seep Reverse Lab
- Claude Code
- Codex
- Security and science
- Intermediate
View prompt
Using the Seep Reverse Lab workspace, triage <path-to-apk> and decompile it with seep_apk_decompile in fold mode. Expected output: a control-flow skeleton listing the main classes and their branches. Verify that the skeleton covers the classes the app's main activity calls.
-
Generate a Frida verification hook that fixes its own errors
Create a Frida hook script for an APK and let the agent retry failed runs up to three times.
View prompt
Using the Seep Reverse Lab workspace, generate a Frida hook for <class-name> in <path-to-apk> with seep_apk_gen_hook and run it on the connected device. Expected output: hook_verify.js and the captured stdout. Verify that the run stops after three attempts if it does not succeed.
How to use Seep Reverse Lab
- Check you have what it needs: 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.
- Open angusdevgo/Seep-Reverse-Lab on GitHub and read the README and license.
- Double-click check.bat to confirm the Seep workspace health before starting.
- Open the Seep project folder in Claude Code or Codex so the agent loads the project instructions.
- Give the agent the APK path and the feature name you are authorized to audit.
- Review the decompiled control-flow skeleton and the knowledge base match the agent reports.
These steps come from our top use case, Audit an app feature gate for CWE-602 authorization flaws, which also has a copy-paste agent prompt.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeSeep Reverse Lab alternatives · Best AI repos for Security and science
About this repo
- Who it is forWritten for security auditors and reverse engineers who work with an AI agent and need authorized, evidence-backed checks of client-side app behavior.
- Why it is hot
- LanguageLua
- Sourcegithub.com/angusdevgo/Seep-Reverse-Lab · Back to Hot repos
Requirements
- 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)
Maintain Seep Reverse Lab? Add the Featured on Deduped badge
Paste this into your README:
[](https://dedupedai.com/use-cases/angusdevgo-seep-reverse-lab/?ref=badge)
Questions about Seep Reverse Lab
What is Seep Reverse Lab?
Seep Reverse Lab is a Lua-based, agent-driven workbench that wraps reverse engineering tools (Radare2, JADX, Apktool, Frida) and runs CWE-602 client-side authorization audits. It is an open-source project on GitHub: https://github.com/angusdevgo/Seep-Reverse-Lab.
Who is Seep Reverse Lab for?
Written for security auditors and reverse engineers who work with an AI agent and need authorized, evidence-backed checks of client-side app behavior.
What can I do with Seep Reverse Lab?
4 use cases so far, for example: Audit an app feature gate for CWE-602 authorization flaws; Map a Windows PE binary's protections and key functions; Map an APK's control flow without flooding the agent context. Each has steps and a copy-paste agent prompt.
What do I need to run Seep Reverse Lab?
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).
What are alternatives to Seep Reverse Lab?
Other hot AI repos in Security and science: Rea, Reverify, Ablation, Claude AD, Awesome Reverse Engineered.
Is Seep Reverse Lab safe to run?
Deduped does not own, audit or vouch for it. Read the README and license, run it on your own systems first and review every command before you run it.