Jon Tetreault

Writing · November 2026

The rescue used the same door.

Keplr wallets created with Google or Apple login were emptied through a flaw at the login provider. The unusual part is that the people protecting the funds used the attacker's route to do it, which is why nobody can yet say what was stolen.

Keplr, a wallet for the Cosmos ecosystem, suspended Google and Apple sign-in on November 7 after reports of unauthorized transactions. The cause sits with Web3Auth, the company that runs those logins. The Hacker News covered it on November 9. I'm sticking to what I could read and marking where the record is thin.

What the sources agree on

Keplr uses Web3Auth for its social logins. Keplr co-founder Josh Lee said, in the words crypto.news quotes: "This was not a hack of Keplr's code. The incident originated at Web3Auth, a provider Keplr uses." Web3Auth acknowledged an infrastructure problem affecting certain embedded wallets and paused its embedded wallet service.

Wallets secured with a recovery phrase or a hardware wallet are not affected, according to Keplr. Lee estimated early that about 20% of Google and Apple login accounts could be affected, and that only a fraction appeared exploited. Web3Auth says its initial investigation found "no evidence that MetaMask users are impacted." Consensys, which makes MetaMask, acquired Web3Auth in June 2025, per The Hacker News.

The number you can't use

Bitquery counted at least $6.01 million moved from roughly 44,700 wallets, per Bitcoin.com News. That is a count of transfers, not losses. The Hacker News reports that Bitquery first called the movements theft, then issued a corrected analysis treating them as a rescue.

Here is why. Web3Auth says its recovery teams used the same route as the exploit to move at-risk funds into recovery wallets before the attacker could reach them. It has published a list of verified recovery addresses, and some of the large destination wallets Bitquery had flagged turned out to be on it. A wallet that shows zero may have been robbed, or it may have been rescued.

The outlets don't line up on money. GoPlus said at least about $1 million was stolen, without showing how it got there, per The Hacker News. Bitquery's $6.01 million includes protective moves. Keplr and Web3Auth have published no dollar figure, no reimbursement plan and no timetable for returning the secured funds. I won't pick a number for them.

What nobody has said

How the flaw worked. Neither company has explained the technical cause, when it was first used, or whether the route is now closed. The Hacker News notes Web3Auth says the issue touches services used by some other companies, and Keplr is the only one named so far.

The timing is also strange. According to The Hacker News, the first protective transfer happened 21 minutes before Web3Auth's first public notice, and about 86% of the wallets were emptied after Keplr warned users. crypto.news reports Web3Auth said some protective transactions were mistaken for attacker activity. That is the cost of fixing a breach through the broken door: the evidence looks identical.

The part that isn't news

"Sign in with Google" feels like an account. A wallet is not an account. Whoever can reconstruct the key controls the funds, and with a social login, some part of that key's creation and storage lives on a provider's infrastructure. I've written about this shape before, with servers and with plugins. Someone else's system sat between you and your key, and you didn't choose its security.

I lost 9 BTC to security mistakes. What I took from it is that convenience is just trust you haven't priced yet. Social login is a fair trade for a small balance and a new user. It is a poor trade for a balance you can't afford to lose.

What I'd do

1. Find out how each wallet you use was created. If you signed in with Google, Apple or any social login, you did not generate your own recovery phrase. Write that list down.

2. If you're a Keplr social-login user, follow Keplr's guidance. Don't send new funds to the account. Don't re-import or recreate it. Move liquid funds to an account secured by a recovery phrase or a hardware wallet. Staked and locked assets are taking longer to secure.

3. Treat "recovery" messages as hostile. Both companies warned about unsolicited offers of help. Check only the official Keplr and Web3Auth accounts, and compare any address against the published recovery list before assuming it belongs to a thief.

4. Move real money to keys you hold. A hardware wallet with a recovery phrase written on paper and stored offline removes the provider from the chain of custody. Keplr says those wallets were not affected here.

5. Don't re-import a possibly exposed key anywhere. A key that may have leaked doesn't become safe in a new app. Move the funds, not the key.

The boring conclusion

The question for any wallet is who else can reconstruct the key, and whether you'd know if they did. This one is still developing. If a root cause or a confirmed loss figure is published, I'll update it.

Verify everything, especially the login that says it's your wallet.

— Jon Tetreault, November 2026. The habits, tools, and checks behind this piece are what I teach in Crypto Security Mastery.