hack or exploit

Web3Auth Exploit Doesn't Affect Trust Wallet: Products That Might be Affected

59Importance
updatingStatus
4News media
5Pieces
Published
Updated
Since then
4 new reports
Also mentions
TWTATOM

A Web3Auth-linked wallet incident centered on Keplr users who signed in with Google or Apple accounts, with one data provider tying more than $6 million to the drain and Web3Auth disputing that estimate. Keplr later said some flagged addresses were Web3Auth recovery wallets, while Trust Wallet said it was not affected and other Web3Auth-based products were still listed as potentially exposed.

Key claims & sources

✓
Trust Wallet said it was not affected by the Web3Auth exploit, while products that rely on Web3Auth were listed as potentially affected.
✓
Bitquery traced the theft estimate to Keplr wallets created with Google and Apple logins.
✓
Keplr confirmed Web3Auth recovery addresses after the wallet breach.
✓
Web3Auth said the addresses flagged as attacker wallets were its recovery wallets.

What it means

Web3Auth is the infrastructure many wallets use to let people skip seed phrases and sign in with a Google or Apple account instead, splitting the resulting key through MPC so no single party is supposed to hold it. Keplr, a leading Cosmos wallet, built its social-login option on this service. The same convenience model underpins rivals like Particle Network and Magic, which is why a single vendor's incident can ripple across wallets that otherwise look unrelated, draining funds across eight Cosmos networks by initial counts.

Keplr users who created wallets via Google or Apple now need to check whether their addresses were ever flagged, since Web3Auth says some of the 'attacker' wallets Bitquery identified are actually its own recovery addresses holding user funds, not stolen ones. Trust Wallet customers can stand down entirely, as the company confirmed no exposure. Anyone using a lesser-known wallet built on Web3Auth, however, still has to wait for that product's own confirmation before assuming safety.

Social login was sold as the fix for crypto's onboarding problem, letting new users skip seed phrases entirely. This episode shows the cost: when Web3Auth holds recovery wallets on users' behalf, it is also the party that decides, after the fact, whether a flagged address is a thief or itself. That is a custodial relationship dressed as a convenience feature, and the gap between Bitquery's $6.01 million theft estimate and Web3Auth's rebuttal shows how little outside observers can verify on their own.

Keplr's confirmation that a six-account Cosmos Hub batch tokenizing 2,265.59 staked ATOM led back to Web3Auth recovery addresses is the first concrete reconciliation point, and more such matches would shrink the real loss figure well below initial estimates. Watch whether Web3Auth publishes a full account-by-account breakdown of the flagged wallets, since that document, not further dueling press statements, will settle how much of the $6 million was ever actually stolen.

Market reaction i

Trust WalletTWT the event is about this asset
first headline
-0.8% 2 h before
+1.8% 4 h after
$0.3937price at publication
12data points

Coverage timeline

Every piece in order, with the time its news medium declares — if it is not believable we use ours and say so — and what it added to what was already known at that point. Arriving first is not the same as adding something.

first
Nov 8 09:14
+2 h 19 m
Nov 8 11:32
+3 h 53 m
Nov 8 13:07
The Defiant context
Its angle: destination, tokenized, includes
+4 h
Nov 8 13:13
Crypto Briefing echo
No new facts: vulnerability, accurately, challenges; with quotes
+4 h 20 m
Nov 8 13:34
BeInCrypto context
Its angle: infrastructure, safekeeping, maintenance; with quotes

Thefts of a similar size

WhenWhat happenedFigure
2.6 years ago Remilia · Private key compromised incident $6M
3.1 years ago Coins.ph · Private key leakage incident $6M
3.8 years ago LendHub · Incorrect Share Accounting incident $6M
3.8 years ago LendHub · Contract vulnerability incident $6M
4.0 years ago FTX & 3Commas · Phishing attack incident $6M

4285 incidents stored · 459 were as large as this one or larger ($6M)