# HD-INC-148: A mother got a ransom call with a voice that sounded exactly like her daughter, and her daughter was safe the whole time

> In 2023 an Arizona mother took a call in which she heard what sounded like her teenage daughter crying, then a man demanding a ransom. Her daughter was safe the whole time and no money was paid. She said she was sure the voice was her daughter's and told the US Senate she believed AI voice cloning had been used, though the caller was not identified and the audio was not confirmed as AI-generated. Experts say a convincing voice clone can now be built from a short sample of someone speaking.

- Source: https://useheadlights.com/library/HD-INC-148/
- Publisher: Headlights (useheadlights.com), author Ellie Harris
- Published: 2026-08-11
- Company: No single company; consumer voice-cloning tools
- Sector: Consumer AI
- Country: United States
- Year: 2023
- Behaviour in the record (Headlights reading): Not established
- Governance domains: Consumer protection, Civil liberties
- Licence: CC BY-NC 4.0. Cite as: Harris, E. (2026). A mother got a ransom call with a voice that sounded exactly like her daughter, and her daughter was safe the whole time. Headlights AI Incident Library, HD-INC-148. https://useheadlights.com/library/HD-INC-148/

## What happened

It was reported that in 2023 a mother in Arizona answered a phone call and heard what sounded like her 15-year-old daughter crying and distressed. Reporting indicates a man then came on the line and said he had her daughter, and demanded a ransom that began at one million dollars and was then lowered. She said she was convinced the voice was her daughter's. Her daughter was actually safe the whole time, away on a trip, and was reached soon afterwards, and no money was paid.

She later told the US Senate Judiciary Committee in June 2023 that she believed AI voice cloning had been used to imitate her daughter, and she urged lawmakers to act. Experts quoted in reporting said a convincing clone of someone's voice can now be made from a short sample of them speaking, making this kind of call possible.

But there is an important distinction in this case. The caller was not identified and the recording was not publicly confirmed to be AI-generated. Based on the evidence made public, AI voice cloning was the mother's belief and a warning from experts, not an established finding about this particular call.

## What an auditable version would have shown

If a service can clone someone's voice, there should be a record of whose voice is being copied and why the service has permission to copy it. Without consent, the clone should not be created, and synthetic audio should be marked so that later there is some way to check whether a machine produced it.

There is another side to this incident too. When someone receives a frightening demand involving a loved one, there needs to be a way to slow the decision down and verify the claim through another channel before money is sent. Those two records, on the tool's side and the receiver's side, could make a cloned voice easier to trace and a panicked decision harder to exploit.

## Where the gap was

Voice is something we instinctively recognise, and hearing someone you love crying can make the situation feel real before you have had time to question it. At the same time, copying a person's voice has become cheap and easy, and a short clip from social media can be enough to build a clone. There may be no obvious sign for the person listening that what they are hearing is synthetic, and no evidence available to them in that moment showing whether the person whose voice was copied ever consented. For a parent hearing what sounds like their child in distress, that is a powerful gap.

## What governance should have looked like

A tool capable of reproducing a real person's voice should require proof of consent and should mark synthetic audio so it can be identified later. A ConstraintGate is designed to stop a service from cloning a specific real person's voice without evidence that they agreed. A VerificationGate deals with the other side of the problem: before someone takes a high-stakes action because of a frightening call, the claim should be checked through another channel, such as a call back or an agreed family word. One makes impersonation harder to create, and the other gives the person receiving it a reason to stop before acting.

The reference implementation of ConstraintGate and VerificationGate is open source. It lives at [github.com/saffronandindia/headlights-oss](https://github.com/saffronandindia/headlights-oss), Apache 2.0 licensed, free for any company to install. The repository is public now.

## Sources

- [AI scam calls: this mom believes fake kidnappers cloned her daughter's voice (CNN)](https://www.cnn.com/2023/04/29/us/ai-scam-calls-kidnapping-cec/index.html)
- [Written statement of the parent, US Senate Judiciary Committee (13 June 2023)](https://www.judiciary.senate.gov/imo/media/doc/2023-06-13%20PM%20-%20Testimony%20-%20DeStefano.pdf)
- [Mom recounts the deepfake kidnapping scam in Senate testimony (Gizmodo)](https://gizmodo.com/ai-deepfake-kidnapping-scam-congress-hearing-1850536490)

## Related

- [HD-INC-069](/library/HD-INC-069)
- [HD-INC-047](/library/HD-INC-047)
- [HD-INC-039](/library/HD-INC-039)