Emerging evidence
Published recordCrimeThe Trace
More
Coinbase AI Blocked $4.7M In Deepfake Musk Scam
- Truvace record
- TRV-2026-3050raw data (JSON)
- Version
- v1Published
- First published
- Evidence type
- News report
- Sources
- 1 sourceJournalism
- sha256
- 14799cd5652d…check it
Coinbase said its AI scam-prevention agent stopped about $4.7 million, or 91% of attempted sends, from reaching a deepfake Elon Musk crypto giveaway scam. Coinbase (COIN) said its AI scam-prevention agent stopped about $4.7 million in customer funds from reaching scammers who used a deepfake of Elon Musk to pitch a fake Tesla crypto giveaway, blocking roughly 91% of the money customers tried to send. T
49Gain side
How the two sides scoreClose call
50Problem side
The gain
Coinbase said its AI scam-prevention agent blocked about $4.7 million, roughly 91% of the money customers tried to send, to a deepfake Elon Musk crypto giveaway scam, with no humans in the loop.
The problem
Coinbase's figures imply about $460,000 still left customers' accounts during the deepfake Musk giveaway scam, even with its AI agent running, and the company did not say how much reached the scammers.
A fixed formula sets both scores from the evidence and its sources. Reader votes don’t move them.
What the scores mean
G is the gain side, out of 100. It goes up when the gain is specific, when it measurably helped people and when the sources behind it are strong.
P is the problem side, out of 100. It goes up when the problem is specific, when it measurably hurt people and when the sources behind it are strong.
What this doesn’t fix
The $4.7 million and 91% figures come from Coinbase's own blog post, and the company did not say how much reached the scammers, when the fake stream ran or which coins customers tried to send.
Sources
1 on file- Bitcoin Magazinebitcoinmagazine.com
Cite this record
v1Truvace Impact Record TRV-2026-3050, v1: “Coinbase AI Blocked $4.7M In Deepfake Musk Scam.” Truvace, 2026-11-19. /record/TRV-2026-3050 (accessed on the day you copy it). sha256 14799cd5652d28f1…
Change history
1 versionEvery change made to this record since it was first published, and why. Nothing has changed since it went up.
Certified into the record
Check this record hasn’t been altered
How to check it yourself, without trusting this page
Download any version from /api/record/TRV-2026-3050 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.
ace