Case Library / Deepfake & Synthetic Media / WPP deepfake scam: a fake Mark Read, a cloned voice, and a target who said no (2024)

WPP deepfake scam: a fake Mark Read, a cloned voice, and a target who said no (2024)

Fraudsters faked WPP CEO Mark Read on WhatsApp and staged a Teams call with a cloned executive voice. The agency head said no. Why that matters.

Share:

Social Engineering Examples·6 sources

The WPP deepfake scam is a case that failed, which is exactly why it's useful. In 2024, fraudsters set up a WhatsApp account using a public photo of Mark Read, chief executive of the world's biggest advertising group. From it, they arranged a Microsoft Teams meeting that appeared to include Read and another senior WPP executive. On the call they played an AI clone of that second executive's voice over old YouTube footage of them, while "Read" chipped in through the text chat. The target, a WPP agency head, was asked to help set up a new business. Read's internal email said the goal was personal details and money. The agency head didn't bite. Public reporting: 10 May 2024. Status: Attempt failed; nothing lost; attackers unidentified.

Key takeaways

  • Nobody ever got as far as asking for a payment. A person stopped it at the pretext stage.
  • Only the voice was synthetic. The video was existing public footage, and the "CEO" was text-only.
  • A public photo, a few YouTube clips and a messaging app were all the raw material needed.
  • The meeting invite came through WhatsApp, not the company calendar. That was the clue.

How it worked

Layer What the attackers did
Fake profile A WhatsApp account with a publicly available photo of Mark Read
Fake meeting A Teams call, set up from that account, seemingly with Read and a second senior executive
Synthetic voice An AI clone of the second executive's voice, played alongside existing YouTube footage of them
Text-only CEO "Read" stayed off camera and typed in the meeting chat
The ask Help set up a new business. Per Read's email, the real aim was personal details and money
The outcome The agency head found it suspicious and didn't go along with it

WPP never said what tipped the executive off. No glitchy video, no telltale audio artefact was reported. A spokesperson credited "the vigilance of our people, including the executive concerned". In other words, the request itself, or the way it arrived, felt wrong.

Tip: a meeting invite from a senior leader that arrives via a personal messaging app rather than the corporate calendar is a red flag on its own, before anyone says a word.

Whose voice was cloned?

Here's a genuine ambiguity in the record. The Guardian, which obtained Read's email, wrote that the impostors "deployed a voice clone of the executive as well as YouTube footage of them". Which executive? Coverage split. Some outlets (the FT headline, the New York Post) read it as Read's voice. TechRadar, quoting the same email, said the second executive was the one cloned and that the fake Read only took part via chat.

This page follows the second reading. It fits The Guardian's next sentence, that Read was impersonated "off-camera using the meeting's chat window", which would be odd if his voice were also live on the call. WPP never named the second executive or the agency head, and never gave the date of the attempt.

Why a failed attempt matters

This came a few months after the Arup deepfake, where a video call full of synthetic colleagues led to HK$200 million in transfers. WPP shows the same playbook aimed inward, at a company's own senior staff, and shows it failing.

Think about where it failed. The attackers got a target onto a call and delivered their story. That's all they managed. They never reached a payment request, so payment thresholds, callback rules and dual authorisation never came into play. Those controls can't be what saved WPP. A person did, at the earliest and cheapest moment to catch it. A case that ends in a wire teaches you to harden the wire. This one teaches you that the decisive control sits upstream, in whether an odd request on an odd channel gets checked before anyone acts.

Read's email put it plainly to staff: "just because the account has my photo doesn't mean it's me". He also noted that senior leaders face more tailored, psychological attacks than the general public does.

What stops it

  • Verify unusual requests out of band, on a channel you already use with that person, no matter how convincing the voice or video.
  • Treat personal-app meeting invites as suspect. Real executives use the corporate calendar.
  • Train leaders specifically. Generic phishing awareness doesn't cover "your CEO is on a call asking for a favour".
  • Assume your public footage is attacker material. Interviews, panels and press photos are enough to build a clone.
  • Reward the person who says no. WPP publicised the near miss. That's how the next target knows what to look for.

See also deepfake examples, voice cloning and CEO fraud.

Common questions

What was the WPP deepfake scam?

An attempt in 2024 to trick a WPP agency head using a fake WhatsApp profile of CEO Mark Read, a staged Teams call, an AI voice clone of a second executive and old YouTube footage. The target was asked to help set up a new business. It failed.

Did WPP lose any money?

No. No payment was ever requested and no data was lost, according to WPP and Read's internal email.

Was Mark Read's voice deepfaked?

Probably not. The best reading of the reporting is that the second executive's voice was cloned, while the fake "Read" took part only through the meeting's text chat. Some outlets reported it the other way.

How was the scam detected?

WPP credited the vigilance of the targeted executive. No technical detection was reported.

Sources
  • CEO of world's biggest ad firm targeted by deepfake scam. The Guardian (secondary). The article that obtained Mark Read's internal leadership email, and the closest thing to a primary record this case has. Its account of the operation runs to about five sentences, and this file quotes them rather than extrapolating past them. It carries the direct email quotes and the WPP spokesperson statement. Re-fetched 2026-09-02: the live page truncated mid-article on extraction, so the full text was read through the Wayback Machine capture of 24 December 2024.
  • WPP boss targeted by deepfake scammers using voice clone. Financial Times (secondary). Paywalled, and verified to its headline only. Re-fetched 2026-09-02: the page title renders as "Subscribe to read" and the headline is the only body text available. Several outlets credit the FT as their source, but nobody on this project has read the article, so no mechanical detail in this file is attributed to it. The headline on its own is one reason coverage drifted toward "Read's voice was cloned."
  • Top WPP advertising executive hit by scammers using voice cloning attack. TechRadar (secondary). Quotes the email directly and gives the clearest statement of the reading this file follows on whose voice was cloned. Its own introductory summary loosely says "deepfake videos", which its detail sentence does not support; the detail sentence is what is relied on here. Fetched and confirmed 2026-09-02.
  • WPP chief exec Mark Read targeted by deepfake scammers. MM+M, republished from Campaign UK (secondary). Quotes the email and the WPP spokesperson statement, and is consistent with The Guardian throughout. Fetched and confirmed 2026-09-02.
  • AI voice, fake WhatsApp account: How scammers targeted CEO of world's biggest ad firm using deepfake. The Times of India (secondary). Quotes the email accurately, but contradicts itself on whose voice was cloned: its lede has the scammers using "Read's voice clone and public YouTube footage", while its detail sentence four sentences later says "a voice clone and YouTube footage of the other executive was used while scammers impersonated Read off-camera using the chat function." Cited here for the email quotes and as evidence of the split, not as a source that settles the point. Fetched and confirmed 2026-09-02.
  • Information on the fraudulent use of WPP's name and those of its agencies. WPP (first-party, general fraud notice, not about this incident). A standing corporate notice that WPP's name and its agencies' names have been used fraudulently by third parties on unofficial websites and apps. Read in full and confirmed live 2026-09-02: it never mentions this incident, Read, the Teams call or a voice clone, and it supports nothing in this file beyond the general fact that WPP publicly acknowledges brand-impersonation fraud.

Provenance. This case has no primary source in the strict sense, because the underlying document is an internal email that has never been published in full.

Cite this case

Social Engineering Examples. “WPP deepfake scam: a fake Mark Read, a cloned voice, and a target who said no (2024)”. Accessed 3 November 2026. https://socialengineeringexamples.com/wpp-deepfake-ceo-scam-attempt-2024

Attack Chain & Defense
1Reconnaissance and target selection
What happened

Fraudsters likely identified WPP CEO Mark Read as a high-value persona to impersonate, and selected an internal WPP "agency leader" as the actual fraud target, consistent with attackers using public sources such as press coverage, corporate leadership pages, and professional-networking profiles to map senior executives and reporting lines before making contact.

The control that would have stopped it

Senior-executive visibility (press coverage, corporate bios, professional-networking profiles) is very difficult to suppress at enterprise scale, so the realistic control is not hiding who the CEO or agency leaders are, but hardening the verification processes this information later gets weaponized against.

2Impersonation-asset collection
What happened

The attackers obtained a publicly available photograph of Read, per Guardian and Times of India reporting, to stand up a fake WhatsApp account in his name, and separately sourced existing public YouTube footage of a second, unnamed senior WPP executive to reuse as video material for the live call.

The control that would have stopped it

A single existing public photo or video clip cannot be reliably taken down or prevented from being reused, so the practical defense is the awareness message Read himself sent staff: a familiar photo or face on a call "doesn't mean it's really them," shifting the burden to skepticism at the point of contact rather than prevention of the asset's existence.

3Synthetic-media preparation
What happened

The email reported by The Guardian records that the attackers had an "AI voice clone" of the second executive ready for the call. No source names the tool, the service, or the audio it was trained on, so this file does not reconstruct them.

The control that would have stopped it

Commercial voice-cloning and video-synthesis tools are broadly available and cannot be blocked by a target organization, so defenses shift downstream to requiring identity verification that does not depend on how convincing a voice or video sounds or looks.

4Initial contact via spoofed profile
What happened

Using the fake WhatsApp account bearing Read's photo, the fraudsters made contact and arranged what appeared to be a legitimate Microsoft Teams meeting involving Read and the second senior executive.

The control that would have stopped it

Treating executive contact or meeting invitations that arrive through personal messaging apps like WhatsApp, rather than corporate channels or calendars, as an inherent red flag, and requiring confirmation through a known corporate channel before accepting the meeting.

5Live multi-persona execution
What happened

On the Teams call itself, the attackers deployed the cloned voice of the second executive together with existing YouTube footage of that same executive, while separately impersonating Read off-camera through the meeting's text-chat window, together manufacturing the appearance of an authentic two-executive meeting. The sources describe the video element as footage taken from YouTube, not as synthesized video.

The control that would have stopped it

Mandatory out-of-band verification, such as calling back a known corporate number or confirming through a separate, previously established channel, before treating instructions delivered on a video call as genuine, regardless of how authentic the voice or video appears.

6Social-engineering ask, and the point at which the chain broke
What happened

With the fabricated meeting's credibility established, the fraudsters pressed the actual target, a WPP agency leader, to help set up a "new business," which Read's email said was intended to lead to the extraction of personal details and money. The chain ended here. No payment instruction, account, invoice or sum was ever put to the target on the record, and WPP credited the vigilance of its people, including the executive concerned, with preventing the incident.

The control that would have stopped it

WPP credited the vigilance of its people, including the executive concerned, as the control that stopped the fraud, and said nothing further about what the target actually noticed. The broader lesson industry write-ups draw is mandatory, policy-level verification for any request to establish a new business relationship or move money that arrives through an unconventional or high-pressure channel, applied when the request is made rather than when money is about to move.

Quick Facts
Victim
WPP plc
(world's largest advertising and public relations holding company); the specific target was an unnamed senior WPP "agency leader"/"agency head," with CEO Mark Read and a second unnamed senior WPP executive impersonated as part of the pretext
Company
WPP plc
Location
United Kingdom
(WPP global headquarters, London); the attack itself was conducted remotely/virtually and the specific location of the targeted executive was not disclosed
Date
Disclosed internally and publicly reported 2024-05-10; exact date of the attack itself was not disclosed by WPP
Impact
No theft or payment loss was reported.
Basisnot-a-lossNo theft or payment loss reported; WPP described the attempt as prevented, but total incident costs were not measured
Mark Read's leadership email said "Fortunately the attackers were not successful" (quoted by The Guardian, 10 May 2024), and a WPP spokesperson said the incident "was prevented" thanks to the vigilance of the executive concerned. No sum or transfer request was reported; the reported ask was to set up a new business as a route to money and personal details. These statements do not independently measure every possible incident-response or other internal cost.
Status
Documented incident
Case Type
Real-World Incident
Sector
Media & Entertainment, Professional & Business Services
Threat Actor
unknown
Explore more

Related Cases

Browse by what this case has in common with others in the library.