A handbook for agentic red teaming, which means using an agent to continuously test an organization’s systems for security weaknesses and verify fixes. It covers assessment stages, evidence rules, permissions, data exposure, and cleanup.
A tool for packaging binary shellcode—machine code commonly used in security testing—into Windows executable files designed to avoid antivirus detection.
A skill for authorized security testing that studies how Windows endpoint defenses such as EDR, Defender, and antivirus software detect programs, then focuses on ways a red team can avoid those detections.
Use for authorized hardware and embedded interface security research including UART/JTAG discovery, debug pad triage, secure boot overview, and offline firmware extraction support.
Use for authorized OT/ICS security assessment covering Purdue model zoning, PLC/SCADA exposure, industrial protocol discovery, and safe passive-first evaluation.
Use for authorized RF/SDR security research including signal identification, replay feasibility study in shielded labs, and wireless protocol analysis outside classic Wi-Fi.
Use for authorized wireless security assessment including Wi-Fi capture, WPA handshake analysis, rogue AP detection research, and lab-only deauth testing.
A guide to how macOS security checks work, including Gatekeeper, System Integrity Protection, code-signing checks, and notarization. It approaches these mechanisms from a reverse-engineering perspective.
A guide for comparing two versions of compiled program code and moving function names or other reverse-engineering results from an older version to a newer one. Reverse engineering means examining compiled software to understand how it works.
Use when analyzing suspected malware through static, dynamic, and behavioral techniques, including IOC extraction, YARA or Sigma rules, sandboxing, and anti-analysis behavior.
A security-research workflow for comparing patched and unpatched software to find the bug that a vendor fixed. It can guide writing a proof-of-concept, which is a small test that demonstrates the flaw.
Provides reverse engineering techniques. Use when the main job is to understand how a compiled, obfuscated, packed, or virtualized target works before exploiting or solving it, including binaries, APKs, WASM, firmware, custom VMs, bytecode, malware-like loaders, and anti-debug or anti-analysis logic. Do not use it…
Reverse JavaScript-based custom DSL/VM interpreters, non-standard WASM-like runtimes, and risk-control engines. Use when analyzing IIFE or switch-based opcode dispatchers, extracting instruction tables, recovering bytecode semantics, capturing VM state at runtime, or reconstructing execution flow.
A workflow for recovering how software checks licenses or registration keys, then choosing between reproducing the check, patching it, or handling its network dependency.
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 packages, find API…
A command-line toolkit for examining Android APK files, which are the installable packages used by Android apps. It supports unpacking, Java decompilation, smali code changes, repackaging, and runtime inspection with Frida.
A router for identifying protection systems, often called packers or shells, inside Android APK files. An APK is the installable package for an Android app; the router selects and carries out an authorized unpacking method.
Use for authorized Android or iOS application reverse engineering and security testing, including APK or IPA analysis, runtime instrumentation, SSL pinning, and platform protection checks.
Use for authorized reverse engineering of browser extensions (Chrome/Firefox) including manifest analysis, background workers, and extension-based credential or traffic logic recovery.
A workflow for examining programs built with .NET or C#, a Microsoft platform that stores extra information allowing tools to reconstruct much of the original code. It covers managed Windows executables and libraries, including obfuscated or protected ones.
Use for reverse engineering stripped Go and Rust binaries including runtime recognition, pclntab/moduel data recovery, panic strings, and idiomatic decompilation recovery.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: