Riot Confirms Valorant Ban Behind Viral “Evil Tung Tung Tung Sahur” Clip

Vanguard has been central to Valorant’s competitive identity since the game’s earliest days, but the “Evil Tung Tung Tung Sahur” footage shows why a kernel-level anti-cheat system is judged as much by its response speed as its ability to stop a cheater appearing in a match at all.

Riot Anti-Cheat Director Phillip Koskinas identified the account in the viral clip as FaeL o Anacondo#br1. It was banned on September 3, 2026, after playing three games — six days before the footage spread widely on September 9 and 10. Koskinas named the cheat used as “Sysinfo,” dismissing it as “lowskill vibeslop.” The clip’s Gekko model used the bizarre Evil Tung Tung Tung Sahur visual while displaying behavior associated with wallhacks and aim assistance or auto-targeting.

That timeline matters. The video is not evidence that Riot ignored this specific account after it became a viral spectacle; enforcement had already happened. It also does not establish how Riot detected it, whether through Vanguard’s client signals, server-side analysis, reports, review, or a combination. Nor does one three-game ban prove every wallhack or targeting tool is caught instantly. The circulated profile figures — 51.0 K/D, a 1,000 Tracker Score and seven aces — underscore how disruptive even a brief cheating window can be.

Riot’s wider policy is uncompromising: aimbots and unauthorized software can bring permanent account bans, while knowingly queuing with cheaters can result in a 180-day ban. Recent enforcement also targets stream sniping and instalock tools; Valorant patch 13.05 applies temporary game bans when detected, escalating to permanent bans for repeat use. An optional on-demand Vanguard mode forms part of those anti-cheat updates.

For tournament players and organizers, the practical standard is straightforward: verify account standing, ban history and device integrity before entry. Riot acted decisively in this case, but the clip remains a reminder that fast punishment is not the same thing as zero competitive disruption.