{"id":50900,"date":"2024-04-03T07:13:51","date_gmt":"2024-04-03T11:13:51","guid":{"rendered":"https:\/\/www.kaspersky.com\/blog\/?p=50900"},"modified":"2024-04-03T08:01:42","modified_gmt":"2024-04-03T12:01:42","slug":"hacker-attacks-apex-legends-global-series-tournament","status":"publish","type":"post","link":"https:\/\/www.kaspersky.com\/blog\/hacker-attacks-apex-legends-global-series-tournament\/50900\/","title":{"rendered":"Live hack: Apex Legends esports tournament scandal"},"content":{"rendered":"

The esports industry is booming: prize pools for top tournaments have long surpassed $10 million<\/a>, with peak online viewership exceeding one million<\/a>. This naturally attracts hackers, who typically either steal game source-code<\/a> or target individual gamers. Recently, cyberattacks have gone beyond the pale: hackers disrupted a major Apex Legends tournament<\/a>.<\/p>\n

This post explores why gamers need cybersecurity, and how they can get it.<\/p>\n

What happened<\/h2>\n

During the final match of the North American leg of the Apex Legends Global Series (ALGS) tournament between the Dark Zero and Luminosity teams, a cheat configuration window suddenly popped up on a player\u2019s screen. The bewildered player also gained the ability to see in-game opponents through walls (\u201cwallhack\u201d) \u2014 a capital offense in competitive gaming, usually punishable by a multi-year or even lifetime ban. The player was disqualified, and their team received a technical defeat.<\/p>\n

\"Screenshot<\/a>

Screenshot with cheat window from the match broadcast. Source<\/a><\/p><\/div>\n

The tournament organizers didn\u2019t adjust the rules or implement additional security measures on players\u2019 computers, leading to a repeat incident a few matches later: another pop-up cheat window, wallhack, and even aimbot functionality this time. At this point, the organizers suspected something was up: cheaters can indeed be found in esports, but brazenly opening a cheat window mid-game seemed beyond belief. The match was stopped, and the tournament postponed indefinitely.<\/p>\n

Shortly after, a user nicknamed Destroyer2009 claimed responsibility on social media<\/a>, stating they exploited a remote code execution vulnerability<\/a>. However, the supposed culprit didn\u2019t specify where the vulnerability resided: in Apex Legends itself, the Easy Anti-Cheat software mandatory for esports tournaments, or another program. Easy Anti-Cheat representatives declared their software secure. Gamers worldwide await a similar statement from Respawn Entertainment \u2014 Apex Legends\u2019 developers \u2014 but so far there\u2019s been no word; however, Respawn did announce that it has already released<\/a> the first in a series of security updates.<\/p>\n

This case is unprecedented in esports. Internet issues? Sure. Hardware problems? Those happen too. But never before has a tournament been interrupted and postponed due to hackers.<\/p>\n

Esports needs protection<\/h2>\n

Of course, it\u2019s premature to draw conclusions before the investigation concludes: the tactics and methods used by the attackers, the vulnerability exploited, and the software at fault all remain unknown. However, it\u2019s likely that the Apex Legends players\u2019 computers lacked robust protection<\/a>, which could also have prevented other embarrassing situations in esports. For example, in the summer of 2023 during the Bali Major 2023 Dota 2 tournament, Russian player Ivan \u201cPure\u201d Moskalenko found himself at the center of a controversy<\/a>. Mid-match, Ivan accessed his own game\u2019s Twitch stream, potentially gaining an advantage as the stream displayed both teams\u2019 positions. Tournament organizers weren\u2019t pleased, disqualifying the gamer and handing his team a technical defeat<\/a>.<\/p>\n

\"Pure<\/a>

Pure opened up a Twitch stream of his own game during an official match. Source<\/a><\/p><\/div>\n

The tournament rules<\/a> stipulated restricted internet access from gaming terminals during matches: only Steam, Dota 2, and TeamSpeak were allowed. But simply blocking specific websites \u2014 or all extraneous resources altogether \u2014 could have been achieved with security solutions.<\/p>\n

Nuances of protecting esports players<\/h2>\n

Gamers often consciously reject cybersecurity, guided by the outdated belief that \u201cantiviruses slow games down\u201d. But the reality today is that this isn\u2019t the case: tests<\/a> show that protection<\/a>\u00a0has no impact on gameplay whatsoever.<\/p>\n

Skeptics also like to cite instances where annoying antivirus notifications popped up on the screen at crucial moments during games. Our products<\/a>\u00a0offer a special gaming mode<\/a>, which activates automatically when games (and some other applications in fullscreen mode) are launched, pausing anti-virus database updates, notifications, and scheduled computer scans. Your computer remains protected \u2014 even during the most intense esports matches, while Kaspersky Premium<\/a>\u00a0works in the background.<\/p>\n

Though it\u2019s not known for certain where exactly the RCE vulnerability used by the hacker during the ALGS tournament is hidden, we recommend that all fans of this game install reliable gaming protection<\/a>\u00a0on their combat computers.<\/p>\n

\"Kaspersky<\/a>

Kaspersky VPN Secure Connection protects gamers\u2019 privacy while maintaining a stable, blazing-fast and secure connection with minimal latency<\/p><\/div>\n

And to protect your privacy while gaming, use our ultra-fast VPN<\/a> \u2014 either standalone or included with a Kaspersky Premium<\/a> subscription. Special VPN servers in a separate \u201cGaming\u201d locations list use the optimized Catapult Hydra protocol to reduce latency, which is crucial because the lower it is, the better the gaming experience.<\/p>\n\n","protected":false},"excerpt":{"rendered":"

Hackers have long been engaging with the gaming world: from cracking games and creating cheats, to, more recently, attacking esports players live during an Apex Legends tournament. Regarding the latter, we break down what happened and how it could have been avoided.<\/p>\n","protected":false},"author":2754,"featured_media":50901,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[2683,9],"tags":[647,899],"class_list":{"0":"post-50900","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-threats","8":"category-tips","9":"tag-gamers","10":"tag-hack"},"hreflang":[{"hreflang":"x-default","url":"https:\/\/www.kaspersky.com\/blog\/hacker-attacks-apex-legends-global-series-tournament\/50900\/"},{"hreflang":"en-in","url":"https:\/\/www.kaspersky.co.in\/blog\/hacker-attacks-apex-legends-global-series-tournament\/27280\/"},{"hreflang":"en-ae","url":"https:\/\/me-en.kaspersky.com\/blog\/hacker-attacks-apex-legends-global-series-tournament\/22571\/"},{"hreflang":"en-us","url":"https:\/\/usa.kaspersky.com\/blog\/hacker-attacks-apex-legends-global-series-tournament\/29939\/"},{"hreflang":"en-gb","url":"https:\/\/www.kaspersky.co.uk\/blog\/hacker-attacks-apex-legends-global-series-tournament\/27437\/"},{"hreflang":"es-mx","url":"https:\/\/latam.kaspersky.com\/blog\/hacker-attacks-apex-legends-global-series-tournament\/27150\/"},{"hreflang":"es","url":"https:\/\/www.kaspersky.es\/blog\/hacker-attacks-apex-legends-global-series-tournament\/29835\/"},{"hreflang":"it","url":"https:\/\/www.kaspersky.it\/blog\/hacker-attacks-apex-legends-global-series-tournament\/28656\/"},{"hreflang":"ru","url":"https:\/\/www.kaspersky.ru\/blog\/hacker-attacks-apex-legends-global-series-tournament\/37236\/"},{"hreflang":"fr","url":"https:\/\/www.kaspersky.fr\/blog\/hacker-attacks-apex-legends-global-series-tournament\/21680\/"},{"hreflang":"pt-br","url":"https:\/\/www.kaspersky.com.br\/blog\/hacker-attacks-apex-legends-global-series-tournament\/22383\/"},{"hreflang":"de","url":"https:\/\/www.kaspersky.de\/blog\/hacker-attacks-apex-legends-global-series-tournament\/31169\/"},{"hreflang":"ja","url":"https:\/\/blog.kaspersky.co.jp\/hacker-attacks-apex-legends-global-series-tournament\/36174\/"},{"hreflang":"ru-kz","url":"https:\/\/blog.kaspersky.kz\/hacker-attacks-apex-legends-global-series-tournament\/27599\/"},{"hreflang":"en-au","url":"https:\/\/www.kaspersky.com.au\/blog\/hacker-attacks-apex-legends-global-series-tournament\/33444\/"},{"hreflang":"en-za","url":"https:\/\/www.kaspersky.co.za\/blog\/hacker-attacks-apex-legends-global-series-tournament\/33071\/"}],"acf":[],"banners":"","maintag":{"url":"https:\/\/www.kaspersky.com\/blog\/tag\/gamers\/","name":"gamers"},"_links":{"self":[{"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/50900","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/users\/2754"}],"replies":[{"embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/comments?post=50900"}],"version-history":[{"count":4,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/50900\/revisions"}],"predecessor-version":[{"id":50908,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/50900\/revisions\/50908"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/media\/50901"}],"wp:attachment":[{"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/media?parent=50900"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/categories?post=50900"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/tags?post=50900"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}