Case Library / Phishing / LastPass employee ignores an AI clone of the CEO's voice on WhatsApp (2024)

LastPass employee ignores an AI clone of the CEO's voice on WhatsApp (2024)

An attacker sent a LastPass employee WhatsApp calls and a voicemail using an AI copy of the CEO's voice. The employee reported it. What gave it away.

Share:

Social Engineering Examples·6 sources

In April 2024 a LastPass employee got a string of WhatsApp messages from someone claiming to be the company's chief executive. Missed calls. Texts. A voicemail. The voicemail used AI-generated audio made to sound like the CEO, and the gist, as the CEO later recalled it, was "I need help urgently". The employee didn't reply. WhatsApp isn't a channel LastPass uses for business, the contact came outside working hours, and the whole thing had the pushy feel of a scam. So the employee ignored it and told the security team. LastPass said the attempt had no impact, then wrote it up on its own blog on 10 April 2024 as a warning to everyone else. Status: it failed, LastPass says nothing was affected, and nobody knows who was behind it.

Key takeaways

  • Nothing technical caught this. One employee noticed the wrong channel and the fake urgency.
  • The cloned voice was most likely built from the CEO's public podcast and video appearances.
  • LastPass never said what the attacker actually wanted. The chain broke before any request was made.
  • A security company that had been badly breached in 2022 chose to publish a near miss. That's rare and useful.

How it worked

Step What happened
Pick a face The attacker chose LastPass's CEO to impersonate. Press reports say the voice clone was likely made from public recordings
Pick a channel WhatsApp, with an account presenting as the CEO. Not a LastPass business channel
Pile on Call after call, then texts, then a voicemail. The voicemail carried the fake voice and the urgent tone
The ask Never reached. LastPass didn't describe a specific request, and none was acted on
The end The employee disengaged and reported it. Security mitigated and shared the details with industry partners

LastPass is a password manager owned by GoTo. The employee was described in press coverage as a sales executive. Neither the employee nor the attacker has been named.

Tip: a familiar voice is no longer proof of identity. If your "CEO" needs something urgently over a personal messaging app, that's the moment to call them back on a number you already have.

The tells

  • Wrong channel. The company doesn't do business over WhatsApp.
  • Wrong time. Contact outside normal hours.
  • Forced urgency. "I need help urgently" and a run of missed calls and texts.
  • Pressure to skip process. An executive asking a sales employee for an unspecified favour, fast.

None of these tells is about the audio. The employee didn't need to detect a deepfake. The context gave it away.

Why it matters

Voice cloning used to be a headline tactic: the 2019 UK energy firm case, then the Arup video-call fraud a few months before this one. LastPass's point in publishing was different. The tools are now cheap enough that ordinary fraudsters use them for ordinary executive-impersonation attempts. This wasn't a nation state. It was a scam that happened to have a synthetic voice attached.

It's also a clean example of the attack dying at the human layer. Compare it with the WPP attempt the following month, which failed the same way: a person found the request odd and declined before any money was discussed.

What stops it

  • Verify out of band. Confirm any urgent executive request through an approved internal channel, never the one it arrived on.
  • Channel discipline. If it comes in on personal WhatsApp or by text, assume it's dodgy until proven otherwise.
  • Teach the hallmarks. Someone's in a hurry, it's late, and they want you to skip the usual steps. Classic.
  • No-blame reporting. This only became a lesson because the employee spoke up. Make that easy.
  • Put voice cloning in the training. Sounding like the boss isn't the same as being the boss.
  • Code words or verification protocols for high-stakes executive requests.

See also voice cloning, deepfake examples and CEO fraud.

Common questions

What was the LastPass deepfake incident?

An April 2024 attempt to pressure a LastPass employee through WhatsApp, using calls, texts and a voicemail with an AI copy of the CEO's voice. The employee ignored it and reported it. Nothing was lost.

Did LastPass lose anything?

No. The company said the attempt had no impact and no request was acted on.

How was the CEO's voice cloned?

LastPass didn't say. Press reports noted it was likely generated from the CEO's publicly available podcast and video appearances.

Why did LastPass publish a failed attack?

To warn that deepfake voice tools are now cheap and common enough for everyday executive-impersonation fraud, not just sophisticated actors.

Sources
  • Attempted Audio Deepfake Call Targets LastPass Employee. LastPass (official blog, by Mike Kosak, Sr. Principal Intelligence Analyst) (primary). First-party incident disclosure published April 10, 2024. Confirms WhatsApp channel, calls/texts/voicemail, CEO impersonation via audio deepfake, forced urgency, employee reporting, and LastPass's statement that the incident had no impact. Verified by direct fetch.
  • LastPass: Hackers targeted employee in failed deepfake CEO call. BleepingComputer (secondary). Corroborates the CEO as the impersonated executive, quotes Kosak directly, and notes the clone was likely trained on publicly available audio of the CEO (citing a specific YouTube video) and that WhatsApp being an uncommon business channel helped the employee spot it. Also notes LastPass's 2022 breaches. Verified by direct fetch.
  • LastPass Employee Targeted With Deepfake Calls. SecurityWeek (secondary). Corroborates the incident occurred on a Wednesday in the week of April 10, 2024 (confirmed as the correct weekday for that date), that LastPass is owned by GoTo, and that the attempt failed due to the employee's suspicion of forced urgency and off-hours contact. Verified by direct fetch.
  • Scammers Target LastPass Employee With CEO Audio Deepfake. PCMag (secondary). Corroborates the fraudster created a WhatsApp account posing as the CEO, obtained the employee's contact details, and sent missed calls plus at least one AI voice message. Verified by direct fetch.
  • What CIOs Can Learn from an Attempted Deepfake Call. InformationWeek (secondary). Reports the targeted employee was a sales executive and emphasizes that a simple report to internal security stopped the attack early; includes commentary from LastPass's Mike Kosak on the company's awareness culture. Verified by direct fetch.
  • How LastPass preps for the next audio deepfaker. IT Brew, by Billy Hurley (secondary). In a May 30, 2025 interview, the CEO spoke on the record about the April 2024 incident and described the urgent voice note; the article also identifies the target as someone on the sales team. Retrieved through Exa on October 7, 2026.
Cite this case

Social Engineering Examples. “LastPass employee ignores an AI clone of the CEO's voice on WhatsApp (2024)”. Accessed 3 November 2026. https://socialengineeringexamples.com/lastpass-deepfake-voice-ceo-2024

Attack Chain & Defense
1Target Selection
What happened

the attacker selected LastPass's CEO as the impersonation target and contacted a LastPass employee via WhatsApp.

The control that would have stopped it

employee-facing OSINT exposure (executive names, roles, public appearances) is very hard to eliminate at enterprise scale for anyone publicly identified as a company's CEO; the realistic control assumes attackers already have this and hardens the process it later gets used against, rather than trying to hide it.

2Voice Impersonation Setup
What happened

the attacker used an audio deepfake to impersonate the CEO through WhatsApp.

The control that would have stopped it

an organization has little ability to stop a third party from creating deepfake audio or using an impersonating messaging account; the practical control is to treat a familiar-sounding voice as insufficient proof of identity on its own.

3Initial Multi-Touch Contact
What happened

the attacker reached the employee through WhatsApp, a channel outside LastPass's sanctioned business communications, opening with a series of missed calls and text messages from the account posing as the CEO.

The control that would have stopped it

channel discipline. Requests arriving over personal messaging apps like WhatsApp rather than approved internal business channels should be treated as inherently suspect, regardless of who they claim to be from.

4Pretext Delivery With Pressure
What happened

the attacker followed up with at least one voicemail carrying the AI-generated deepfake audio of the CEO's voice, applying forced urgency to push the employee toward an immediate, unverified response.

The control that would have stopped it

security awareness training that specifically covers AI voice cloning and classic social engineering hallmarks (forced urgency, off-hours contact, pressure to bypass normal process), paired with a no-blame reporting culture that makes it easy and expected for employees to escalate suspicious contacts rather than act on them.

5Intended Payout (blocked before execution)
What happened

the likely end goal was an executive-impersonation fraud outcome, such as a fraudulent transfer or a credential/access request, but LastPass's disclosure does not describe a specific ask ever being made or acted on. The employee recognized the unusual channel, off-hours timing, and urgency as social engineering hallmarks, disengaged without complying, and reported it to internal security, so the chain never reached completion.

The control that would have stopped it

mandatory out-of-band verification, contacting the purported executive or a known security channel through an already-established method, never the channel the request arrived on, before acting on any urgent or unusual request; executive-impersonation playbooks and pre-agreed verification protocols for high-stakes asks. This is the control that actually stopped the attempt: the employee's disengagement and report to internal security closed the chain before any payout could occur.

Quick Facts
Victim
LastPass (password management company, owned by GoTo); the direct target was a LastPass employee, reported by press as a sales executive.
The impersonated executive was the CEO.
Company
LastPass
Location
Remote via WhatsApp
Date
2024-04
Impact
LastPass reported no impact; financial loss was not separately quantified
Basisnot-a-lossCompany-reported no-impact outcome
Status
Documented incident
Case Type
Real-World Incident
Sector
Technology & Software
Threat Actor
unknown
Explore more

Related Cases

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