Skip to content

!!IMPORTANT!! Discord server termed, join the new one! discord.gg/QNkCQDWtGD

Sense

Vanguard Anti-Cheat Explained: How Riot's Kernel Driver Works

A technical deep dive into how Riot Vanguard works at the kernel level, what it monitors from boot, and why it is one of the most aggressive anti-cheat systems in gaming.

By SensePublished

Bu yazıyı Türkçe okuyun

What Is Riot Vanguard?

Riot Vanguard is Riot Games' proprietary anti-cheat system built specifically for Valorant and later extended to League of Legends. Unlike third-party solutions such as EasyAntiCheat or BattlEye that serve many games, Vanguard is developed in-house by Riot's anti-cheat team and tailored to protect their own titles.

What makes Vanguard unique among anti-cheat systems is its boot-time initialization. Vanguard loads a kernel-mode driver (vgk.sys) when Windows starts, not when you launch the game. This driver runs at Ring 0, the highest privilege level in the x86 architecture, giving it the same access as the Windows kernel itself.

Boot-Time Loading: Why It Matters

Most anti-cheat systems load their kernel driver when the game launches. Vanguard takes a different approach by loading at boot. The reason is straightforward: if a cheat loads a kernel driver before the anti-cheat driver loads, the cheat has first-mover advantage. It can hide itself, hook system functions, and establish persistence before the anti-cheat even starts looking.

By loading at boot, Vanguard ensures it is one of the first drivers in the system. It can monitor driver loading from the beginning and detect any attempt to load unsigned or suspicious drivers before the game even starts.

If Vanguard's driver is not running when you try to launch Valorant, the game will refuse to start and display a VAN error code. You need to restart your computer to initialize the driver.

How Vanguard Monitors the System

Kernel Driver Monitoring

Vanguard watches for kernel drivers being loaded into the system. Every driver that loads after Vanguard is checked against several criteria:

  • Signature verification: Vanguard checks whether loaded drivers are properly signed with valid certificates. Unsigned drivers or drivers signed with revoked certificates are flagged.
  • Known vulnerable drivers: Some legitimate signed drivers have known vulnerabilities that cheats exploit to gain kernel access. Vanguard maintains a blocklist of these vulnerable drivers and prevents them from loading.
  • Behavioral monitoring: Even properly signed drivers are monitored for suspicious behavior like accessing Valorant's process memory or hooking system functions that the game relies on.

Memory Integrity

Vanguard continuously verifies the integrity of Valorant's process memory. The game's executable code is checksummed at load time, and Vanguard periodically rechecks these regions during gameplay. Any modification to the game's code, whether from DLL injection, function hooking, or inline patching, triggers a detection.

This extends beyond just the game process. Vanguard monitors critical Windows structures like the System Service Descriptor Table (SSDT) and Interrupt Descriptor Table (IDT) for hooks that could indicate rootkit-level cheats.

Process and Thread Monitoring

Vanguard tracks processes that interact with Valorant's memory space. Any process that opens a handle to the game with memory read or write permissions is logged and analyzed. This catches external cheats that use ReadProcessMemory or WriteProcessMemory to interact with the game.

Thread injection into the Valorant process is also monitored. Techniques like CreateRemoteThread, APC injection, and thread hijacking are detected and blocked.

Hardware Fingerprinting

Vanguard collects detailed hardware identifiers from the system. These include disk serial numbers, MAC addresses, motherboard serial numbers, BIOS UUIDs, TPM identifiers, and more. This fingerprint serves two purposes: identifying hardware-banned players and tracking accounts across hardware changes.

Hypervisor Detection

Vanguard checks for the presence of virtual machine hypervisors. Some advanced cheats use custom hypervisors to intercept memory reads below the operating system level, making them invisible to traditional kernel-mode detection. Vanguard detects common hypervisor signatures and can block the game from running in virtualized environments.

Vanguard vs. Other Anti-Cheat Systems

vs. EasyAntiCheat

EAC loads its driver when the game launches, not at boot. This gives cheats a window to establish themselves before EAC starts. However, EAC benefits from deployment across hundreds of games, giving it a massive cheat signature database. Vanguard's narrower focus means it can be more aggressive with Valorant-specific detections.

vs. BattlEye

BattlEye also loads at game launch and operates at the kernel level. It is known for frequent ban waves and aggressive detection. Vanguard and BattlEye are roughly comparable in detection capability, but Vanguard's boot-time loading gives it an edge against cheats that try to load before the anti-cheat.

vs. Ricochet (Call of Duty)

Ricochet is Activision's kernel-level anti-cheat for Call of Duty. Like Vanguard, it uses a kernel driver, but it loads at game launch rather than boot. Ricochet is notable for its "damage shield" feature that reduces cheaters' ability to harm legitimate players in real-time, which Vanguard does not have.

The Privacy Debate

Vanguard's always-on kernel driver has been controversial since launch. Critics argue that a kernel-level driver running from boot has unprecedented access to the system, even when you are not playing Valorant. Riot has responded that the driver is dormant when the game is not running and only actively monitors when Valorant is launched.

The Vanguard tray icon in the system tray allows you to disable the driver, but doing so requires a restart before you can play Valorant again. This gives players control over when the driver is active, though many leave it running permanently for convenience.

What Vanguard Bans Look Like

When Vanguard detects a cheat, the ban process involves multiple steps:

  1. Detection event: Vanguard flags suspicious activity and reports it to Riot's servers.
  2. Verification: Riot's backend systems verify the detection to minimize false positives.
  3. Account ban: The player's Riot account receives a permanent ban from Valorant.
  4. Hardware ban: The hardware identifiers collected by Vanguard are added to a blocklist, preventing new accounts on the same hardware.

Bans can be immediate for known cheat signatures or delayed as part of ban waves for newer detections. The delay makes it harder for cheat developers to identify which update triggered the detection.

Getting Past Vanguard's Hardware Ban

After a Vanguard hardware ban, your PC is blocked regardless of which Riot account you use. Creating a new account, reinstalling Windows, or reformatting drives does not remove the ban because Vanguard reads hardware identifiers from the physical components themselves.

The identifiers that Vanguard tracks are extensive, covering multiple hardware components simultaneously. Changing a single component is not enough because Vanguard uses a composite fingerprint that tolerates minor changes.

Sense AC's HWID spoofer is designed to work against Vanguard's fingerprinting system. It modifies the hardware identifiers at the kernel level before Vanguard's driver can read them, presenting a completely new hardware profile. This allows you to create a fresh Riot account and play Valorant on previously banned hardware.

Key Takeaways

Vanguard is one of the most technically sophisticated anti-cheat systems in gaming. Its boot-time kernel driver, comprehensive memory monitoring, and aggressive hardware fingerprinting make it a formidable barrier for cheat developers. Understanding how it works is essential for anyone interested in the technical side of game security.