Blizzard GM Cheats a WoW +23 Key for a Streamer

A Mythic+23 key cleared with 15 seconds to spare, a boss that dies for no apparent reason. A sixth character even shows up in the logs, an actor who doesn’t belong to any of the five official players. That’s the starting point of a story that’s been shaking World of Warcraft for the past few hours, dissected by ZiL XP on his YouTube channel. A Blizzard GM allegedly used their admin powers to save the run for a group that included a streamer in its ranks.

The evidence is public, one of the players admitted to it live on Twitch, and Blizzard has confirmed it opened an investigation. This isn’t the studio’s first public clarification this year, after the warning issued to a French-speaking creator. Here’s the full case file, with links to every source.

A +23 Key Saved by a Blizzard GM

On July 17, 2026, a group clears a Mythic+23 key in Nexus-Point Xe’nas, one of the dungeons from Midnight Season 1. Timer cleared: 29 minutes and 46 seconds. Nothing alarming at first glance, this kind of run happens by the hundreds every week. Except one detail in the logs was about to change everything.

It’s a Reddit user, u/Acrobatic_Pianist688, who stumbles onto the anomaly while browsing random logs. Their post on r/wow sets things ablaze in under an hour. The group shows five players, like any Mythic+ key. But a sixth actor appears in the report, a character who was never part of the official group and isn’t listed anywhere on the player side.

The Warcraft Logs report shows this ghost presence at the exact moment several enemies die for no apparent reason, outside any normal dungeon mechanic. No player spell matches these deaths. The bug hypothesis quickly collapses given the nature of the spells used.

Peyton « Tettles » Tettleton, a journalist at Wowhead, picks up the story before some links go dead. He manages to archive screenshots showing the evidence while it’s still working, letting the story keep circulating despite the cleanup attempts. A Blizzard GM (Game Master) does indeed appear to have gotten involved. He allegedly handed a validated key to a group that included a streamer.

The Logs That Point the Finger: « Area Death (TEST) » and « Death Touch »

It all comes down to Warcraft Logs. The site records every hit landed during a fight, including the ones that have no business being there. In this key’s report, two spells immediately stand out: « Area Death (TEST) » and « Death Touch ». Neither exists in any spell list available to a player. These are development tools, normally reserved for Blizzard’s internal testing.

The caster’s name is already a first problem. The log attributes these spells to a certain Daijosai, who’s absent from the five-player roster attempting the key. This name appears in several numbered copies in the report, as if the same character existed four times simultaneously in the instance. A normal player can’t duplicate their own avatar. An account with admin rights, on the other hand, can summon a ghost entity to perform a specific action, then make it disappear. That’s exactly the kind of move a Blizzard GM can pull off behind the scenes.

The numbers tell the rest of the story. On one of the trash packs, the target hit by « Area Death » still had 89.3% of its health at the moment of impact. On the final boss, Lothraxion, it’s « Death Touch » that hits while it has 1.4% health left. Peyton « Tettles » Tettleton, a Wowhead journalist, cross-referenced these values with the total damage still needed before the timer ran out. The math comes out to roughly 17 million health points to close, in just 15 seconds. A gap that no comp, however optimized, could have bridged at that stage of the key.

There was still one thing to check: whether this report itself had been faked. The Mythic+23 key for Nexus-Point Xe’nas is indeed listed on Raider.IO, with a timer of 29 minutes and 46 seconds. That figure matches the log exactly, dated July 17, 2026. Raider.IO operates independently from Warcraft Logs: the two platforms share neither a database nor a recording source. The fact that both versions match rules out the possibility of a report doctored after the fact.

Two links let you verify all of this without a middleman. The full report can be checked on Warcraft Logs, with the death details and spell sources. Wowhead’s analysis, which covers every figure cited here, is available on this page.

In the clip, Yiesus tells the story straight. The group finishes the fight against the last boss, looks at the health bar, and realizes some percentage is missing. His first thought is an execution error, a pack skipped on the first pull. His second thought, far less innocent, is to go ask for help from his contact at Blizzard.

The original clip on yumytv’s channel, where the player himself recounts his request to the Blizzard GM.

The message he describes sending to his Blizzard GM fits in one sentence. Do me a favor, look at this thing with 20 million health, can you one-shot it? Just this once. This isn’t a joke told after the fact to justify himself, it’s the actual request, admitted publicly, mic open.

Look, I didn’t want to hurt anyone. If Blizzard wants to void this key or take my title away, that’s fine, I don’t mind. Personally, I think it was harmless. Looking back, I shouldn’t have done it.

Yiesus, live on yumytv’s channel (full clip)

ZiL XP points out the logical flaw in this defense. Saying the cheating didn’t hurt anyone ignores one simple detail: this same dungeon was cleared, fair and square, by players who got no admin boost whatsoever. And the « I’m willing to give back the title » argument sounds different once you remember the key is dated July 17, five days before the story broke. Nobody gives back a title out of professional conscience before getting caught.

One motive, though, is far from trivial: the PUG tank needed to clear this specific dungeon to earn his seasonal title. A player outside the small friend group, whose progress depended on this run, and who happens to be the one who left a trace in the logs.

Why a +23 Isn’t a Victimless Cheat

To understand why this story is causing such a stir, you need to know what a title key is. Every season, World of Warcraft hands out a special title to the best Mythic+ dungeon players. This title isn’t given to everyone. It’s reserved for the very top of the leaderboard, historically around the top 0.1% of the season’s players. In other words, a handful of people out of hundreds of thousands.

This detail completely changes the nature of the problem. A +2 or +20 key finished with a Blizzard GM’s help steals nothing from anyone. These are tiers that almost every active player reaches without any trouble. Nobody watches this leaderboard, nobody fights for a spot on it. It’s a bit like a Blizzard GM teleporting you into an old raid to hand you invincibility. You’re not taking that invincibility from anyone, since nobody was competing for it.

A +23 works differently. The title leaderboard is a zero-sum game: there’s a fixed number of spots. Every score that climbs pushes another one below the cutoff line. If a group artificially clears a score it didn’t earn, someone else, somewhere on the leaderboard, ends up mechanically shut out of the title they would have legitimately gotten. It’s not an « extra » key, it’s a spot taken from someone else.

What makes the excuse hard to defend is the rest of the player’s reasoning. He explains he doesn’t like keys he calls a chore, the ones you redo just to check a box. Except that’s exactly the point of competitive Mythic+ play: farming keys you don’t need, restarting the ones that fail. Taking the failure until it finally goes through is part of the game. Remove that constraint, and you remove the challenge itself.

• Seasonal title reserved for the very top of the leaderboard, historically the top 0.1%
• Relative score: every point gained costs someone else a spot
• Low key (+2, +20): no impact on this leaderboard
• Title key (+23 and above): direct impact on who does or doesn’t get the title

Do the math yourself. Just pinging someone on Discord and getting a coherent reply takes time. « Yo come help us », « wait, what are you talking about », « come on, log in, we need to kill something », that exchange alone already eats up a good chunk of the 15 seconds available. Add launching the client, the login screen, loading the map, the dungeon. Add teleporting to the right monster and pressing a spell powerful enough to drop it in one hit. According to ZiL XP, it simply doesn’t fit inside the stated time window.

Hence the alternative theory: what if the Blizzard GM was already there, well before the call for help? A fourth instance of the same character would suggest a presence that had been set up for a while, not an account just opened in an emergency. Nothing proves this formally, the analysis remains a reading of partial logs and a guess, but the gap between the actual timing and the story told is hard to ignore.

One detail further complicates any independent verification of the facts. Of the group’s five players, four weren’t logging their run, only the PUG tank was recording his session. So it’s impossible to cross-reference multiple viewpoints or timestamps to confirm or disprove the timeline given by the players themselves.

There’s also the question of the « clean » key. Sure, the tank supposedly skipped a pack, but he’s not the only one who stumbled during this run. Several players died at different points in the key, which puts the idea of one isolated, fatal mistake in perspective. One slip among others, on a run that was already far from flawless.

X Account Deleted, Key Wiped: The Trail Vanishes

One detail caught the community’s attention even before Blizzard reacted. The person who posted the logs claims this alleged Blizzard GM helped a group land its +23. The suggested motive: a soft spot for his favorite streamer. A claim to take with a grain of salt since no hard evidence confirms this link. One thing did catch the eye of amateur sleuths on Reddit and Discord: one of the group’s members is a female streamer. The alleged Blizzard GM’s X account had been publicly interacting with her for a while.

Digging back through these old public exchanges, several players found birthday messages and other signs of interaction that suggest a prior relationship rather than a random encounter through a support ticket. Nothing proves this link explains the intervention on the Mythic+23 key, but the coincidence was enough to fuel speculation as the story spread.

The timeline of the account’s disappearance is itself telling. In Tettles’s video, published the night after the events, the X account is still visible, but switched to protected mode, viewable only by its followers. A sign its owner had realized the story was starting to spread. A few hours later, as other content creators picked up the topic, the account simply no longer existed. Deleted, with no explanation, no archive left behind.

While this digital cleanup was underway, Blizzard eventually broke its silence. The response came from Randy « Kaivax » Jordan, Community Manager, on the official forum thread where the issue had been reported.

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.

Randy « Kaivax » Jordan, Community Manager Blizzard

A carefully worded statement that speaks for itself, neither confirming nor denying the facts, but officially acknowledging that an investigation has been opened. The studio is no stranger to sensitive cases these days, between its lawsuit against Project Ascension and recurring tensions with the community.

It’s also around the time of this response that the most concrete trace of the incident vanished in turn. On Raider.IO, the July 17 run no longer appears in the affected players’ history. The tank did show a Nexus-Point +23 dated the 17th, now erased, while the group’s healer now only has a +23 dated July 12, a week earlier, with a different lineup. The points were pulled, the leaderboard corrected, as if the run had never happened. Wowhead documented this return to normal in its coverage of Blizzard’s response.

On the punishment side, ZiL XP gives his take in the video that started this whole story. For him, the players clearly cheated and admitted it on stream by acknowledging they asked a GM for help. A sanction seems logical to him. His reasoning goes further regarding the GM themselves: the role is supposed to embody a form of authority and neutrality, a bit like a referee on a field. If the referee cheats, the offense takes on a different dimension. The video’s author believes stripping the GM role and its powers would be the bare minimum, without necessarily going as far as termination, while admitting a firing wouldn’t surprise him either.

What strikes him most is discovering that GMs capable of stepping directly into the game still exist at all. The last visible GMs, in robes, casting spells among players, date back to the Vanilla era, around 2004-2006. Since then, that kind of contact has become so rare it’s nearly vanished from the regular game experience.

Today, most support goes through tickets, with sometimes slow replies and human contact kept to a minimum. Whispered messages with the small Blizzard icon next to the name, once a sign a GM was replying directly to a player, have become a rarity. Seeing an active in-game GM resurface, in this exact context, raises a simple question: that kind of support still exists somewhere in the organization, but under what conditions can an ordinary player hope to access it? The topic adds to an already packed year for the studio, which is simultaneously waging a twenty-year war against private servers.