A structured, citable database of verified AI voice cloning and impersonation scam incidents. Every record is backed by published news reporting and links to our full analysis and the original source.
Last updated November 9, 2026
The loss total sums only incidents where the source disclosed a specific US-dollar amount. 14 incidents have a disclosed amount in another or unconfirmed currency, shown per record but never converted or summed. For 12 incidents the source reporting did not quantify or disclose the loss, so the total understates real losses. 2 incidents involved no monetary loss.
Beyond verified incidents
These patterns are supported by published reporting, including articles that may not qualify as verified incident records. They are not included in the incident totals above.
A caller claims to be a grandchild in an emergency and pressures a grandparent to send money before checking with family. A cloned voice is possible but must be established by the reporting.
A caller falsely claims a loved one has been kidnapped and demands an immediate ransom while discouraging verification.
A scammer poses as a relative to make a request for money or sensitive information sound like it came from someone the recipient knows.
Someone poses as a company leader or trusted business contact to push an urgent payment, account change or disclosure past normal approval checks.
A scammer poses as a real estate or closing contact to redirect funds during a time-sensitive transaction.
A scammer poses as an FBI, IC3 or other recovery agent to re-scam someone who has already reported a fraud, often asking for money or personal information. Reported use of AI does not by itself prove a named agent's voice was cloned.
WIS10 reports spoofed FBI numbers and AI used to sound believable; it does not establish cloning a specific agent's voice.
A scammer poses as law enforcement or a court officer, claims a missed jury summons or warrant, and demands payment or information to avoid arrest.
Agents can read these patterns and verified incidents through our MCP setup guide. The remote MCP connection address is https://trustonion.io/mcp (use an MCP client, not a JSON feed).
Beyond the database
Read the evidence behind individual incidents, then take the next useful step at home.
Case study · Updated November 9, 2026
An Ontario woman from Smiths Falls lost $12,000 after scammers used AI voice cloning to impersonate her brother in a fake car accident emergency call.
Read the case
Case study · Updated November 9, 2026
Georgia farmers are losing thousands to AI-generated fake dealership websites and phone scams. A Bulloch County case highlights the growing threat to rural buyers.
Read the casePractical reporting ·
Three defendants allegedly cloned CEO voices with AI to trick finance teams into wiring $129M. Here's how the scheme worked and what stops it.
Practical reporting ·
Coral Springs became Florida's first city to ban Bitcoin ATMs after local victims lost nearly $350,000. More than half were over 60. Here's how the scam worked.
Practical reporting ·
A DoorDash customer used an AI-generated burnt pizza photo to claim a fraudulent refund. Here's what it means for businesses verifying digital claims.
Voice Clone Scam Pulse is free to cite and reuse with attribution (CC BY 4.0). Suggested citation:
Trust Onion, "Voice Clone Scam Pulse: AI Scam Incident Database," trustonion.io/voice-clone-scam-pulse (updated 2026-11-09).
Journalists: every record links to the original news source — please verify and credit primary reporting as well. See our methodology, inclusion rules, and corrections policy, or contact us to report an error.
Using something from this page? Please credit Trust Onion and link back.
Voice Clone Scam Pulse — AI Scam Incident Database — Trust Onion. https://trustonion.io/voice-clone-scam-pulse
