Arbitrary Process Termination in Tower of Fantasy GameDriverX64.sys
GameDriverX64.sys, the Tower of Fantasy anti-cheat kernel-mode driver, version 7.23.4.7 and earlier, contains an access control flaw in an IOCTL handler. A user-mode process can open a handle to the device object exposed by the driver and issue specially crafted IOCTL requests that are executed in kernel context without proper authentication or authorization checks. As described in the provided content, this allows an unprivileged local attacker to invoke driver functionality to terminate arbitrary processes, including security products and critical system services, from kernel mode.
Are you exposed to this one?
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (1 hidden).
This repository is a real exploit-focused research repo for CVE-2025-61155, not just a README. It documents and demonstrates a local BYOVD-style abuse path in the signed Windows anti-cheat driver GameDriverX64.sys used by Tower of Fantasy. The core exploit capability is arbitrary process termination from kernel context: an unprivileged local process can satisfy the driver's weak create-time gate by loading any DLL named QmGUI.dll, QmGUI4.dll, or gameuirender.dll, then open the exposed device \\.\HtAntiCheatDriver and send IOCTL 0x222040 with an 8-byte buffer containing magic 0xFA123456 and a target PID. The driver then performs ZwOpenProcess(GENERIC_ALL) and ZwTerminateProcess in kernel mode, allowing termination of arbitrary processes including protected AV/EDR services. Repository structure is primarily documentation-heavy, with one actual PoC source file and one YARA detection ruleset. Key files are: poc/poc.cpp (minimal C++ PoC and main entry point), advisory.md (formal advisory), docs/01-technical-analysis.md (reverse-engineering teardown of the driver internals and exploit chain), docs/02-exploitation.md (walkthrough of the abuse flow), docs/03-detection.md and detection/* (YARA and IOC content), docs/04-mitigation.md (blocklist/WDAC guidance), and docs/05-in-the-wild.md (threat-actor usage context). The vulnerable driver binary itself is intentionally omitted; sample/SAMPLE.md provides hashes, signer, and provenance instead. The PoC is operational but basic rather than weaponized: it defaults to targeting notepad.exe, uses hardcoded constants, and does not include driver installation or advanced targeting logic. Still, it clearly demonstrates the exploit chain and the main offensive outcome: local disabling of security tooling via a vulnerable signed driver already reported as abused in the wild.
Recent activity
17 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A specific vulnerable driver cited as part of BYOVD tradecraft used to disable or evade security controls during malicious operations.
A documented driver vulnerability in Tower of Fantasy that DragonForce attackers exploited in a BYOVD chain to terminate or bypass security defenses before ransomware deployment.
A specific vulnerable driver issue referenced as being abused in a BYOVD defense-evasion chain to disable security tools at the kernel level during the intrusion.
A vulnerable driver flaw in Tower of Fantasy GameDriverx64.sys abused in BYOVD operations to obtain kernel-level privileges and terminate security products.
The version that knows your environment.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.