Blizzard Fires Employee Over GM “Death Touch” Mythic+ Incident

Blizzard has confirmed that an employee used development-only spells to give a World of Warcraft group an unfair advantage during a +23 Nexus Point Xe’na Mythic+ run. The employee responsible is no longer with the company, and Blizzard is also taking action against player accounts that were complicit in the incident.

Blizzard Confirms Employee Misused Developer Spells

The official response was posted on the World of Warcraft forums by Blizzard community manager Kaivax.

“We can confirm that this was the action of a single Blizzard employee, in violation of our Code of Conduct. This employee is no longer with the company effective immediately. We are also taking action against the player accounts that were complicit in this violation.”

Blizzard explained that a limited number of employees have access to developer tools and spells on live World of Warcraft servers. These tools are intended for testing and urgent fixes, and every use is logged and shared with Blizzard’s Platform Security team. Blizzard said its internal monitoring showed that the incident was isolated to one employee.

What Happened During the +23 Nexus Point Xe’na Run?

The incident surfaced after a Warcraft Logs report showed a character outside the five-player group using a development-only “Death Touch” effect. The spell reportedly helped the group defeat enemies and complete the dungeon before the Mythic+ timer expired.

The run was recorded through Blizzard’s API and appeared on Raider.IO as a completed +23 Nexus Point Xe’na. Raider.IO administrators later invalidated the result while leaving its page available for reference.

According to the WoW subreddit’s GM Death Touch megathread, the Demon Hunter from the run later discussed the incident during an interview with Growl, also known as Yumytv. The player claimed the group was joking with a GM friend in Discord during a “homework key” and did not expect the employee to actually intervene.

Pug Bear Tank Says He Was Unaware of the GM Intervention

The Guardian Druid tank was reportedly a pick-up player who was not part of the group’s Discord conversation. Reddit moderators shared the following statement after the tank contacted them through modmail:

“I want to address the situation surrounding the +23 NPX run. At the end of the run I noticed we were off count by .7 or so and I was confused until I realized we didn’t grip in and tag the arcanist on pull 1. I futilely pulled the lingering image with I believe like 30-45 seconds knowing we didn’t have time or damage to kill and it just flopped over at 80%. I thought it was some strange coding or weird interaction with pulling on the bridge.

This led me to try and upload the logs to see what happened. I’m pretty new to that in general as I generally pug all my keys and someone else is usually logging and as a tank I don’t really care about parsing through them as much as I maybe should.

I have not been banned as of yet regarding the incident. (Hopefully will remain that way but of course perfectly happy to redo my NPX)

To the best of my knowledge I was not aware that any GM intervention had occurred while we were playing.

I appreciate all my friends who have vouched for me as not a buyer or an exploiter. I was getting spammed a ton by people in game claiming I was one or both of those the last two days and just wanted to say my peace on here.”

The tank said he uploaded the combat log specifically to understand why the enemy suddenly died. That uploaded log ultimately helped the WoW community identify the use of the unauthorized developer spells.

What Action Is Blizzard Taking?

Blizzard has terminated the employee responsible and confirmed that action is being taken against complicit player accounts. The company did not identify the players being penalized or specify the exact suspensions or account penalties being issued.

Blizzard also thanked community members who reported the incident and community websites working to remove the affected result from their records. According to the development team, the community’s findings aligned with Blizzard’s internal monitoring and helped confirm that its security tools detected the misuse.