auto-reverse

Plugin auto-reverse from marketplace auto-reverse in waterbili/AUTO_REVERSE. Commands read from the repo's manifest — 26 days ago.

Skills (29)

• auto-reverse-orchestrator

  Fully automated reverse-engineering orchestrator. Given a target (Android APK/AAB/XAPK, web URL, or Windows PE), it drives the end-to-end workflow — fingerprinting → planning the analysis chain → static analysis → dynamic analysis → native deep-dive → result synthesis → reproduction & verification —

• android-re-decompile

  Decompile Android APK, XAPK, JAR, and AAR files using jadx or Fernflower/Vineflower. Reverse engineer Android apps, extract HTTP API endpoints (Retrofit, OkHttp, Volley), and trace call flows from UI to network layer. Use when the user wants to decompile, analyze, or reverse engineer Android package

• android-re-fundamentals

  Android reverse-engineering onboarding and fundamentals. Covers device preparation and rooting (unlock bootloader, flash a clean ROM, Magisk root, real-device vs emulator trade-offs), full environment setup (JDK, adb/fastboot, Frida server/tools, Charles/mitmproxy CA certificates), APK internal stru

• android-unpacking

  Android unpacking/unshelling—use frida-dexdump to dump the DEX released by a hardening packer from memory. Applicable when opening the APK in jadx only shows the packer stub and not the real business code (whole-release packers like Tencent Legu/Bangcle/360 hardening). Trigger scenarios — unpacking,

• apk-acquire

  Fully automatic APK acquisition for Android reversing. Given a package name, it obtains the APK through the first route that works — pull from a connected adb device, use a local file, or download from APKPure's direct-link endpoint (XAPK with splits or single APK) — then optionally installs it back

• apktool-decompile

  A complete guide and workflow for decompiling, modifying, and repackaging Android APKs with apktool.

• bilibili-reverse

  Bilibili (Bilibili / B-site) Android API reverse-engineering skill — reconstruct Bilibili's APP-API protection and request signing end to end. Covers the APP-API `sign` parameter (appkey + appSecret + MD5 over sorted params, computed inside libbili.so), the `x-bili-ticket` JWT / GenWebTicket HMAC, t

• frida-hooking

  Comprehensive guide and patterns for writing Frida hook scripts for Android (Java & Native).

• frida-mitm-capture

  Fully automated Android HTTPS capture skill built on Frida + mitmproxy. Injects an SSL bypass script via attach mode (defeating conscrypt / OkHttp CertificatePinner / NetworkSecurityConfig) and forwards traffic to mitmproxy over adb reverse USB forwarding, saving it as JSONL. Use cases: (1) capturin

• jadx-reverse-engineering

  Patterns and workflows for using JADX MCP to reverse engineer Android applications.

• mitm-capture

  A mitmproxy-based tool for capturing mobile-app network traffic, detecting encrypted parameters, and analyzing APIs.

• objection-runtime

  Use objection (a Frida-based runtime mobile exploration tool) for one-command runtime analysis of Android apps—SSL pinning bypass, root/debugger detection bypass, in-memory class and method enumeration, heap object search and invocation, keystore/filesystem browsing, and runtime hooking, all without

• ios-app-re

  iOS app reverse-engineering automation skill. Onboard the device (jailbreak/TrollStore/re-sign) → decrypt/dump the binary → class-dump/binary analysis → Frida dynamic (SSL unpin/jailbreak-detection bypass/keychain) → re-sign and deploy, using iOS tools from the catalog throughout (fetch on demand if

• capa-triage

  Use capa (Mandiant) + FLOSS to perform capability triage and string deobfuscation on native libraries (.so / ELF) and executables—before diving into IDA/Ghidra decompilation, automatically identify what capabilities a binary has (crypto/network/anti-debug/anti-analysis/file operations) and recover o

• ghidra-reverse-engineering

  Use Ghidra (the free NSA reverse-engineering framework) + GhidraMCP to analyze Android native libraries (.so) and JNI interfaces—via MCP, let Claude drive Ghidra directly to do decompilation, cross-references, function renaming, string/constant search, and P-code dataflow analysis; plus batch analys

• ida-reverse-engineering

  Workflows and patterns for using IDA MCP and idat (headless) to analyze Android native libraries and JNI interfaces.

• jni-env-patching

  Methodology for stubbing out the JNI environment when emulating an Android SO with unidbg. When native code calls back into the Java layer via JNI to obtain data (device info, credentials, system properties, etc.) and raises an UnsupportedOperationException or a [JNI] unhandled error, follow the pri

• unidbg-emulation

  Guide to emulating Android SO files with Unidbg. Use the JVM-based unidbg framework to locally emulate Android ARM32/ARM64 .so files for reverse engineering, algorithm extraction, signature generation, and reconstructing Java/Native call chains. Covers project structure (unidbg-android/unidbg-api/ba

• akamai-reverse

  Akamai Bot Manager (BMP / Bot Manager Premier) reverse-engineering skill — an end-to-end methodology from traffic-capture fingerprinting to generating server-accepted sensor_data / akamai-bm-telemetry and obtaining a valid _abck cookie. Covers the roles of the four cookie types _abck / bm_sz / ak_bm

• castle-reverse

  Castle.io (io.castle.android / "Highwind" engine, and the web castle.browser.js) anti-bot reversing — recover how the X-Castle-Request-Token + __cuid (x-castle-client-id) are generated, and reproduce them with an offline generator. Covers the Android native-Java SDK (v3.1.1, fully reversed: hex-asse

• cdp-browser

  Drive a real Chrome browser via CDP (Chrome DevTools Protocol) for web automation, reverse-engineering, and information gathering. No webdriver fingerprint, does not trigger anti-bot defenses. Use cases: (1) website reverse-engineering (capturing APIs, analyzing JS, intercepting network requests); (

• env-supplement-proxy

  Use an ES6 Proxy recursive wrapper + access logging for "automatic environment supplementation / automatic environment disclosure"—wrap globalThis/window/navigator/document in a recursive Proxy, trap get/set/has/getOwnPropertyDescriptor/deleteProperty, record every "accessed but undefined" path, and

• js-trace-engine

  Generic dynamic instrumentation / trace engine for heavily-obfuscated anti-bot JavaScript. Takes ANY obfuscated JS, weaves Babel AST probes (function enter/exit, variable assignments, member reads), recursively re-instruments every runtime-generated string (eval / new Function / string setTimeout) s

• jsrpc-universal

  JsRpc "kill-all" (Remote Procedure Call / RPC) technique — expose the JS or native algorithm functions inside an already-loaded real page/App via WebSocket/HTTP RPC, so Python can remotely invoke the algorithm in its real environment, eliminating the need to extract code, mock the environment, or re

• node-bridge-build

  Build an "environment-patching" fallback bridge for anti-bot SDKs (e.g. PerimeterX / Akamai / similar vendors) using jsdom + 11 env-patching modules + a Python curl_cffi coordinator, without relying on a real browser. Trigger scenarios: (1) a pure-algorithm generator temporarily breaks because the S

• px-reverse

  PerimeterX / HUMAN Security SDK reverse-engineering skill — an end-to-end workflow from packet capture to generating _px3/_px2 cookies. Includes 9 algorithm modules (payload/PC/OB/SID/UUID/anti-tamper/hash/memory/ns), CLI tool scripts, a cross-version location manual, a 27-entry OB handler shape-mat

• ruishu-reverse

  Ruishu (Rivers Security) anti-bot pure-algorithm reversing — Cookie T generation + URL suffix handling

• web-api-analyzer

  Analyze website API endpoints and JS logic using Playwright. Intercept network requests, extract API patterns, capture encrypted parameters, and export HAR files. Use when the user wants to reverse-engineer a website's API calls, analyze request/response patterns, or understand JS encryption logic.

• windows-pe-re

  Windows PE reverse-engineering automation skill (.exe/.dll/.sys). Fingerprint/packer-and-language detection → route by type (.NET decompile / native decompile / unpack) → dynamic debugging → deobfuscation → capability triage, using Windows tools from the catalog throughout (fetch on demand if missin