Uncovering The Specific CCT Match Fixing Evidence That Prompted The Abrupt Competitive Retirement Of AntyVirus

Miłosz “AntyVirus” Konieczka posted what he called a “final post” on X on June 2, 2026, announcing he was leaving Counter-Strike. He had been active in tier-two and tier-three European CS for five years, most recently playing for DragonClaw, the organization-less Polish team formerly known as Oramond and briefly VRSDelivery. His exit came less than 24 hours after CYBERSHOKE operations manager Emil “VigoV” Khakimov put out a public post naming him and his teammates in what amounted to a documented accusation package: screenshots of alleged match-fixing discussions and voice clips connected to DMA radar cheats.

This was not an anonymous forum rumor. The material was compiled by CYBERSHOKE’s captain Daniil “alpha” Demin, who said on X that someone he refers to only as “Person X” claimed they sold radar cheats to AntyVirus directly. According to alpha, Person X provided screenshots of match-fixing arrangements. Alpha said he then ran the voice recordings through multiple verification sources, including players zur1s and innocent, before going public. CCT confirmed to HLTV on June 1 that it had opened a formal investigation into the former Oramond squad. The team was actively competing in CCT 2026 Europe Series 3 at the time.

What exactly did the allegations include?

Two separate types of misconduct were alleged, and that combination is worth paying attention to. The first was match-fixing: that members of the squad had agreed to lose matches deliberately, with the outcomes tied to betting activity. The second was DMA cheat usage. Direct memory access hardware reads data from a target system externally, meaning standard software-based anti-cheat tools may not catch it the same way they would a conventional cheat client. When this category of allegation surfaces in lower-tier CS, it tends to prompt a different kind of concern than the usual VAC ban or ESIC case, because the core question becomes whether the detection infrastructure in place was ever capable of catching it.

AntyVirus pushed back in his retirement post. “For past 5 years I was trying my best to leave ‘underground’ and become professional player and for past 5 years i’m all the time accused of cheating or other stuff,” he wrote. He said he had recorded POV footage with OBS, used integrity cameras, sometimes two cameras at once, and ran kernel-level anti-cheat software. He also told HLTV separately that he considered the accusations false and was willing to cooperate with ESIC. Following his announcement, alpha posted that Person X had told him the plan was for AntyVirus to “take all the blame” on himself, and called on investigators to continue examining the rest of the team.

Those who want to follow this story from the source can read the full HLTV report.

Why did CCT get involved so quickly?

CCT’s response speed was not purely reactive. Thunderpick, the betting platform and tournament sponsor, also committed to its own investigation after VigoV’s post circulated. According to reporting from bo3.gg, CCT confirmed its investigation on June 1, the same day the public posts went up. The fact that both a tournament organizer and a betting partner moved within hours suggests the matter landed in front of people already watching for suspicious activity around that bracket.

This is part of a broader structural shift in how lower-tier CS operates. For anyone tracking major esports stories, a good gaming news website covers how CCT moved to align with Valve’s regulations from 2025 onward, requiring invite decisions to be based on the VRS and published when a team is disqualified. Part of that context is that tournament operators now face more reputational exposure when integrity problems surface in events they run. Doing nothing quickly is no longer neutral.

Was DragonClaw already under scrutiny before June 2026?

Yes, and by more than one organization. According to HLTV’s reporting on the DragonClaw investigation, ENCE issued a statement in 2025 raising competitive integrity concerns ahead of their YGames Pro Series Season 5 final against M1. That M1 roster featured several players who now make up DragonClaw. On Liquipedia, the team’s history shows the core originally came together under the Oramond name on September 30, 2025, after Reason Gaming parted ways with the roster. They went through two name changes before settling on DragonClaw in late May 2026, barely days before the allegations became public.

That pattern, a group of players cycling through names without an organization behind them, competing mainly in online CCT events, is exactly the environment where oversight can lag. ESIC’s previous investigations into tier-two match-fixing have produced formal bans: in May 2025, multiple ATOX players received lifetime bans after a 15-page ESIC report documented over 70 suspicious transactions tied to an underground Chinese betting syndicate. In April 2025, ESIC handed a lifetime ban to Swedish player Joel “joel” Holmlund after finding hardware cheat software on his PC during CCT Season 2 European Series #9. Both cases ran through CCT infrastructure before formal sanctions came down.

What does AntyVirus’s retirement actually resolve?

Practically speaking, not much. Retirement is not a ban. ESIC’s investigation, confirmed at the time of AntyVirus’s post, does not stop because the subject stops playing. In fact, if other team members continue to compete under the DragonClaw name, the inquiry into the broader squad remains open regardless of one player stepping away. Alpha specifically said he hoped the investigation would continue examining the full roster, not treat AntyVirus’s exit as the end of the matter.

For the competitive scene, the case is another data point in a long argument about whether CCT-level tournaments have enough infrastructure to handle integrity problems before they shape bracket outcomes. The CCT format is important: teams compete in online series with significant VRS points implications that feed into Major qualification. Matches where results were manipulated, if that is what investigators ultimately find, would have affected points totals for other teams trying to reach events like IEM Cologne. That is the part that gets lost when coverage focuses only on the retirement announcement.

What happens next with the ESIC investigation?

No formal sanctions had been issued against AntyVirus or DragonClaw as of the time of his announcement. ESIC’s process typically runs from investigation to notice of charge before any ban is confirmed. Past cases have taken weeks to months. Given the complexity of allegations involving both match-fixing and alleged hardware cheating, and the fact that the evidence includes voice recordings that AntyVirus himself suggested could be AI-generated or manipulated, the evidentiary process is unlikely to move quickly.

The community will be watching whether CCT acts unilaterally in the meantime, whether to suspend the remaining DragonClaw players from active events while the inquiry runs, or whether the investigation runs its formal course before any competitive consequences follow. Either way, the story is not over because one player said he was done with the game.