"Overwatch" update notes one of the game's biggest problems which is hacking, and Blizzard is willing to take preventive measures to the next level. Despite its popularity among legitimate competitive gamers, "Overwatch" is just as popular within the cheating and hacking communities.

Like Us on Facebook

"Overwatch" hacking and cheating has been a big problem that's most prominent in Korea. In Korean internet cafe's, players can multiply dozens of Battle.net accounts from pre-installed "Overwatch" copies.

This makes it harder for Blizzard to pinpoint and track such accounts for illicit hacking activities. According to Polygon, a new "Overwatch" update notes a solution to the cheating crisis. Blizzard will now make the "necessary measures" against cheaters and hackers.

Blizzard is threatening to take legal action against cheaters or players who share and distribute any form of hacking software or applications that disrupt fair and competitive play. Starting on February 17, the "Overwatch" update notes will now include a message stating that all non-Korean accounts should require a personal copy to play the game.

According to Kotaku, Blizzard has banned over 22,000 Korean "Overwatch" accounts that were suspected for hacking. And a little over 3,000 accounts were suspended by Blizzard as well.

Cheating cases include hackers performing a sort of DDOS attack on other players, which prevents them from winning. Another "Overwatch" update notes that some players inject some sort of aim-bot an other hacks in their games granting them immediate gun-downs and extremely accurate head-shots.

The previous source even mentioned cases where hackers are publicly streaming their hacks and frustrating legitimate players by easily dispatching them with quick head-shots. The fact that most of these hackers easily multiply and create Battle.net accounts doesn't help Blizzard's cheating problem either. Fair players and legitimate "Overwatch" owners will have to wait for the February 17 "Overwatch" update notes to see if the hacking problem is rectified.