Counter-Strike: Global Offensive has a cheating problem. It can be infuriating to come up against rule-breakers and code-busters in regular matches, but there's a silver lining here: Valve is doing its damndest to fight back.

If you go on any major Counter-Strike board right now, you'll notice a trend: thread upon thread upon thread either complaining about or cheering for VAC (Valve Anti-Cheat) bans. Much like when multiple pros got caught red-handed right before DreamHack Winter 2014, Valve has again upgraded its cheat detection orbital defense laser, and countless jerks are feeling the burn. It is, however, worth noting that no major pros have been exposed as a result of this round of bans. At least, not yet. VAC bans can sometimes occur at odd moments, so time may tell.

I have not been able to verify the scope of the bans myself, given that the big, bad banhammer only recently dropped. I've contacted Valve for more information about how they've modified VAC and just how many types of cheats they've exposed, but they've yet to reply. I'll update this post as soon as I hear back.

However, even a brief glance around CS community watering holes is enough to suggest a big impact. Players are claiming 16 different types of cheats have been forced out of the woodwork, with some calling this the biggest string of VAC bans in CS:GO's history.



Notorious cheaters like Mekelek and Broly are officially on VACation, now that rather glaring cheat detection avoidance tactics (if two players both got reported by the game's Overwatch system in the same match, reports would be discarded as spam; thus, cheaters would use the buddy system) have been patched out.

Business is booming on boards like /r/VAC_Porn, which does not, in fact, feature terrorists leaving nothing to the imagination, but rather pics of people losing their pricey items when their accounts get locked. Ahhhh, sweet, sweet schadenfreude.


I imagine we'll find out more about this in the coming days. If you've heard anything more, feel free to reach out.

To contact the author of this post, write to or find him on Twitter @vahn16.