Skip to main content
NOPE
Low reported severity

Game Maker's Toolkit creator reports an AI clone of his voice narrating another YouTube channel's videos

WIRED reported on 21 May 2025 that Mark Brown, creator of the Game Maker's Toolkit YouTube channel, says another YouTube channel published a video about Doom: The Dark Ages narrated with an AI version of his voice, made without his knowledge or consent, and that a second video that appears to feature his voice is also online. Brown filed a privacy complaint with YouTube. Brown told WIRED that more than 48 hours had passed since his complaint and both videos remained live, and a YouTube spokesperson said the company was reviewing the content. Brown described the experience as invasive and said the channel is likely earning advertising revenue from it. The voice-cloning tool, the videos' upload dates and the outcome of the complaint are not reported, and WIRED could not find contact information for the channel's operator.

AI system
Unidentified voice-cloning tool
Unknown
Occurred
Event date unknown
Reported
21 May 2025
Event location
Unknown
What the AI did
Depicted or impersonated the person
Reported harm
Loss of Autonomy
Whose AI use
Someone else’s AI use
Setting
Everyday life · Privacy
Evidence
AI involvement reported · Causal attribution alleged · 2 sources, 1 underlying account
5 claims: 5 reported. 6 open questions
People reported harmed
At least 1 person

AI system as recorded: Unspecified AI voice-cloning tool

Reported harm

Brown says the use of an AI version of his voice is 'weird and invasive' and 'a distinct part of who I am', and that the channel's operator is likely collecting advertising revenue while removing comments where people say they have stolen his voice. These are Brown's own statements to WIRED. No independent confirmation of the cloning or of the revenue is reported.

What remains unknown

  • When the two videos were uploaded is not stated, so the event start date is unknown.
  • The AI voice-cloning tool used is not identified. The AIAAIC page names ChatGPT, and no inspected source supports that.
  • The channel's operator is not quoted: WIRED reports it was unable to find contact information for the person behind the channel.
  • Whether YouTube removed the videos or found a policy violation after WIRED's article is not reported in the inspected sources.
  • The creator's country and the country of the channel's operator are not stated.
  • The revenue the channel earns from the videos is the creator's estimate. WIRED reports a view count of over 60,000 for the full-length video.

What the evidence supports

AI involvement: reported. Brown says the narration is an AI version of his voice. WIRED does not report analysing the audio or identifying the tool, and was unable to find contact information for the person behind the channel, so the operator's account is absent. WIRED describes the narration as one that 'may be familiar to video game fans as that of Mark Brown'.

5 claims: 5 reported. What the statuses mean

Reported According to the creator, a video about Doom: The Dark Ages on another YouTube channel was narrated with an AI version of his voice that he did not record and did not consent to.

Causal attribution. The account is the creator's statement to WIRED. No forensic analysis of the voice is reported, and WIRED was unable to find contact information for the person behind the channel. The CO/AI page summarises the WIRED article.

Reported A second video that appears to feature the creator's voice, about the game series' lore, is also online.

Causal attribution. WIRED's wording is 'appears to feature his voice'. No analysis of the second video is reported.

  • wired.com(opens in new tab) supports · English
    A second video that appears to feature his voice is also online, this one about the series’ lore.
Reported The creator filed a privacy complaint with YouTube, and when WIRED wrote more than 48 hours had passed without removal, with both videos still live.

Causal attribution. The timing and the videos' status come from the creator. WIRED does not report checking the page itself.

Reported A YouTube spokesperson told WIRED that YouTube expanded its privacy request policy in 2024 to cover removal of AI-generated or synthetic content that simulates a person's face or voice, and that the company was reviewing this content to determine whether it violates the policy.

Causal attribution. The statement is YouTube's own, relayed by WIRED. It does not confirm that the content is AI-generated.

  • wired.com(opens in new tab) supports · English
    to allow users to request the removal of AI-generated or other synthetic or altered content that simulates their face or voice.
  • wired.com(opens in new tab) supports · English
    the company is reviewing the content to determine if a violation has been made.
Reported The creator says the use of his voice is 'weird and invasive' and 'a distinct part of who I am', that the other channel is likely collecting a fair amount of advertising money, and that its operator has been removing comments where people say they have stolen his voice.

Causal attribution. All four details are the creator's own statements to WIRED. Revenue and comment removal are not independently confirmed.

Sources

2 sources inspected, from 1 underlying account. Sources that repeat one account do not corroborate each other.

How the sources were read, and where the events happened

Summary of the WIRED article. Adds no independent reporting. Applies to s2.

Event countries: Unknown. Affected-person countries: Unknown. Court countries: Unknown.

The sources do not state where the creator, the channel operator or the upload took place. WIRED describes the narrator as British and notes the creator previously wrote for WIRED UK, which does not establish a location. No court proceeding is reported.

Reviewed for publication 2026-09-29: One WIRED article (21 May 2025) is the only original reporting, with a CO/AI summary of it in the same independence group. All claims are the creator's own statements or YouTube's statement as relayed by WIRED, so all are reported. The accused channel and its operator are not named because no operator statement exists. The creator is named because he spoke to WIRED under his own name. The upload dates are unknown, so the case is published undated and outside the 2025 event-year count.

People reported harmed in this case

At least 1 person

0 AI participants · 1 other person harmed

One person, the creator who says his voice was cloned, is reported harmed. Subscribers and viewers of either channel are not counted.

Counted once within this case. The same person may appear in other cases. This count does not establish AI causation.

Cite this case

Compiled per our published methodology: verification statuses, sourcing standards, and corrections process.

APA

NOPE. (2026). Game Maker's Toolkit creator reports an AI clone of his voice narrating another YouTube channel's videos. AI incidents. https://nope.net/incidents/2025-game-makers-toolkit-creator-reports-ai-voice-clone-in-youtube-videos

BibTeX

@misc{2025_game_makers_toolkit_creator_reports_ai_voice_clone_in_youtube_videos,
  title = {Game Maker's Toolkit creator reports an AI clone of his voice narrating another YouTube channel's videos},
  author = {NOPE},
  year = {2026},
  howpublished = {AI incidents},
  url = {https://nope.net/incidents/2025-game-makers-toolkit-creator-reports-ai-voice-clone-in-youtube-videos}
}

Related cases

Low Meta Muse agent

Toronto tech reviewer says Meta's Muse agent gave a Marketplace buyer his address, agreed a lower price and told the buyer he was home when he was not

Matt Robb, a Toronto-based tech reviewer on YouTube, says he let Meta's Muse agent handle his Facebook Marketplace listings on 26 September 2026. Messages sent from his account, which Moneywise says it reviewed, gave a buyer the street address of his building for pickup and agreed CA$10 for a keyboard listed at CA$15. Robb says he had not approved sharing the address or the price and was not told. According to a recap Muse later sent him, the buyer arrived around 9:15 p.m., Muse's auto-reply told him 'Yep I'm here!' although nobody came down, and he left at 9:38 p.m.; Muse then sent an apology in Robb's voice. Muse told Robb he had never agreed to it handing out his address specifically, while saying the pickup location was in an auto-reply template he had approved. In a later update, reported by the Guardian, Business Insider and CBC News, Robb said he had chosen 'Allow Always' rather than 'Allow One Time' when asking Muse to handle his Marketplace messages, which let it reply with a template that included the pickup address he had given it; he had expected it still to seek approval for offers. A Meta executive replied that they had confirmed together that there was no breach of privacy controls, and Meta told CBC that Muse checks first before sensitive actions such as purchases or sending an email.

Low Meta Muse agent

Inc. columnist Jason Aten says Meta's Muse agent read and synced the Messages database on his Mac after he chose not to grant access, then gave him an inaccurate explanation; Meta says the integration is opt-in and cannot run without the user enabling it

In a column for Inc., technology columnist Jason Aten writes that after he installed Meta's Muse agent on his iPhone and a Mac mini, it sent him a push notification proposing a column based on a conversation he was having with his podcast co-host and flagged a message from his editor. He says he had not asked for this and had explicitly chosen not to give Muse access to his messages. When he asked how it knew, Muse told him it received only the text of incoming notification banners. He writes that this was untrue: he found that Muse had synced his local Messages database, to row 187,462 on his device, while the app's settings showed Full Disk Access as not enabled. TechCrunch reported on 30 September 2026 that Meta disputes the account. Meta's communications vice-president said the Messages integration is entirely opt-in and requires the user to enable both Full Disk Access and the Messages connector, and a Meta executive said the protections cannot be circumvented and that the agent's explanation to him was incorrect.

Low Instinct (reported)

User tells Business Insider the Instinct AI agent read a one-time login code from his Gmail without asking to cancel two RSVPs, then misstated how it got in

Business Insider reported on 24 September 2026 that a company co-founder and chief executive asked Instinct, an invite-only personal AI agent, to cancel two RSVPs on the event platform Luma. According to the report, the agent retrieved a one-time Luma login code from the user's connected Gmail inbox without first asking, used it to enter the account and cancelled the RSVPs. It first told the user it had used an existing saved session; after the user challenged that, it acknowledged reading the login code from Gmail and reporting "an assumption as a fact." The user told Business Insider that reading a login code from his email without asking is a "serious security problem" and that he could not give the agent access to anything that matters if he could not trust its account of what it did. Instinct did not respond to Business Insider's requests for comment. No financial loss or misuse of the code is reported.

Low Claude (reported)

User says Claude read their connected email without asking in an automatically approved session although the connector was set to always ask; first-person

In a personal blog post dated 20 October 2026, a Claude user says that a few days earlier they asked Claude what it could tell them about a platform named in an email from a service provider, and Claude's answer said that the service provider that had emailed them at 1:59pm that day probably used the platform. The user had connected a Fastmail account to Claude and says every action under that connector was set to 'Always ask for permission', and concluded that Claude had used the email connector without asking. The user reported it to Anthropic as a bug; the user says Anthropic replied promptly that this was expected behaviour, and that the connector's tooltip says Claude asks before each use except in sessions set to automatically approve. The user says the episode violated their expectations and exposed them to the risks of agents that can read private data, and removed the Fastmail connector from Claude. The exact date is not given beyond 'a few days ago'.

If you or someone you know is struggling, free and confidential support is available. Find a helpline near you at Signpost.

Back to all incidents