{"id":34544,"date":"2025-01-28T15:47:53","date_gmt":"2025-01-28T15:47:53","guid":{"rendered":"https:\/\/dejan.au\/index.php\/2025\/01\/28\/warzone-trojan-horse-theory-was-ricochets-anti-cheat-leak-intentional-dexerto\/"},"modified":"2025-01-28T15:47:53","modified_gmt":"2025-01-28T15:47:53","slug":"warzone-trojan-horse-theory-was-ricochets-anti-cheat-leak-intentional-dexerto","status":"publish","type":"post","link":"https:\/\/dejan.au\/index.php\/2025\/01\/28\/warzone-trojan-horse-theory-was-ricochets-anti-cheat-leak-intentional-dexerto\/","title":{"rendered":"Warzone Trojan Horse theory: Was RICOCHET\u2019s anti-cheat leak intentional? &#8211; Dexerto"},"content":{"rendered":"<p>Warzone Trojan Horse theory: Was RICOCHET\u2019s anti-cheat leak intentional? Activision \/ Pexels, Kemal HayitCall of Duty\u2019s highly anticipated RICOCHET Anti-Cheat was leaked to hackers, but an intriguing theory thinks that this was actually intentional. Instead of a security disaster, some think the Warzone anti-cheat leak was a Trojan Horse. Catching up to speed in the CoD and Warzone anti-cheat saga is fairly easy. Warzone (and CDL Challengers) had hacking problems and Activision announced an upcoming, proprietary RICOCHET Anti-Cheat. Then, within a day, the kernel-level driver was apparently leaked and hackers began reversing it. Another day later, Activision calmed concerns that this leak meant impending doom for the Warzone anti-cheat. The devs explained that the leaked build was \u201cpre-release\u201d and intentionally given to third parties for testing. And that\u2019s where the Trojan Horse theory comes in, as some are speculating that it was supposed to end up with hackers \u2014 as a means to sabotage them. Warzone anti-cheat Trojan Horse theory Update from #TeamRicochet: \u25b6\ufe0f RICOCHET Anti-Cheat\u2122 is in controlled live testing. Before putting it on your PC, we\u2019re testing the hell out of it \u25b6\ufe0f Testing includes providing a pre-release version of the driver to select 3rd parties \u25b6\ufe0f Readying server-side upgrades for launch\u2014 Call of Duty (@CallofDuty) October 15, 2021 As you can see from CoD\u2019s tweet, they didn\u2019t seem particularly worried about the leaking and consequent anti-cheat reversing. This lends itself to the Trojan Horse theory, which was first raised by the New York Subliners\u2019 Mavriq. The theory, in essence, suggests that \u201cthis was a controlled \u2018leak\u2019 done with a decoy file to throw cheat providers off and get them working to exploit vulnerabilities that don\u2019t exist.\u201d In doing so, hackers would be thrown off the trail of the real anti-cheat. Could malware have been hidden in the Warzone anti-cheat leak? Would be funny as hell if they hid malware in this and leaked it on purpose \ud83e\udd23 https:\/\/t.co\/iLcb3ZgmfU \u2014 Nick \u201cProReborn\u201d (@ProRebornYT) October 14, 2021 While some hope that Activision\u2019s security team hid malware in their leaked build, there hasn\u2019t been much evidence of that. Instead, Mavriq explained that the leak felt \u201cbarebones\u201d and \u201cout-of-date.\u201d So, the Trojan Horse might not be as exciting as a malware-infested build that would take down hackers from the inside. But, if it\u2019s a rudimentary \u201cpre-release\u201d build, then there\u2019s still hope that cheaters won\u2019t be prepared for the final version when it finally launches.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Warzone Trojan Horse theory: Was RICOCHET\u2019s anti-cheat leak intentional? Activision \/ Pexels, Kemal HayitCall of Duty\u2019s highly anticipated RICOCHET Anti-Cheat was leaked to hackers, but an intriguing theory thinks that this was actually intentional. Instead of a security disaster, some think the Warzone anti-cheat leak was a Trojan Horse. Catching up to speed in the [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-34544","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/dejan.au\/index.php\/wp-json\/wp\/v2\/posts\/34544","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/dejan.au\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/dejan.au\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/dejan.au\/index.php\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/dejan.au\/index.php\/wp-json\/wp\/v2\/comments?post=34544"}],"version-history":[{"count":0,"href":"https:\/\/dejan.au\/index.php\/wp-json\/wp\/v2\/posts\/34544\/revisions"}],"wp:attachment":[{"href":"https:\/\/dejan.au\/index.php\/wp-json\/wp\/v2\/media?parent=34544"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/dejan.au\/index.php\/wp-json\/wp\/v2\/categories?post=34544"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/dejan.au\/index.php\/wp-json\/wp\/v2\/tags?post=34544"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}