Game Hacking

Game Hacking

Offensive technique taxonomy and threat model: how cheats escalate from user-mode memory/injection to kernel drivers, hypervisors, EFI, and DMA as defenders raise the bar.

Escalation model

1. User-mode — RPM/WPM, DLL/shellcode injection, graphics/input hooks
2. Kernel-mode — signed/vulnerable drivers (BYOVD), callback/page-table work
3. Below the OS — hypervisor, PCIe DMA, external devices / second machines

Key sub-areas

• Memory, injection, hooking (inline/IAT/VTable/HWBP)
• Visual ESP / aim / movement cheats; AI visual pipelines (OBS + YOLO + HID)
• Overlays via Present Hook and external/DWM windows
• HWID spoofing, stack spoofing, driver communication channels
• EFI boot-time mappers; engine-specific paths (Unreal/Unity/Source)
• AC-system exploration repos (e.g. vac3_inhibitor for VAC3) sit in the user-mode research lane

Related concepts

DMA · BYOVD · Present Hook · IL2CPP · Kernel Callbacks · vac3_inhibitor · Anti-Cheat

README map

Cheat is the largest category (~2500 links): debugging, injection, DMA, overlays, vulnerable drivers, EFI, HWID, game-specific trees, plus Some Tricks Ring0/Ring3.

→ README § Cheat