Skip to content
OpenAgentSkill
Browsing is open · Catalog captured 2026-11-21 · Automatic updates and account services are paused.
Security

anti-cheat-systems

Guide for modern game anti-cheat architecture, Windows kernel monitoring, and detection tradeoffs. Use this skill when analyzing EAC, BattlEye, Vanguard, FACEIT AC, kernel callbacks, handle protection, manual-map detection, boot-start drivers, BYOVD, DMA threats, or behavioral telemetry in game security research.

alicewe1 · Static checks on file

Installation

Read the source and dependencies before running a command. Copying does not install or execute anything.

npx skills add alicewe1/alice_skill --skill anti-cheat-systems

About this skill


name: anti-cheat-systems description: Guide for modern game anti-cheat architecture, Windows kernel monitoring, and detection tradeoffs. Use this skill when analyzing EAC, BattlEye, Vanguard, FACEIT AC, kernel callbacks, handle protection, manual-map detection, boot-start drivers, BYOVD, DMA threats, or behavioral telemetry in game security research. x-alice-class: game

Anti-Cheat Systems & Analysis

Overview

This skill covers layered anti-cheat design across kernel drivers, privileged services, in-game components, and backend telemetry. It is most useful for mapping how modern anti-cheats monitor process handles, image loads, memory integrity, driver trust, virtualization abuse, DMA threats, and suspicious input behavior on Windows.

README Coverage

  • Anti Cheat > Guide
  • Anti Cheat > Stress Testing
  • Anti Cheat > Driver Unit Test Framework
  • Anti Cheat > Anti Debugging
  • Anti Cheat > Page Protection
  • Anti Cheat > Binary Packer
  • Anti Cheat > CLR Protection
  • Anti Cheat > Anti Disassembly
  • Anti Cheat > Sample Unpacker
  • Anti Cheat > Dump Fix
  • Anti Cheat > Encrypt Variable
  • Anti Cheat > Lazy Importer
  • Anti Cheat > Anti-Cheat Programming
  • Anti Cheat > Compile Time
  • Anti Cheat > Shellcode Engine & Tricks
  • Anti Cheat > Obfuscation Engine
  • Anti Cheat > Screenshot
  • Anti Cheat > Game Engine Protection:*
  • Anti Cheat > Open Source Anti Cheat System
  • Anti Cheat > Analysis Framework
  • Anti Cheat > Detection:*
  • Anti Cheat > Signature Scanning
  • Anti Cheat > Information System & Forensics
  • Anti Cheat > Dynamic Script
  • Anti Cheat > Kernel Mode Winsock
  • Anti Cheat > Fuzzer
  • Anti Cheat > Windows Ring3 Callback
  • Anti Cheat > Windows Ring0 Callback
  • Anti Cheat > Winows User Dump Analysis
  • Anti Cheat > Winows Kernel Dump Analysis
  • Anti Cheat > Sign Tools
  • Anti Cheat > Backup File / Backup Drivers
  • Anti Cheat > Black Signature
  • Windows Security Features

Major Anti-Cheat Systems

Easy Anti-Cheat (EAC)

  • Multi-component architecture with service, driver, and game-facing protections
  • Process integrity verification and memory inspection
  • Runtime driver loading with strong client-side enforcement
  • Used by: Fortnite, Apex Legends, Rust

BattlEye

  • Kernel driver plus service and game module coordination
  • Handle protection, process monitoring, and memory scanning
  • Strong focus on injected code and runtime tampering visibility
  • Used by: PUBG, Rainbow Six Siege, DayZ

Vanguard (Riot Games)

  • Boot-start kernel driver with early visibility into later-loaded drivers
  • Boot-time initialization
  • Driver allowlisting and aggressive system trust checks
  • Used by: Valorant, League of Legends

FACEIT AC

  • Kernel-level competitive anti-cheat with strong process and driver monitoring
  • Emphasis on platform integrity and low tolerance for hostile drivers
  • Often discussed alongside Vanguard in kernel anti-cheat research

Valve Anti-Cheat (VAC)

  • User-mode detection
  • Signature-based scanning
  • Delayed ban waves
  • Used by: CS2, Dota 2, TF2

Other Systems

  • PunkBuster: Legacy FPS anti-cheat
  • FairFight: Server-side statistical analysis
  • nProtect GameGuard: Korean anti-cheat solution
  • XIGNCODE3: Mobile game protection
  • ACE (Tencent): Chinese market protection

Detection Mechanisms

Detection Decision Methodology

Use research-rigor for source verification and empirical validation. Numeric values elsewhere in this skill are examples or research hypotheses unless they are tied to a representative, versioned calibration study for the target game.

  1. Define the decision unit: player, engagement, session, account, device, or build; state the game mode, patch, platform, input method, and timeframe.
  2. Establish telemetry trust: record whether each field is server-observed, server-derived, client-reported, or reconstructed. Client reports are adversarial inputs; server authority improves trust but does not eliminate clock, replication, schema, or game-logic errors.
  3. Keep layers separate: observation -> finding -> attribution -> action. A detector hit is not itself proof of cheating or actor intent.
  4. Calibrate locally: derive features, sample floors, and operating thresholds from representative data. Hold out players/sessions and time periods; segment results by relevant populations.
  5. Measure deployment risk: report prevalence, FPR, FNR, precision, recall, calibration, uncertainty, and the expected review volume. A score in [0, 1] is not a probability unless calibrated as one.
  6. Corroborate correctly: combine causally distinct signals and evaluate their joint errors. Correlated signals, maximum-score aggregation, or a fixed signal count do not guarantee a lower false-positive rate.
  7. Review high-impact actions: preserve counterevidence and an appeal path; use human review or independently trusted evidence before punitive action when false positives remain plausible.

For invariant findings, first verify that the invariant is guaranteed in the observed state and exclude rollback, retry, reconnect, replication delay, legitimate transitions, administrator/test paths, stale baselines, and game bugs. Describe the result as a state-integrity violation until exploitation and attribution are separately supported.

Every evidence package should retain the raw artifact or immutable reference, timestamps and ordering, schema/game/detector versions, feature transforms, threshold/model version, sample counts, provenance, contradictory evidence, limitations, and the exact rule that fired.

Memory Detection

- Code section hashing and integrity verification
- Executable private memory and manual-map detection
- Injected module and anomalous image mapping detection
- Memory modification and stack provenance monitoring

Process Detection

- Handle access str
Read the complete source ↗