Incidents

Keplr Wallet Warns Google and Apple Login Users After Unauthorized Transactions

Keplr has paused Google and Apple logins after reports of unauthorized transactions. The warning covers some wallets built on Web3Auth infrastructure.

Keplr Wallet Warns Google and Apple Login Users After Unauthorized Transactions

On November 7, Keplr reported unauthorized transactions affecting some wallets created using Google or Apple accounts. Keplr has paused both login methods. Web3Auth, which provides the underlying infrastructure, is investigating jointly with the wallet team. In a later update, Keplr said the issue involves the exposure of private keys for some of these wallets.

Who is affected

Keplr distinguishes between wallets created by signing in with Google or Apple and wallets set up with a recovery phrase or a hardware device. The company says the second group is not affected by this incident. However, not every account in the first group has been drained.

Web3Auth confirmed a security issue in its own infrastructure that affects some of the wallets Keplr uses. Both providers also described steps they took to secure assets at risk. Because of this, a lower balance alone does not tell a user whether funds were stolen or moved as a protective measure.

Bitquery published an independent analysis of the fund flows. Its findings confirm transfers out of multiple wallets. We are not citing a total loss figure: the providers have reported protective actions, so individual transfers should not be attributed to the attackers without caution.

What to do now

Choose the steps that fit how your wallet was created, and check them against the latest official updates:

  • Do not send new funds to a potentially compromised wallet created with Google or Apple.
  • Do not restore such a wallet in random services, and do not share its details with anyone offering help.
  • For any remaining liquid assets, follow Keplr’s current instructions for moving them to a wallet created with a recovery phrase or a hardware device.
  • Ignore private messages and links that promise to recover your funds.
  • Keep your transaction history and any correspondence you may need to investigate the incident.

Pausing logins does not invalidate a private key that has already been exposed. When you assess whether a wallet is safe, look at what the providers have said about keys and assets, not just whether the login form is available.

SecurHUB commentary

This incident shows why a security review of any service must also cover the vendors responsible for authentication and key storage. In incident response, it is essential to establish the scope of the breach and preserve evidence that separates attacker activity from remediation steps.

Sources: TSN, The Crypto Times, Bitquery

AuthorSecurHUB Team

Read more

Related articles

Want to know if this affects your company?

A free consultation with one of our experts — no obligation, in full confidence.

Let's talk