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 command that adds code-obfuscation and anti-analysis techniques to an existing shellcode loader. A shellcode loader is a program that loads and runs shellcode, and these techniques are commonly associated with avoiding detection or analysis.
Generate shellcode loaders by combining components from knowledge base. Creates working C/C++/Rust loaders using documented techniques. Triggers on "generate loader", "create loader", "shellcode loader", "生成loader".
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…
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: