AD SPACE AVAILABLE · BRAND PARTNERS WELCOME

Fake Anti-Cheat Drivers and Kernel Rootkits: BYOVD Exploits and Driver Verifier Isolation

365Finds Editorial
Indexed 11,430 Wiki articles

Put 365 Wiki to work with your AI

Copy the prompt below, paste it into the AI you already use, then ask your question.

Download full Skill

Try it with the prompt first. If you use 365 Wiki often, install the full 365Wiki Skill so you do not have to paste it again. No regular AI? Gemini or Microsoft Copilot on the web will work.

365Wiki Skill

Threat Vector Matrix: Legitimate Kernel Anti-Cheat vs Counterfeit Rootkits

Modern PC competitive titles require Ring 0 kernel-level anti-cheat drivers (e.g. vgk.sys, EasyAntiCheat.sys, bedaisy.sys). Cybercriminals exploit this paradigm by distributing pirated game installers, private cheat loaders, or community tournament clients bundling "Bring Your Own Vulnerable Driver" (BYOVD) payloads and persistent kernel rootkits.

Driver Artifact ProfileCryptographic Signature StatusExecution PrivilegeThreat Behavior / Persistence
Legitimate Commercial Anti-CheatValid EV Code Signing Certificate from Microsoft WHQLRing 0 Kernel ModeInitializes at boot; monitors process memory and hypervisor states
BYOVD (Vulnerable Signed Driver)Legitimate but ancient/revoked certificate (e.g. gdrv.sys)Ring 0 Kernel ModeAbuses known CVE read/write primitives to disable EDR/AV software
Counterfeit Community Anti-CheatSelf-signed or test-mode certificateRing 0 Kernel ModeInjects persistent backdoor; intercepts Discord tokens and Steam sessions
Cracked Game Bypass DriverStripped signature loaded via DSE bypassRing 0 Kernel ModeEnforces permanent rootkit hooks; installs hidden mining worker threads
Driver Verifier Flagged ModuleFails pool allocation or I/O request packet checksRing 0 Kernel ModeCauses instant bugcheck (PAGE_FAULT_IN_NONPAGED_AREA) on load

Identifying Rogue Kernel Drivers in Windows System32

Attackers deploy rootkits directly into the Windows driver directory or register them as background system services:

  1. Audit Driver Store via Command Line: Execute PowerShell to inspect all installed third-party drivers and their digital signers:
    // Inspect third-party kernel drivers and filter out non-Microsoft signers
    Get-WmiObject Win32_SystemDriver | Where-Object { $_.State -eq "Running" -and $_.PathName -notmatch "Windows\System32\drivers" } | Select-Object Name, DisplayName, PathName
    
  2. Inspect Driver Digital Signatures via Sigcheck: Scan target drivers using Microsoft Sysinternals Sigcheck:
    sigcheck64.exe -v -a C:\Windows\System32\drivers\suspicious_ac.sys
    
    Look for:
    • "Signing date": Outdated timestamps (e.g. 2015-2018 drivers in a 2026 title).
    • "Revocation status": Revoked by Microsoft Root Authority.

Activating Windows Memory Integrity (HVCI) and Driver Blocklists

Hypervisor-Protected Code Integrity (HVCI) neutralizes unsigned or vulnerable drivers by enforcing hardware-enforced virtualization security:

  1. Open Windows Security -> Device security -> Core isolation details.
  2. Toggle Memory integrity to On.
  3. Toggle Microsoft Vulnerable Driver Blocklist to On.
    • If Windows refuses to enable Memory Integrity due to an incompatible driver, note the published filename (e.g. oem_anticheat.sys).
  4. Forcefully purge the incompatible driver using pnputil:
    // Enumerate and delete the offending third-party driver package
    pnputil /enum-drivers
    pnputil /delete-driver oemXX.inf /uninstall /force
    

Using Driver Verifier to Isolate Rogue Kernel Hooks

// PowerShell helper to inspect active kernel service registrations
Get-Service | Where-Object { $_.ServiceType -eq "KernelDriver" -and $_.Status -eq "Running" } | Select-Object Name, DisplayName, Status
  1. Press Win + R, type verifier.exe, and hit Enter.
  2. Select Create standard settings -> click Next.
  3. Select Select driver names from a list -> click Next.
  4. Sort by Provider and select all non-Microsoft and unverified driver files.
  5. Reboot Windows. If a driver executes an illegal kernel memory read, Driver Verifier crashes the system cleanly with an explicit bugcheck pointing directly to the offending .sys binary, allowing safe removal in Safe Mode.