Peeling the Onion: Forensic Dissection of the Evolution of FPS Cheats, a Red Teamer's View on Windows Memory Security
Feb 5, 2027 — 04:00 pm - 4:50 PMGarden ABC
Speakers:
You need to register and log in to access this functionality
Already registered? Log in now to personalize your experience!
Abstract
A 48 GB memory image, a few cheat families, some weeks of evenings. I red-team for a living, but competitive FPS is where the memory-safety fight is loudest, so I got hold of several generations of cheats, each built to survive whatever killed the one before.
The first is plain software with a stolen EV certificate. The second goes physical: a custom DMA card and a second PC. The third gives up on userland — a compact kernel driver that speaks TCP from ring 0, discovers its operator over UDP, and encrypts its channel with a date-derived keystream. Verified byte by byte against pcaps.
This is a forensics talk, not a cheating tutorial. I got things wrong: two early conclusions turned out false, and I'll show how cross-validation caught them.
I close with a clip of my clean-room re-implementation, reading memory it was never meant to read.
It does.





















