CS2 Let Grenade Cams Turn Into Wallhacks and FACEIT Patched Before Valve
A grenade-camera exploit turned CS2 utility into live wallhacks this week, and FACEIT reaching the fix first made Valve's queue look exposed.
For about 48 hours, CS2 utility stopped being utility
There are bad CS2 bugs, and then there are bugs that make every round feel rotten. This week landed squarely in the second category. A viral Reddit post from May 5 showed players using the grenade preview camera in live matches to peek spots they were never supposed to see. A day later, another Reddit thread made the mood even worse: players were saying the trick had already spilled into Premier and Competitive and was turning mid-round utility into cheap surveillance.
That is the part that matters. This was not some obscure workshop glitch or weird warmup bug. If the reports were accurate, live ranked Counter-Strike briefly had a legal-looking information exploit that let people cook grenades, watch the little picture-in-picture camera, and get enemy info through walls. In a game where one extra body on a site can decide a whole call, that is nuclear.
Why players freaked out so fast
The panic was not just about seeing a cursed clip on social media. It was about how usable the exploit sounded in real rounds.
Players in the Reddit threads described the same pattern over and over: throw or fake utility, use the preview camera, count bodies, confirm stacks, then make the call. That turns one of Counter-Strike's oldest skill checks into a joke. Good teams are supposed to earn info with spacing, timing, sound, and risk. This bug let people skip that tax.
That is also why the community reaction was so sharp. Normal cheating accusations in CS2 get messy because everyone has a different threshold. One guy says wallhack, another guy says sound cues, another says lucky timing. This one felt cleaner. If you saw someone constantly pinning grenades and cancelling them, or spamming decoys in strange spots, players suddenly had a believable reason to think something was off.
I think that is what made this story hit harder than a regular patch-week complaint. It attacked trust, not just balance. Every suspicious rotate starts to look poisoned once players believe the game might be feeding hidden info to the other side.
FACEIT moved first, and that is the uncomfortable part
The most telling update did not come from Valve. It came from FACEIT's official subreddit account on May 6. FACEIT said it had already shipped a fix across all servers for the sv_grenade_trajectory_prac_pipreview exploit, specifically to stop players from seeing enemy positions through the grenade camera.
That is a brutal look for Valve's own queue.
Third-party platforms are supposed to be the ones reacting around the edges. Here, FACEIT looked like the adult in the room. It saw a competitive-integrity problem, locked it down server-side, and told players it had done so. Meanwhile, Premier had to sit there under a cloud of "is this actually working in my games right now?"
Even if the exploit window was short, that sequence matters. CS2 ranked has spent too much time lately making players argue about whether a bad loss came from cheats, bugs, desync, or plain tilt. When a third-party platform can patch faster than the developer, it tells players exactly where they should trust the ladder less.
Valve's May 7 patch looks like the quiet kill shot
Valve's May 7 update notes were framed like a routine patch. The headline items were easy to skim past:
Cache hole fixes and clipping cleanup n- NIGHTMODE II music kits in the store
Deathmatch score value changes and XP limit adjustments
A handful of misc fixes
Buried in the misc section were two lines that stand out in this context: Adjusted player model occlusion bounds and Fixed a case where map guides for Ancient wouldn't load in the nighttime version.
Valve did not write "we fixed the grenade-camera wallhack." That part is inference, not a direct statement. But the timing is hard to ignore. The exploit blew up on May 5 and May 6, FACEIT pushed a server-side block on May 6, and players immediately started posting on Reddit on May 7 that the bug appeared fixed after the patch landed.
So yes, the likely read here is that Valve quietly killed it without calling it out by name. That happens all the time with security-style fixes. Developers do not always want to spotlight the exact hole they just closed. Fair enough.
The problem is that silence also leaves players guessing about the size of the blast radius. Was this live in every queue? For how long? Did Valve log abuse? Are punishments coming, or is this another one of those "patch it and move on" episodes? Right now, players do not have those answers.
The real story is bigger than one exploit
The nasty detail here is not just that a bug existed. It is the kind of bug it was. This was not a classic external cheat story. It looked like official practice-mode or guide-related functionality bleeding into live competition where it had no business existing. That should make every CS2 player a little uneasy, because it suggests the boundary between training tools and ranked play still is not hard enough.
CS2 has had plenty of patch weeks lately. Some were chaotic, some were harmless, some were even pretty good. This one exposed something simpler: players can live with rough edges, but they do not forgive hidden info. The second utility starts doubling as a drone feed, the match stops being Counter-Strike.
Valve probably closed this one on May 7. Good. But the lasting image of the week is still ugly: for a brief stretch, players believed a cooked decoy could tell more truth than a teammate holding the angle, and FACEIT was the first place that looked ready for it.