Blizzard DDoS Possibly Linked to Second Overwatch Ban Wave



Blizzard Entertainment logoYesterday, Blizzard Entertainment enacted a second ban wave of players who were cheating in Overwatch. Many banned players complained online and some of their comments suggested they were seeking some kind of revenge on Blizzard. Not long after that, Blizzard experienced a DDoS attack. This doesn’t prove that the situations are connected – but it certainly looks suspicious.

In May, a warning was posted on the Overwatch Forums that stated: “If a player is found to be cheating – or using hacks, bots, or third-party software that provides any sort of unfair advantage – that player will be permanently banned from the game. Full stop.” In June, Blizzard banned players who were cheating in Overwatch. One would think this should have been enough of a clue that Blizzard is serious about banning cheaters.

Despite a very obvious example of what would happen to cheaters, some players decided to cheat in Overwatch anyway. This caused Blizzard to enact a second banwave. Kotaku reported:

This time around, Blizzard sniffed out players who use “triggerbots”, which shoot for players when their crosshairs appear over a target, and “aimbots,” which aid in accuracy.

A Reddit user compiled a series of screenshots of complaining comments that were posted by people who were cheating and got banned. Many of the comments are overly dramatic, and some are NSFW.

Included in the Kotaku article are a few comments that imply that some banned players want to take revenge upon Blizzard via a DDoS attack. There’s no way to know whether those comments came from people who actually know how to do that, but it definitely looks suspicious.

Yesterday and today, @BlizzardCS (the verified Twitter account for Blizzard Entertainment North America Customer Support) posted a series of tweets stating that they were experiencing a DDoS attack. It affected players ability to log in to all of Blizzard’s games and also impacted their websites.

Shortly before I posted this blog, @BlizzardCS tweeted: