Game Hacking Techniques

This is a threat modeling reference that maps the offensive side of game security, from user-mode memory reading and DLL injection all the way down to kernel drivers, hypervisors, and DMA hardware. It covers the full escalation ladder that cheaters climb when anti-cheat systems push them out of easier attack surfaces. The source material pulls from the awesome-game-security taxonomy, so you get concrete categories like overlay rendering, W2S transforms, vulnerable driver abuse, and even AI visual aimbots that use YOLO models with OBS capture to avoid touching game memory entirely. Use this when you need to understand what modern cheats actually look like under the hood, especially if you're building or auditing anti-cheat systems.

skills.sh installs: 325
GitHub stars: 3.7K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add gmh5225/awesome-game-security --skill game-hacking-techniques --agent claude-code

Installs into .claude/skills of the current project.

Files

Game-hacking techniques

Map what an attacker observes or controls, the required capability, the trust boundary crossed, and where defenders have evidence or authority.

Topic routing

Capabilities and core techniques for privilege levels, manipulation, injection, and cheat categories.
Rendering, memory, and input for overlays, access paths, driver communication, world-to-screen, and input.
Platform and evasion for EFI, device identity, stack behavior, and anti-detection concepts.
Engines and workflow for engine-specific surfaces and representative research workflows.
Attack-surface map, repository resources, and repository map for evidence and source selection.

Use the narrower engine, graphics, DMA, kernel, mobile, server, or supply-chain skill when one boundary dominates. Keep recommendations defensive and within the user's authorized scope.

SKILL.md on GitHub