World of Warcraft GM accused of cheating to save a Mythic+23 run
A developer-only ability wiped an enemy at 89.3% health, letting a group beat a Mythic+23 dungeon with 14 seconds left. The ability’s tooltip reads: “Kills all enemies in a 30 yard radius. Cheater.” Blizzard says it’s reviewing.
Somewhere in Blizzard’s internal toolset there is a spell called Area Death (TEST). It kills everything within thirty yards instantly. Its tooltip, written by a developer at some point for other developers, ends with a single word.
“Cheater.”
On July 21, that ability showed up in a live World of Warcraft competitive dungeon run.
What the logs showed
The dungeon was Nexus-Point Xenas, one of eight in the current Season 1 Mythic+ rotation. The group was running it at key level 23 — high enough that clearing it in time is a genuine achievement, and one that carries a seasonal title.
They were not going to make it. Then an enemy sitting at 89.3% health simply died, and the group finished with 14 seconds on the clock.
The log shows the kill came from Area Death (TEST), cast by a character named Daijosai. Daijosai was not one of the five players in the group. A second developer ability, Death Touch, hit a boss near the end of the same run.
Game masters are Blizzard employees with elevated in-game permissions, normally used to resolve support tickets and stuck characters. Not to finish keys.
They brought a stranger
Here’s the part that decided everything, and it’s the detail most of the coverage skipped.
The group’s fifth was a pickup tank. A random. And that random was running combat logging, which uploads the entire fight — every ability, every cast, every source — to Warcraft Logs automatically.
So the run got published. A Reddit user going by Acrobatic_Pianist688 pulled it apart and posted what they found on July 21, and the thread moved fast.
Wowhead’s Peyton “Tettles” Tettleton then cross-referenced the log timestamps against third-party tracking data and confirmed the run matched a real completed dungeon, which killed the obvious defense that somebody had doctored a log for attention.
Four people knew. The fifth had a tape recorder.
The confession
The logs were damning but circumstantial. What ended the argument was one of the players going on stream and explaining it.
Appearing on YumyTV‘s Twitch channel, a group member — the streamer known as Yiesus — said the group finished the final boss and realized they were short on the required enemy count. So he asked a friend who works at Blizzard, in voice chat, for help.
His words: “I’m like, ‘bro, please, can you do me a solid.’”
He said he meant no harm, that he hates “homework keys,” and that he didn’t actually expect his friend to do it. He allowed that in hindsight his friend shouldn’t have. He also said he doesn’t much care if Blizzard strips the run and the title, because he considers the whole thing harmless.
PC Gamer‘s account of the incident: the GM did this without realizing it was being recorded.
Blizzard’s answer, and what’s missing from it
Community manager Randy “Kaivax” Jordan replied late Tuesday, both on the official forums and in the Reddit thread that started it.
“Thank you to those who flagged this. We are reviewing and will take action as appropriate. A fair and competitive playing field is essential to our games, and we won’t tolerate cheating.”
Read it again and notice what isn’t in it. No mention of an employee. No mention of a game master. No mention of the account, the run, the title, or whether anyone still works there. Thirty-eight words about cheating in general, from a company whose own staff member is the accused.
That’s a statement written by people who know exactly how bad this is and have not yet decided what to say about it.
Why a +23 key is worth cheating for
For anyone outside WoW wondering why a five-person dungeon triggered a corporate statement: Mythic+ is the game’s competitive treadmill. Keys scale in difficulty, each level is timed, and the top brackets are where a small slice of the playerbase measures itself.
The titles are the point. They’re seasonal, they’re visible to everyone, and the ranking sites that track them are a public record of who cleared what.
Which is what makes “it was harmless” a difficult position. A title that fewer than one in a thousand players earn is worth precisely what it costs to get, and this one cost a favor.
What happens next
Blizzard has a track record here. It banned boosting organizations outright, and it is currently in court against private server operators over what its filing calls large-scale and ongoing infringement. The company does not typically let competitive-integrity stories fade.
The run can be wiped. The title can be revoked. Both are trivial for Blizzard to do.
The harder question is the one Kaivax’s thirty-eight words carefully stepped around, and Blizzard hasn’t answered it yet.
Article compiled and edited by Derek Gibbs (entertainment editor) and the Clownfish TV newsroom.
D/REZZED is part of Clownfish TV. For more news, views, and rants on gaming, tech, and pop culture, visit clownfishtv.com. Watch the show on YouTube at @ClownfishTV where new episodes drop daily. Subscribe to the Clownfish TV podcast on Apple Podcasts, Spotify, iHeart, and wherever else you get your podcasts. Sign up for the free newsletter at more.clownfishtv.com.
Hat Tips:
Warcraft Logs (July 21, 2026) — the primary combat log showing Area Death (TEST) and Death Touch, the casting account, and the fight timing
Blizzard official forums and Reddit — community manager Randy “Kaivax” Jordan’s full statement, and the origin thread from user Acrobatic_Pianist688
YumyTV (Twitch) — the stream on which a member of the group described asking a Blizzard employee for the kill
Kotaku — the Area Death (TEST) tooltip text and the identification of group members
PCGamesN — the Nexus-Point Xenas dungeon context, the 89.3% health figure, and the 14-second finish
PC Gamer / GamesRadar — the Mythic+23 details, the GM permissions explanation, and Blizzard’s competitive-integrity history
GamesHub — the detail that the log was uploaded by a pickup tank who had been logging the key
Dexerto (Cande Maldonado) — Wowhead’s Tettles verifying the log against third-party tracking data