CybersecurityNovember 9, 20264 min read

Web3Auth breach let attackers drain some Keplr wallets

If I signed into a crypto wallet with Google or Apple, could someone else get in? In some Keplr cases, the answer was yes after a flaw at Web3Auth was exploited, and the provider then drained other exposed wallets first to stop more theft.

If I signed into a crypto wallet with Google or Apple, could someone else get in?

For some Keplr users, that answer turned into a hard yes.

The reported setup is pretty specific. Some people created a Keplr wallet using Google or Apple sign-in. Keplr relies on Web3Auth to handle that login flow. Late last week, both companies said an attacker exploited a security flaw at Web3Auth and used it to reach those wallets and steal funds.

Then Web3Auth did something you do not see every day: it used the same route the attacker had used to empty other wallets that were still at risk, before the attacker could get to them.

That sounds wild, because it is.

The weak point was not Keplr's password box

A lot of people hear "wallet compromised" and assume the owner got phished, reused a password, or installed something bad. That still happens all the time. But this case appears different.

The issue, based on the known details, was in the company sitting behind the social login layer.

Think of it like this: your apartment door is solid, but the building's master key cabinet has a flaw in its lock. If someone gets into that cabinet, they may not need to break your door at all. In this setup, Google or Apple sign-in was the front-end experience, but Web3Auth was part of the machinery that made access to the wallet work.

That is the real lesson here. Security is not just the app you can see. It is also the chain of services behind it.

For non-specialists, "sign in with Google" often feels safer because you are not creating another password. And in many cases it does reduce some common risks. But it also means you are trusting the extra provider that turns that login into wallet access.

Different trust model, different failure mode.

Why draining wallets "for safety" happened

At first glance, a provider emptying customer wallets sounds like the attack itself.

But the idea is straightforward. If the attacker had a working path into exposed wallets, and that path could not be cut off fast enough, the fastest way to stop more theft may have been to move the funds out first to a controlled location.

It is similar to moving cash out of an open register when you realize someone has copied the key to the shop.

That does not make it comfortable. It does show how serious the access problem likely was. If a company decides the least bad option is to use the same access path before the criminal does, you are looking at a response built around speed, not elegance.

It also highlights something many people miss about crypto systems: if a wallet path is exposed, transfers can be immediate and hard to reverse. There is no card issuer to call for a chargeback.

The bigger issue with convenience logins for high-value accounts

Social sign-in is convenient. For low-risk services, that tradeoff can be perfectly reasonable.

For something that can hold money, the bar is higher.

I am not saying Google or Apple sign-in is inherently unsafe. The problem is that every extra layer adds another place where design mistakes, implementation flaws, or operational failures can hit you.

With a traditional website account, a login provider breach might expose profile data or let someone read messages. With a crypto wallet, the same class of failure can directly turn into stolen assets.

That difference matters.

And this case is a good reminder that "non-custodial" or self-directed tools can still depend heavily on third parties for key management, authentication, or recovery flows. If one of those pieces breaks, the user still bears the consequences.

What Keplr users should do now

If you use Keplr and set it up with Google or Apple, treat this as something to check right away.

  • Review your wallet activity for transfers you do not recognize.
  • Check whether your wallet was one of the at-risk cases and whether funds were moved as a protective step.
  • Follow the wallet provider's account recovery or migration guidance if they have issued any.
  • If you still have assets in a wallet tied to the affected login flow, consider moving them to a newly created wallet with a safer setup.
  • For higher-value holdings, prefer a hardware wallet or another setup where the signing keys are more isolated.
  • Tighten the security of the Google or Apple account connected to financial tools: strong unique password, phishing-resistant MFA where available, and review of active sessions and recovery options.

More broadly, make a habit of asking one simple question before you trust a financial app: who else is in the path between me and my money?

That question saves a lot of false comfort.

The clear read from this incident is that convenience features can quietly expand the blast radius. If your wallet depends on a third party to make access work, that third party is part of your threat model whether you think about it or not.