awesome-game-security

Analyze layered anti-cheat architecture, detection evidence, telemetry, and enforcement tradeoffs. Use for system-level defense questions; use narrower skills for DMA, kernel, graphics, mobile, or server details.

Find, select, classify, or maintain resources in awesome-game-security. Use for repository navigation, category placement, duplicate review, generated descriptions, wiki coverage, or choosing a domain skill.

Analyze PCIe DMA threats, host-mediated memory acquisition, FPGA behavior, and IOMMU defenses. Use when the memory initiator or device boundary matters; use kernel security for host-only mechanisms.

Analyze game-engine internals and select version-matched resources for Unreal, Unity, Source, Godot, or custom engines. Use for engine structure, object models, assets, SDK extraction, or editor/runtime boundaries.

Classify game-cheat capabilities and their defensive implications across memory, injection, rendering, input, engines, kernels, DMA, and remote transports. Use for authorized threat modeling, not operational deployment.

Verify consequential or disputed game-security claims with primary sources, reproducible evidence, explicit trust boundaries, and calibrated uncertainty. Use alongside a domain skill when evidence quality affects the conclusion.

Review multiplayer authority, RPCs, sessions, authorization, replication, inventory, economy, purchases, retries, and replay. Use when server or backend state is the security boundary.

Assess game build, launcher, update, distribution, mod, plugin, dependency, signing, provenance, and recovery trust. Use when release or content ingestion is the security boundary.

Analyze Direct3D, DXGI, OpenGL, or Vulkan rendering, overlays, presentation, capture, and measurement evidence. Use when the graphics pipeline or frame-observation boundary is central.

Analyze Linux, SteamOS, Steam Deck, Wine, or Proton game-security boundaries. Use for ELF/process evidence, privileges, namespaces, seccomp, LSMs, compatibility, or Linux memory forensics.

Analyze Android or iOS game-security trust boundaries, packages, native code, platform integrity, instrumentation, attestation, and signing. Use when mobile OS or device behavior is central.

Analyze supplied game binaries, protection components, drivers, dumps, or traces through reproducible disassembly, decompilation, debugging, diffing, and interface reconstruction.

Analyze Windows driver trust, callbacks, IRQL, kernel memory, DSE, PatchGuard, VBS/HVCI, ETW, crash evidence, and build-specific internals for authorized game-security research.