[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DB6HD8MVGGR48K7T6JD541":3,"skill-same:01M7DB6HD8MVGGR48K7T6JD541":45},{"skillNo":4,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M7DB6HD8MVGGR48K7T6JD541","reverse-engineering-tools",null,"alicewe1\u002Falice_skill","alicewe1","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F102134151?v=4","01M7D9STCM8HAESM958JP0989K","Alice_we","01M7D9STDR22MTD9FTTWPAZNV8",64,"GPL-3.0","https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002F_modules\u002Freverse-engineering-tools\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: reverse-engineering-tools\ndescription: Guide for reverse engineering protected games and anti-cheat components across user mode, kernel mode, and hypervisor-aware environments. Use this skill when analyzing drivers, IOCTL protocols, callback registration, injected-code artifacts, integrity checks, protected binaries, or debugging security-sensitive game components.\nx-alice-class: reverse\n---# Reverse Engineering Tools & Techniques\n\n## Overview\n\nThis skill covers reverse engineering workflows for game security research, including protected game clients, anti-cheat user-mode modules, kernel drivers, memory artifacts, and debugging environments that must survive anti-analysis checks.\n\n## README Coverage\n\n- `Cheat > Debugging`\n- `Cheat > RE Tools`\n- `Cheat > Mixed boolean-arithmetic`\n- `Cheat > Dynamic Binary Instrumentation`\n- `Cheat > Fix VMP`\n- `Cheat > Fix Themida`\n- `Cheat > Fix OLLVM`\n- `Cheat > Virtual Environments`\n- `Cheat > Decompiler`\n- `Cheat > IDA themes`\n- `Cheat > IDA Plugins`\n- `Cheat > IDA Signature Database`\n- `Cheat > Binary Ninja Plugins`\n- `Cheat > Ghidra Plugins`\n- `Cheat > Radare Plugins`\n- `Cheat > Windbg Plugins`\n- `Cheat > X64DBG Plugins`\n- `Cheat > Cheat Engine Plugins`\n- `Cheat > ROP Finder`\n- `Cheat > ROP Generation`\n- `Anti Cheat > Anti Debugging`\n- `Anti Cheat > Anti Disassembly`\n- `Anti Cheat > Dump Fix`\n- `Anti Cheat > Sample Unpacker`\n- `Anti Cheat > Obfuscation Engine`\n- `Anti Cheat > Winows User Dump Analysis`\n- `Anti Cheat > Winows Kernel Dump Analysis`\n\n## Debugging Tools\n\n### Windows Debuggers\n- **Cheat Engine**: Memory scanner and debugger for games\n- **x64dbg**: Open-source x86\u002Fx64 debugger\n- **WinDbg**: Microsoft's kernel\u002Fuser-mode debugger\n- **ReClass.NET**: Memory structure reconstruction\n- **HyperDbg**: Hypervisor-based debugger\n\n### Specialized Debuggers\n- **CE Mono Helper**: Unity\u002FMono game debugging\n- **dnSpy**: .NET assembly debugger\u002Fdecompiler\n- **ILSpy**: .NET decompiler\n- **frida**: Dynamic instrumentation toolkit\n\n### Platform-Specific\n- **edb-debugger**: Linux debugger\n- **PINCE**: Linux game hacking tool\n- **H5GG**: iOS cheat engine\n- **Hardware Breakpoint Tools**: HWBP implementations\n\n## Disassembly & Decompilation\n\n### Multi-Platform\n- **IDA Pro**: Industry standard disassembler\n- **Ghidra**: NSA's reverse engineering framework\n- **Binary Ninja**: Modern RE platform\n- **Cutter**: Radare2 GUI\n\n### Specialized Tools\n- **IL2CPP Dumper**: Unity IL2CPP analysis\n- **dnSpy**: .NET\u002FUnity decompilation\n- **jadx**: Android DEX decompiler\n- **Recaf**: Java bytecode editor\n\n## Memory Analysis\n\n### Memory Scanners\n```\n- Cheat Engine: Pattern scanning, value searching\n- ReClass.NET: Structure reconstruction\n- Process Hacker: System analysis\n```\n\n### Dump Tools\n```\n- KsDumper: Kernel-space process dumping\n- PE-bear: PE file analysis\n- ImHex: Hex editor for RE\n```\n\n## Dynamic Binary Instrumentation (DBI)\n\n### Frameworks\n- **Frida**: Cross-platform DBI\n- **DynamoRIO**: Runtime code manipulation\n- **Pin**: Intel's DBI framework\n- **TinyInst**: Lightweight instrumentation\n- **QBDI**: QuarkslaB DBI\n\n### Use Cases\n1. API hooking and tracing\n2. Code coverage analysis\n3. Fuzzing harness creation\n4. Behavioral analysis\n5. Driver IOCTL and callback tracing\n\n### Exception-Driven Lightweight DBI (Trap-and-Emulate)\n```\nConcept:\n- Replace branch instructions with fault-generating sentinel opcodes\n- Catch the resulting exception → emulate the original branch → log → resume\n- Full cycle: patch → fault → capture → emulate → record → restore → continue\n\nSentinel Selection:\n- HLT (0xF4) for ret → triggers STATUS_PRIVILEGED_INSTRUCTION\n- SALC (0xD6) for jmp\u002Fjcc\u002Fcall → triggers STATUS_ILLEGAL_INSTRUCTION\n- Avoids INT3 (0xCC) which anti-debug\u002Fintegrity checks commonly scan for\n- Different sentinels can multiplex branch types\n\nException Capture:\n- Hook KiUserExceptionDispatcher (not VEH\u002FSEH) for lowest-latency interception\n- Assembly stub tail-calls into RtlDispatchException\n- Handler dispatches by exception code to custom emulation logic\n\nBranch Emulation Engine:\n- Disassemble original (pre-patch) instruction at fault RIP\n- jcc: 16-condition lookup table (ZF, SF, CF, OF, PF combinations)\n- Direct call: push return address, update RIP\n- Indirect branch: resolve effective address (register, memory, SIB, RIP-relative)\n- ret: pop return address from stack, handle ret imm16 (extra pop)\n- loop\u002Fjrcxz: decrement RCX, conditional branch\n\nInstrumentation Strategies:\n- Bounded Bulk Patching: scan a window from seed address, patch all branches\n  → Simple but detectable by integrity checks\n- Branch Chasing: patch only current branch, re-instrument at target on fault\n  → Minimal memory footprint, highest stealth, best for unknown binaries\n- CFG-Guided Patching: recursive-descent static CFG + chasing for unreached edges\n  → Best coverage\u002Fsafety balance\n\nIntegrity Check Evasion:\n- PAGE_GUARD + Trap Flag (single-step) instead of direct code patching\n- Trigger guard page exception → set TF → single-step through original instruction\n- Avoids modifying .text section (defeats hash-based integrity checks)\n```\n\n### Control Flow Tracing (CFT) Applications\n```\n- Runtime call graph generation with register context at each edge\n- Divergence testing: compare traces across different inputs\u002Fenvironments\n  → Quickly locates input validation, anti-debug, anti-tamper trigger points\n- Deobfuscation: resolve all indirect branches in virtualized code\n- Hot path analysis, branch coverage measurement\n- Performance: ~600x slowdown (exception per branch), not suitable for\n  timing-sensitive targets (rdtsc checks, session timeouts)\n- Portable to other architectures: ARM (UDF), RISC-V (illegal instruction)\n```\n\n### User-Mode Hypervisor-Assisted Tracing\n```\nConcept:\n- Use Windows Hypervisor Platform (WHP) API to run guest code in user mode\n- No kernel driver required — standard user-mode process hosts the hypervisor\n- Map host memory pages into guest address space\n- Configure page-level traps (read\u002Fwrite\u002Fexecute permissions per page)\n- Guest execution triggers VM exits on configured events\n\nTrap-Driven Execution:\n- Page fault traps: set per-page R\u002FW\u002FX permissions via EPT-equivalent API\n  → Execute fault = code coverage, Write fault = memory write monitoring\n  → Read fault = data access tracking\n- CPUID interception: guest executes CPUID → VM exit → host decides response\n  → Useful for fingerprinting guest environment queries\n- Syscall interception: guest executes syscall → VM exit → host emulates\n  → Controlled experiments without real kernel interaction\n\nWorkflow:\n1. Prepare initial CPU state (registers, segments, control registers)\n2. Map target code + data pages with desired permissions\n3. Enter guest execution loop\n4. On VM exit: inspect reason, handle trap, optionally modify state\n5. Resume or terminate guest\n\nAdvantages:\n- Pure user-mode: no driver signing, no PatchGuard concerns\n- Deterministic: full control over guest memory and execution\n- Composable: combine with disassemblers\u002Femulators for hybrid analysis\n- Debuggable: host process can be debugged normally\n\nLimitations:\n- Requires hardware virtualization support (VT-x\u002FAMD-V)\n- Windows-specific (WHP API is Windows 10+)\n- Cannot run full OS — suited for code snippets and function-level analysis\n- Nested virtualization considerations when host is already a VM\n```\n\n## Anti-Analysis Bypass\n\n### Techniques\n- Anti-debug detection bypass\n- VM\u002FSandbox evasion\n- Timing attack mitigation\n- PatchGuard circumvention\n\n### Tools\n- **TitanHide**: Anti-debug hiding\n- **HyperHide**: Hypervisor-based hiding\n- **ScyllaHide**: Anti-anti-debug plugin\n\n## Game-Specific Analysis\n\n### Unity Games\n1. Locate `GameAssembly.dll` (IL2CPP) or managed DLLs\n2. Use IL2CPP Dumper for structure recovery\n3. Apply dnSpy for Mono games\n4. Hook via Unity-specific frameworks\n\n### Unreal Engine Games\n1. Identify UE version from signatures\n2. Use SDK generators (Dumper-7)\n3. Analyze Blueprint bytecode\n4. Hook UObject\u002FUFunction systems\n\n### Native Games\n1. Standard PE analysis\n2. Import\u002Fexport reconstruction\n3. Pattern scanning for signatures\n4. Runtime memory analysis\n\n## Workflow Best Practices\n\n### Initial Analysis\n```\n1. Identify protections (packer, obfuscator, anti-cheat)\n2. Determine game engine and version\n3. Collect symbol information if available\n4. Map out key modules, callbacks, and trust boundaries\n```\n\n### Deep Analysis\n```\n1. Locate target functionality\n2. Trace execution flow\n3. Document structures, memory artifacts, and relationships\n4. Correlate IOCTLs, callbacks, and runtime checks\n```\n\n## Obfuscation Taxonomy\n\n### Mixed Boolean-Arithmetic (MBA)\n```\n- Linear MBA: e.g., x + y = (x ^ y) + 2*(x & y)\n- Polynomial MBA: higher-degree expressions over boolean\u002Farithmetic mix\n- Tools: SSPAM, MBA-Blast, SiMBA for simplification\n- Common in: VMProtect, Themida, custom LLVM passes\n```\n\n### Control Flow Flattening (CFF)\n```\n- OLLVM-style: all basic blocks behind a dispatcher switch\n- Recovery: symbolic execution, pattern matching, deobfuscation passes\n- Tools: D-810 (IDA), de-ollvm scripts, SATURN\n- Variants: nested dispatchers, encrypted state variables\n```\n\n### Opaque Predicates\n```\n- Invariant conditions injected to confuse static analysis\n- Number-theoretic (x² mod 4 ∈ {0,1}), pointer-aliasing based\n- Detection: abstract interpretation, SMT solvers (Z3)\n```\n\n### Virtualization-Based Obfuscation\n```\nVMProtect \u002F Themida \u002F Code Virtualizer:\n- Custom bytecode VM with randomized opcode set per build\n- Handler table dispatch loop: fetch → decode → execute\n- Devirtualization approaches:\n  - Trace-based: record handler execution, lift to IR\n  - Pattern-based: identify handler semantics by structure\n  - Symbolic: concolic execution through VM dispatch\n- Tools: VMPAttack, NoVmp, Oreans UnVirtualizer, vtil\n```\n\n### Binary Lifting\n```\n- Lift machine code to compiler IR (LLVM IR, VEX, ESIL)\n- Enables compiler-level optimization passes for deobfuscation\n- Tools: McSema, remill, RetDec, Binary Ninja MLIL\u002FHLIL\n```\n\n## Disassembler Plugin Ecosystem\n\n### IDA Pro Plugins\n```\nCategories found in README (> IDA Plugins, 150+ entries):\n- Decompiler enhancers: HexRaysPyTools, HRDevHelper\n- Type recovery: ClassInformer, auto_struct\n- Signature: FLIRT, Lumina, IDA Signature Database\n- Scripting: IDAPython, IDC, LazyIDA\n- Visualization: IDAGraph, Lighthouse (coverage)\n- Anti-obfuscation: D-810 (MBA), de-ollvm, Patfinder\n- Game-specific: SDK loaders, structure importers\n```\n\n### Binary Ninja Plugins\n```\n- Sidekick, snippets, type libraries\n- HLIL-based analysis scripts\n- Custom architectures and loaders\n- Headless analysis for batch processing\n```\n\n### Ghidra Plugins\n```\n- GhidraScript (Java\u002FPython), Ghidra extensions\n- Ghidraaas (Ghidra-as-a-Service)\n- Type importers, signature matchers\n- Firmware analysis (SVD loader, embedded)\n```\n\n### Radare2 \u002F iaito Plugins\n```\n- r2pipe scripting (Python, JS, Rust)\n- iaito: official radare2 Qt GUI\n- r2ghidra: Ghidra decompiler integration\n- r2dec: lightweight decompiler\n```\n\n### WinDbg Plugins\n```\n- SwishDbgExt, WinDbgX\n- Time Travel Debugging (TTD) extensions\n- !analyze extensions, custom formatters\n- Kernel debugging helpers\n```\n\n### x64dbg Plugins\n```\n- ScyllaHide (anti-anti-debug)\n- TitanEngine, x64dbgpy\n- Trace plugins, pattern scanners\n- Conditional breakpoint scripts\n```\n\n### Cheat Engine Plugins\n```\n- Mono\u002FIL2CPP helpers\n- Auto-assembler templates\n- Structure dissectors\n- Pointer scanner extensions\n```\n\n## MCP-Based RE Tools\n\n```\nThe README's MCP server section and RE tool ecosystem now include\nAI-assisted reverse engineering through Model Context Protocol:\n\n- IDA MCP: AI agent controls IDA Pro (rename, annotate, navigate)\n- Ghidra MCP: AI agent queries Ghidra decompilation and PCODE\n- Binary Ninja MCP: AI agent interacts with Binary Ninja API\n- radare2 MCP: AI agent drives r2 sessions via r2pipe\n- x64dbg MCP: AI agent controls live debugging sessions\n\nWorkflow: LLM ↔ MCP server ↔ RE tool, enabling natural-language\nqueries like \"find all functions calling CreateRemoteThread\" or\n\"rename this function based on its decompiled logic\"\n```\n\n## Binary Diffing\n\n```\nTools for comparing binary versions (patch analysis, vulnerability research):\n- BinDiff (Google): graph-based structural comparison\n- Diaphora: IDA plugin, best open-source binary diff\n- ghidriff: Ghidra-based diffing, command-line and scriptable\n- DarunGrim: patch analysis focused differ\n- turbodiff: lightweight IDA diffing plugin\n\nUse cases in game security:\n- Tracking anti-cheat driver updates between versions\n- Identifying patched vulnerabilities in game clients\n- Comparing obfuscated builds to isolate logic changes\n```\n\n## Anti-Debug Techniques Catalog\n\n### User-Mode Anti-Debug\n```\n- IsDebuggerPresent \u002F CheckRemoteDebuggerPresent\n- NtQueryInformationProcess (ProcessDebugPort, ProcessDebugFlags, ProcessDebugObjectHandle)\n- NtSetInformationThread (ThreadHideFromDebugger)\n- PEB.BeingDebugged, PEB.NtGlobalFlag, heap flags\n- INT 2D, INT 3 scanning, OutputDebugString tricks\n- Timing checks: rdtsc, QueryPerformanceCounter, GetTickCount64\n- TLS callbacks for early detection\n- Exception-based: unhandled exception filter, VEH chain inspection\n- Parent process checks (csrss.exe verification)\n- Self-debugging: NtCreateDebugObject\n```\n\n### Kernel-Mode Anti-Debug\n```\n- KdDebuggerEnabled \u002F KdDebuggerNotPresent\n- Debug register (DR0-DR7) monitoring and clearing\n- KPROCESS.DebugPort zeroing\n- NMI callbacks for debugger detection\n- Hardware breakpoint detection via context inspection\n```\n\n### Anti-Debug Bypass Tools\n```\n- ScyllaHide: comprehensive anti-anti-debug (x64dbg\u002FIDA\u002Fstandalone)\n- TitanHide: kernel-mode debugger hiding\n- HyperHide: hypervisor-based anti-debug bypass\n- SharpOD: OllyDbg anti-anti-debug plugin\n```\n\n## VMProtect\u002FThemida Analysis\n\n### Resources\n- Devirtualization tools\n- Control flow recovery\n- Handler analysis techniques\n- Unpacking methodologies\n\n## ROP\u002FExploit Development\n\n### Tools\n- **ROPgadget**: Gadget finder\n- **rp++**: Fast ROP gadget finder\n- **angrop**: Automated ROP chain generation\n\n---\n\n## Data Source\n\n**Important**: This skill provides conceptual guidance and overview information. For detailed information use the following sources:\n\n### 1. Project Overview & Resource Index\n\nFetch the main README for the full curated list of repositories, tools, and descriptions:\n\n```\nhttps:\u002F\u002Fraw.githubusercontent.com\u002Fgmh5225\u002Fawesome-game-security\u002Frefs\u002Fheads\u002Fmain\u002FREADME.md\n```\n\nThe main README contains thousands of curated links organized by category. When users ask for specific tools, projects, or implementations, retrieve and reference the appropriate sections from this source.\n\n### 2. Repository Code Details (Archive)\n\nFor detailed repository information (file structure, source code, implementation details), the project maintains a local archive. If a repository has been archived, **always prefer fetching from the archive** over cloning or browsing GitHub directly.\n\n**Archive URL format:**\n```\nhttps:\u002F\u002Fraw.githubusercontent.com\u002Fgmh5225\u002Fawesome-game-security\u002Frefs\u002Fheads\u002Fmain\u002Farchive\u002F{owner}\u002F{repo}.txt\n```\n\n**Examples:**\n```\nhttps:\u002F\u002Fraw.githubusercontent.com\u002Fgmh5225\u002Fawesome-game-security\u002Frefs\u002Fheads\u002Fmain\u002Farchive\u002Fufrisk\u002Fpcileech.txt\nhttps:\u002F\u002Fraw.githubusercontent.com\u002Fgmh5225\u002Fawesome-game-security\u002Frefs\u002Fheads\u002Fmain\u002Farchive\u002F000-aki-000\u002FGameDebugMenu.txt\n```\n\n**How to use:**\n1. Identify the GitHub repository the user is asking about (owner and repo name from the URL).\n2. Construct the archive URL: replace `{owner}` with the GitHub username\u002Forg and `{repo}` with the repository name (no `.git` suffix).\n3. Fetch the archive file — it contains a full code snapshot with file trees and source code generated by `code2prompt`.\n4. If the fetch returns a 404, the repository has not been archived yet; fall back to the README or direct GitHub browsing.\n\n### 3. Repository Descriptions\n\nFor a concise English summary of what a repository does, the project maintains auto-generated description files.\n\n**Description URL format:**\n```\nhttps:\u002F\u002Fraw.githubusercontent.com\u002Fgmh5225\u002Fawesome-game-security\u002Frefs\u002Fheads\u002Fmain\u002Fdescription\u002F{owner}\u002F{repo}\u002Fdescription_en.txt\n```\n\n**Examples:**\n```\nhttps:\u002F\u002Fraw.githubusercontent.com\u002Fgmh5225\u002Fawesome-game-security\u002Frefs\u002Fheads\u002Fmain\u002Fdescription\u002F00christian00\u002FUnityDecompiled\u002Fdescription_en.txt\nhttps:\u002F\u002Fraw.githubusercontent.com\u002Fgmh5225\u002Fawesome-game-security\u002Frefs\u002Fheads\u002Fmain\u002Fdescription\u002Fufrisk\u002Fpcileech\u002Fdescription_en.txt\n```\n\n**How to use:**\n1. Identify the GitHub repository the user is asking about (owner and repo name from the URL).\n2. Construct the description URL: replace `{owner}` with the GitHub username\u002Forg and `{repo}` with the repository name.\n3. Fetch the description file — it contains a short, human-readable summary of the repository's purpose and contents.\n4. If the fetch returns a 404, the description has not been generated yet; fall back to the README entry or the archive.\n\n**Priority order when answering questions about a specific repository:**\n1. Description (quick summary) — fetch first for concise context\n2. Archive (full code snapshot) — fetch when deeper implementation details are needed\n3. README entry — fallback when neither description nor archive is available\n","## Overview\n\nThis skill covers reverse engineering workflows for game security research, including protected game clients, anti-cheat user-mode modules, kernel drivers, memory artifacts, and debugging environments that must survive anti-analysis checks.\n\n## README Coverage\n\n- `Cheat > Debugging`\n- `Cheat > RE Tools`\n- `Cheat > Mixed boolean-arithmetic`\n- `Cheat > Dynamic Binary Instrumentation`\n- `Cheat > Fix VMP`\n- `Cheat > Fix Themida`\n- `Cheat > Fix OLLVM`\n- `Cheat > Virtual Environments`\n- `Cheat > Decompiler`\n- `Cheat > IDA themes`\n- `Cheat > IDA Plugins`\n- `Cheat > IDA Signature Database`\n- `Cheat > Binary Ninja Plugins`\n- `Cheat > Ghidra Plugins`\n- `Cheat > Radare Plugins`\n- `Cheat > Windbg Plugins`\n- `Cheat > X64DBG Plugins`\n- `Cheat > Cheat Engine Plugins`\n- `Cheat > ROP Finder`\n- `Cheat > ROP Generation`\n- `Anti Cheat > Anti Debugging`\n- `Anti Cheat > Anti Disassembly`\n- `Anti Cheat > Dump Fix`\n- `Anti Cheat > Sample Unpacker`\n- `Anti Cheat > Obfuscation Engine`\n- `Anti Cheat > Winows User Dump Analysis`\n- `Anti Cheat > Winows Kernel Dump Analysis`\n\n## Debugging Tools\n\n### Windows Debuggers\n- **Cheat Engine**: Memory scanner and debugger for games\n- **x64dbg**: Open-source x86\u002Fx64 debugger\n- **WinDbg**: Microsoft's kernel\u002Fuser-mode debugger\n- **ReClass.NET**: Memory structure reconstruction\n- **HyperDbg**: Hypervisor-based debugger\n\n### Specialized Debuggers\n- **CE Mono Helper**: Unity\u002FMono game debugging\n- **dnSpy**: .NET assembly debugger\u002Fdecompiler\n- **ILSpy**: .NET decompiler\n- **frida**: Dynamic instrumentation toolkit\n\n### Platform-Specific\n- **edb-debugger**: Linux debugger\n- **PINCE**: Linux game hacking tool\n- **H5GG**: iOS cheat engine\n- **Hardware Breakpoint Tools**: HWBP implementations\n\n## Disassembly & Decompilation\n\n### Multi-Platform\n- **IDA Pro**: Industry standard disassembler\n- **Ghidra**: NSA's reverse engineering framework\n- **Binary Ninja**: Modern RE platform\n- **Cutter**: Radare2 GUI\n\n### Specialized Tools\n- **IL2CPP Dumper**: Unity IL2CPP analysis\n- **dnSpy**: .NET\u002FUnity decompilation\n- **jadx**: Android DEX decompiler\n- **Recaf**: Java bytecode editor\n\n## Memory Analysis\n\n### Memory Scanners\n```\n- Cheat Engine: Pattern scanning, value searching\n- ReClass.NET: Structure reconstruction\n- Process Hacker: System analysis\n```\n\n### Dump Tools\n```\n- KsDumper: Kernel-space process dumping\n- PE-bear: PE file analysis\n- ImHex: Hex editor for RE\n```\n\n## Dynamic Binary Instrumentation (DBI)\n\n### Frameworks\n- **Frida**: Cross-platform DBI\n- **DynamoRIO**: Runtime code manipulation\n- **Pin**: Intel's DBI framework\n- **TinyInst**: Lightweight instrumentation\n- **QBDI**: QuarkslaB DBI\n\n### Use Cases\n1. API hooking and tracing\n2. Code coverage analysis\n3. Fuzzing harness creation\n4. Behavioral analysis\n5. Driver IOCTL and callback tracing\n\n### Exception-Driven Lightweight DBI (Trap-and-Emulate)\n```\nConcept:\n- Replace branch instructions with fault-generating sentinel opcodes\n- Catch the resulting exception → emulate the original branch → log → resume\n- Full cycle: patch → fault → capture → emulate → record → restore → continue\n\nSentinel Selection:\n- HLT (0xF4) for ret → triggers STATUS_PRIVILEGED_INSTRUCTION\n- SALC (0xD6) for jmp\u002Fjcc\u002Fcall → triggers STATUS_ILLEGAL_INSTRUCTION\n- Avoids INT3 (0xCC) which anti-debug\u002Fintegrity checks commonly scan for\n- Different sentinels can multiplex branch types\n\nException Capture:\n- Hook KiUserExceptionDispatcher (not VEH\u002FSEH) for lowest-latency interception\n- Assembly stub tail-calls into RtlDispatchException\n- Handler dispatches by exception code to custom emulation logic\n\nBranch Emulation Engine:\n- Disassemble original (pre-patch) instruction at fault RIP\n- jcc: 16-condition lookup table (ZF, SF, CF, OF, PF combinations)\n- Direct call: push return address, update RIP\n- Indirect branch: resolve effective address (register, memory, SIB, RIP-relative)\n- ret: pop return address from stack, handle ret imm16 (extra pop)\n- loop\u002Fjrcxz: decrement RCX, conditional branch\n\nInstrumentation Strategies:\n- Bounded Bulk Patching: scan a window from seed address, patch all branches\n  → Simple but detectable by integrity checks\n- Branch Chasing: patch only current branch, re-instrument at target on fault\n  → Minimal memory footprint, highest stealth, best for unknown binaries\n- CFG-Guided Patching: recursive-descent static CFG + chasing for unreached edges\n  → Best coverage\u002Fsafety balance\n\nIntegrity Check Evasion:\n- PAGE_GUARD + Trap Flag (single-step) instead of direct code patching\n- Trigger guard page exception → set TF → single-step through original instruction\n- Avoids modifying .text section (defeats hash-based integrity checks)\n```\n\n### Control Flow Tracing (CFT) Applications\n```\n- Runtime call graph generation with register context at each edge\n- Divergence testing: compare traces across different inputs\u002Fenvironments\n  → Quickly locates input validation, anti-debug, anti-tamper trigger points\n- Deobfuscation: resolve all indirect branches in virtualized code\n- Hot path analysis, branch coverage measurement\n- Performance: ~600x slowdown (exception per branch), not suitable for\n  timing-sensitive targets (rdtsc checks, session timeouts)\n- Portable to other architectures: ARM (UDF), RISC-V (illegal instruction)\n```\n\n### User-Mode Hypervisor-Assisted Tracing\n```\nConcept:\n- Use Windows Hypervisor Platform (WHP) API to run guest code in user mode\n- No kernel driver required — standard user-mode process hosts the hypervisor\n- Map host memory pages into guest address space\n- Configure page-level traps (read\u002Fwrite\u002Fexecute permissions per page)\n- Guest execution triggers VM exits on configured events\n\nTrap-Driven Execution:\n- Page fault traps: set per-page R\u002FW\u002FX permissions via EPT-equivalent API\n  → Execute fault = code coverage, Write fault = memory write monitoring\n  → Read fault = data access tracking\n- CPUID interception: guest executes CPUID → VM exit → host decides response\n  → Useful for fingerprinting guest environment queries\n- Syscall interception: guest executes syscall → VM exit → host emulates\n  → Controlled experiments without real kernel interaction\n\nWorkflow:\n1. Prepare initial CPU state (registers, segments, control registers)\n2. Map target code + data pages with desired permissions\n3. Enter guest execution loop\n4. On VM exit: inspect reason, handle trap, optionally modify state\n5. Resume or terminate guest\n\nAdvantages:\n- Pure user-mode: no driver signing, no PatchGuard concerns\n- Deterministic: full control over guest memory and execution\n- Composable: combine with disassemblers\u002Femulators for hybrid analysis\n- Debuggable: host process can be debugged normally\n\nLimitations:\n- Requires hardware virtualization support (VT-x\u002FAMD-V)\n- Windows-specific (WHP API is Windows 10+)\n- Cannot run full OS — suited for code snippets and function-level analysis\n- Nested virtualization considerations when host is already a VM\n```\n\n## Anti-Analysis Bypass\n\n### Techniques\n- Anti-debug detection bypass\n- VM\u002FSandbox evasion\n- Timing attack mitigation\n- PatchGuard circumvention\n\n### Tools\n- **TitanHide**: Anti-debug hiding\n- **HyperHide**: Hypervisor-based hiding\n- **ScyllaHide**: Anti-anti-debug plugin\n\n## Game-Specific Analysis\n\n### Unity Games\n1. Locate `GameAssembly.dll` (IL2CPP) or managed DLLs\n2. Use IL2CPP Dumper for structure recovery\n3. Apply dnSpy for Mono games\n4. Hook via Unity-specific frameworks\n\n### Unreal Engine Games\n1. Identify UE version from signatures\n2. Use SDK generators (Dumper-7)\n3. Analyze Blueprint bytecode\n4. Hook UObject\u002FUFunction systems\n\n### Native Games\n1. Standard PE analysis\n2. Import\u002Fexport reconstruction\n3. Pattern scanning for signatures\n4. Runtime memory analysis\n\n## Workflow Best Practices\n\n### Initial Analysis\n```\n1. Identify protections (packer, obfuscator, anti-cheat)\n2. Determine game engine and version\n3. Collect symbol information if available\n4. Map out key modules, callbacks, and trust boundaries\n```\n\n### Deep Analysis\n```\n1. Locate target functionality\n2. Trace execution flow\n3. Document structures, memory artifacts, and relationships\n4. Correlate IOCTLs, callbacks, and runtime checks\n```\n\n## Obfuscation Taxonomy\n\n### Mixed Boolean-Arithmetic (MBA)\n```\n- Linear MBA: e.g., x + y = (x ^ y) + 2*(x & y)\n- Polynomial MBA: higher-degree expressions over boolean\u002Farithmetic mix\n- Tools: SSPAM, MBA-Blast, SiMBA for simplification\n- Common in: VMProtect, Themida, custom LLVM passes\n```\n\n### Control Flow Flattening (CFF)\n```\n- OLLVM-style: all basic blocks behind a dispatcher switch\n- Recovery: symbolic execution, pattern matching, deobfuscation passes\n- Tools: D-810 (IDA), de-ollvm scripts, SATURN\n- Variants: nested dispatchers, encrypted state variables\n```\n\n### Opaque Predicates\n```\n- Invariant conditions injected to confuse static analysis\n- Number-theoretic (x² mod 4 ∈ {0,1}), pointer-aliasing based\n- Detection: abstract interpretation, SMT solvers (Z3)\n```\n\n### Virtualization-Based Obfuscation\n```\nVMProtect \u002F Themida \u002F Code Virtualizer:\n- Custom bytecode VM with randomized opcode set per build\n- Handler table dispatch loop: fetch → decode → execute\n- Devirtualization approaches:\n  - Trace-based: record handler execution, lift to IR\n  - Pattern-based: identify handler semantics by structure\n  - Symbolic: concolic execution through VM dispatch\n- Tools: VMPAttack, NoVmp, Oreans UnVirtualizer, vtil\n```\n\n### Binary Lifting\n```\n- Lift machine code to compiler IR (LLVM IR, VEX, ESIL)\n- Enables compiler-level optimization passes for deobfuscation\n- Tools: McSema, remill, RetDec, Binary Ninja MLIL\u002FHLIL\n```\n\n## Disassembler Plugin Ecosystem\n\n### IDA Pro Plugins\n```\nCategories found in README (> IDA Plugins, 150+ entries):\n- Decompiler enhancers: HexRaysPyTools, HRDevHelper\n- Type recovery: ClassInformer, auto_struct\n- Signature: FLIRT, Lumina, IDA Signature Database\n- Scripting: IDAPython, IDC, LazyIDA\n- Visualization: IDAGraph, Lighthouse (coverage)\n- Anti-obfuscation: D-810 (MBA), de-ollvm, Patfinder\n- Game-specific: SDK loaders, structure importers\n```\n\n### Binary Ninja Plugins\n```\n- Sidekick, snippets, type libraries\n- HLIL-based analysis scripts\n- Custom architectures and loaders\n- Headless analysis for batch processing\n```\n\n### Ghidra Plugins\n```\n- GhidraScript (Java\u002FPython), Ghidra extensions\n- Ghidraaas (Ghidra-as-a-Service)\n- Type importers, signature matchers\n- Firmware analysis (SVD loader, embedded)\n```\n\n### Radare2 \u002F iaito Plugins\n```\n- r2pipe scripting (Python, JS, Rust)\n- iaito: official radare2 Qt GUI\n- r2ghidra: Ghidra decompiler integration\n- r2dec: lightweight decompiler\n```\n\n### WinDbg Plugins\n```\n- SwishDbgExt, WinDbgX\n- Time Travel Debugging (TTD) extensions\n- !analyze extensions, custom formatters\n- Kernel debugging helpers\n```\n\n### x64dbg Plugins\n```\n- ScyllaHide (anti-anti-debug)\n- TitanEngine, x64dbgpy\n- Trace plugins, pattern scanners\n- Conditional breakpoint scripts\n```\n\n### Cheat Engine Plugins\n```\n- Mono\u002FIL2CPP helpers\n- Auto-assembler templates\n- Structure dissectors\n- Pointer scanner extensions\n```\n\n## MCP-Based RE Tools\n\n```\nThe README's MCP server section and RE tool ecosystem now include\nAI-assisted reverse engineering through Model Context Protocol:\n\n- IDA MCP: AI agent controls IDA Pro (rename, annotate, navigate)\n- Ghidra MCP: AI agent queries Ghidra decompilation and PCODE\n- Binary Ninja MCP: AI agent interacts with Binary Ninja API\n- radare2 MCP: AI agent drives r2 sessions via r2pipe\n- x64dbg MCP: AI agent controls live debugging sessions\n\nWorkflow: LLM ↔ MCP server ↔ RE tool, enabling natural-language\nqueries like \"find all functions calling CreateRemoteThread\" or\n\"rename this function based on its decompiled logic\"\n```\n\n## Binary Diffing\n\n```\nTools for comparing binary versions (patch analysis, vulnerability research):\n- BinDiff (Google): graph-based structural comparison\n- Diaphora: IDA plugin, best open-source binary diff\n- ghidriff: Ghidra-based diffing, command-line and scriptable\n- DarunGrim: patch analysis focused differ\n- turbodiff: lightweight IDA diffing plugin\n\nUse cases in game security:\n- Tracking anti-cheat driver updates between versions\n- Identifying patched vulnerabilities in game clients\n- Comparing obfuscated builds to isolate logic changes\n```\n\n## Anti-Debug Techniques Catalog\n\n### User-Mode Anti-Debug\n```\n- IsDebuggerPresent \u002F CheckRemoteDebuggerPresent\n- NtQueryInformationProcess (ProcessDebugPort, ProcessDebugFlags, ProcessDebugObjectHandle)\n- NtSetInformationThread (ThreadHideFromDebugger)\n- PEB.BeingDebugged, PEB.NtGlobalFlag, heap flags\n- INT 2D, INT 3 scanning, OutputDebugString tricks\n- Timing checks: rdtsc, QueryPerformanceCounter, GetTickCount64\n- TLS callbacks for early detection\n- Exception-based: unhandled exception filter, VEH chain inspection\n- Parent process checks (csrss.exe verification)\n- Self-debugging: NtCreateDebugObject\n```\n\n### Kernel-Mode Anti-Debug\n```\n- KdDebuggerEnabled \u002F KdDebuggerNotPresent\n- Debug register (DR0-DR7) monitoring and clearing\n- KPROCESS.DebugPort zeroing\n- NMI callbacks for debugger detection\n- Hardware breakpoint detection via context inspection\n```\n\n### Anti-Debug Bypass Tools\n```\n- ScyllaHide: comprehensive anti-anti-debug (x64dbg\u002FIDA\u002Fstandalone)\n- TitanHide: kernel-mode debugger hiding\n- HyperHide: hypervisor-based anti-debug bypass\n- SharpOD: OllyDbg anti-anti-debug plugin\n```\n\n## VMProtect\u002FThemida Analysis\n\n### Resources\n- Devirtualization tools\n- Control flow recovery\n- Handler analysis techniques\n- Unpacking methodologies\n\n## ROP\u002FExploit Development\n\n### Tools\n- **ROPgadget**: Gadget finder\n- **rp++**: Fast ROP gadget finder\n- **angrop**: Automated ROP chain generation\n\n---\n\n## Data Source\n\n**Important**: This skill provides conceptual guidance and overview information. For detailed information use the following sources:\n\n### 1. Project Overview & Resource Index\n\nFetch the main README for the full curated list of repositories, tools, and descriptions:\n\n```\nhttps:\u002F\u002Fraw.githubusercontent.com\u002Fgmh5225\u002Fawesome-game-security\u002Frefs\u002Fheads\u002Fmain\u002FREADME.md\n```\n\nThe main README contains thousands of curated links organized by category. When users ask for specific tools, projects, or implementations, retrieve and reference the appropriate sections from this source.\n\n### 2. Repository Code Details (Archive)\n\nFor detailed repository information (file structure, source code, implementation details), the project maintains a local archive. If a repository has been archived, **always prefer fetching from the archive** over cloning or browsing GitHub directly.\n\n**Archive URL format:**\n```\nhttps:\u002F\u002Fraw.githubusercontent.com\u002Fgmh5225\u002Fawesome-game-security\u002Frefs\u002Fheads\u002Fmain\u002Farchive\u002F{owner}\u002F{repo}.txt\n```\n\n**Examples:**\n```\nhttps:\u002F\u002Fraw.githubusercontent.com\u002Fgmh5225\u002Fawesome-game-security\u002Frefs\u002Fheads\u002Fmain\u002Farchive\u002Fufrisk\u002Fpcileech.txt\nhttps:\u002F\u002Fraw.githubusercontent.com\u002Fgmh5225\u002Fawesome-game-security\u002Frefs\u002Fheads\u002Fmain\u002Farchive\u002F000-aki-000\u002FGameDebugMenu.txt\n```\n\n**How to use:**\n1. Identify the GitHub repository the user is asking about (owner and repo name from the URL).\n2. Construct the archive URL: replace `{owner}` with the GitHub username\u002Forg and `{repo}` with the repository name (no `.git` suffix).\n3. Fetch the archive file — it contains a full code snapshot with file trees and source code generated by `code2prompt`.\n4. If the fetch returns a 404, the repository has not been archived yet; fall back to the README or direct GitHub browsing.\n\n### 3. Repository Descriptions\n\nFor a concise English summary of what a repository does, the project maintains auto-generated description files.\n\n**Description URL format:**\n```\nhttps:\u002F\u002Fraw.githubusercontent.com\u002Fgmh5225\u002Fawesome-game-security\u002Frefs\u002Fheads\u002Fmain\u002Fdescription\u002F{owner}\u002F{repo}\u002Fdescription_en.txt\n```\n\n**Examples:**\n```\nhttps:\u002F\u002Fraw.githubusercontent.com\u002Fgmh5225\u002Fawesome-game-security\u002Frefs\u002Fheads\u002Fmain\u002Fdescription\u002F00christian00\u002FUnityDecompiled\u002Fdescription_en.txt\nhttps:\u002F\u002Fraw.githubusercontent.com\u002Fgmh5225\u002Fawesome-game-security\u002Frefs\u002Fheads\u002Fmain\u002Fdescription\u002Fufrisk\u002Fpcileech\u002Fdescription_en.txt\n```\n\n**How to use:**\n1. Identify the GitHub repository the user is asking about (owner and repo name from the URL).\n2. Construct the description URL: replace `{owner}` with the GitHub username\u002Forg and `{repo}` with the repository name.\n3. Fetch the description file — it contains a short, human-readable summary of the repository's purpose and contents.\n4. If the fetch returns a 404, the description has not been generated yet; fall back to the README entry or the archive.\n\n**Priority order when answering questions about a specific repository:**\n1. Description (quick summary) — fetch first for concise context\n2. Archive (full code snapshot) — fetch when deeper implementation details are needed\n3. README entry — fallback when neither description nor archive is available\n",{},"main","19a54ac988e9929160334271f5c1924ddd9b227e","_modules\u002Freverse-engineering-tools",19,"https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill","https:\u002F\u002Fgithub.com\u002Falicewe1","写一些自己用得上的工具，能自动化就绝不手动 · 自动化 \u002F 工程效率 \u002F Agent 技能生态 · 保持好奇，持续构建","2026-09-30 00:41:20",{"source":7,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add alicewe1\u002Falice_skill --skill reverse-engineering-tools",{"tool":37,"command":38},"bunx","bunx skills add alicewe1\u002Falice_skill --skill reverse-engineering-tools",{"tool":40,"command":41},"pnpm","pnpm dlx skills add alicewe1\u002Falice_skill --skill reverse-engineering-tools","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002F_modules\u002Freverse-engineering-tools\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":18},"01M7DBMD9P6R27SWQCW5HYVWG0","alice","Alice 六类技能总路由。用户输入 Alice 或要求查看 Alice 技能菜单时，严格输出固定菜单；输入攻\u002F防模式、六类入口或直接描述任务时，按类别→领域→模块渐进路由。","https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002Faliceskill\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":18},"01M7DBM8X5M7YXPYBVFMWF8HRC","alice-reverse","逆向分析渐进路由（二进制 \u002F 移动端 \u002F 协议 \u002F 取证 \u002F 保护机制 \u002F 运行时观测）。触发词：二进制\u002F移动端\u002F反编译\u002FFrida\u002FIDA\u002FGhidra\u002FPE\u002FELF\u002FAPK\u002F协议\u002F取证；先选领域索引，再按任务匹配度与评分选模块，禁止一次读取全部领域。","https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002Falice-reverse\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M7DBM630E2YKQP29194TT7HC","alice-pentest","web安全渐进路由（Web \u002F API \u002F 资产发现 \u002F 漏洞验证 \u002F 云与网络安全）。触发词：Web\u002FAPI\u002F资产发现\u002F端口\u002F漏洞验证\u002F云与网络安全；先选领域索引，再按任务匹配度与评分选模块，禁止一次读取全部领域。","https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002Falice-pentest\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":18},"01M7DBM20M2VDYV5D3MYDGBTQX","alice-game","游戏攻防渐进路由（游戏客户端 \u002F 内存 \u002F 图形 \u002F 反作弊 \u002F 安全研究）。触发词：游戏客户端\u002F内存\u002F图形\u002F偏移\u002F反作弊\u002F模拟器\u002F覆盖层；先选领域索引，再按任务匹配度与评分选模块，禁止一次读取全部领域。","https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002Falice-game\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"01M7DBKXVEKB8931MZG23VACFN","alice-crack","卡密授权渐进路由（卡密 \u002F 激活 \u002F 授权验证 \u002F 许可证管理 \u002F 本地授权分析）。触发词：卡密\u002F激活\u002F授权验证\u002Flicense\u002F机器码\u002F试用状态；先选领域索引，再按任务匹配度与评分选模块，禁止一次读取全部领域。","https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002Falice-crack\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"01M7DBKTMT90MGV2WP8K73TMQD","alice-assist","技能指令渐进路由（技能路由 \u002F 评分 \u002F 吸收 \u002F 迁移 \u002F 自动化 \u002F 文档与平台集成）。触发词：技能创建\u002F吸收\u002F评分\u002F迁移\u002F自动化\u002F文档\u002F平台指令；先选领域索引，再按任务匹配度与评分选模块，禁止一次读取全部领域。","https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002Falice-assist\u002FSKILL.md",[],[]]