
Headline: Keplr suspends Google & Apple logins after Web3Auth breach — investigators trace ~$6M moving from tens of thousands of Cosmos wallets
Keplr Wallet has temporarily disabled Google and Apple social logins after a security incident tied to Web3Auth — the third-party authentication provider used by Keplr — exposed private keys for many social-login accounts. The company first flagged unauthorized transactions on November 7 and immediately began working with Web3Auth and blockchain investigators.
What happened
- Keplr says the issue originated in Web3Auth’s infrastructure, not Keplr’s own wallet code. “This was not a hack of Keplr’s code,” Keplr co-founder Josh Lee said. Keplr estimated roughly 20% of its Google/Apple login accounts could be affected, though only a fraction were exploited.
- Web3Auth acknowledged an infrastructure problem affecting certain embedded wallets used by Keplr and temporarily suspended that embedded wallet service while investigating. The provider said it found no evidence MetaMask users were impacted.
- Web3Auth has not publicly detailed the exact technical entry point that allowed private keys to be exposed, nor released a full list of other wallets that may have relied on the same service.
Blockchain tracing and the money trail
- Blockchain intelligence firm Bitquery traced approximately $6.01 million in transfers tied to activity on November 6–7.
- Their analysis found 44,041 wallets across seven Cosmos networks and 7,603 affected addresses on Injective. After removing duplicates that appeared on multiple networks, Bitquery estimated about 44,700 unique affected wallets.
- Cosmos Hub accounted for roughly $3.5 million of the traced transfers. Other networks with activity included Osmosis, Celestia, Akash, Noble, Babylon, dYdX and Injective.
- The investigators recorded transfers of about 1.96 million staked ATOM. Attackers (or actors moving assets) used staking-share tokenization to transfer staked positions without waiting the standard 21-day unbonding period.
- Bitquery observed that ~86% of affected wallets on the seven linked networks had outgoing transfers after Keplr’s initial warning, and transactions continued during the observation window on November 7.
But not all transfers are confirmed thefts
- On November 8 Web3Auth said some of the addresses flagged in blockchain traces were actually verified recovery wallets used by its teams to protect at-risk assets. That includes a Cosmos Hub address tied to roughly $3.5 million and an Osmosis address with about $1.04 million — both matching entries in Bitquery’s data.
- Web3Auth and Keplr have been performing whitehat recovery operations, moving vulnerable funds into secure recovery wallets. Because recovery transactions used the same technical pathway that attackers exploited, some protective transfers were misinterpreted as theft by on-chain observers.
- Web3Auth published a list of verified recovery addresses that it says are controlled by its recovery teams (covering Cosmos Hub, Osmosis, Celestia, Akash, Noble, Injective, dYdX, Babylon, Axelar, Saga, Agoric and several EVM chains). For eight EVM-compatible chains it identified 0x413e4F4De7E5FF010913488F781E679e76f706dA as a recovery address.
What’s being done
- Web3Auth temporarily paused its embedded wallet service, continues investigating, and is updating the list of verified recovery addresses as additional wallets are validated.
- Keplr is working with Web3Auth on account assessments and recovery steps. They say accounts created using recovery phrases or hardware wallets were not affected.
- Keplr has warned that social-login accounts might show depleted or reduced balances as a result of recovery actions; staked or locked assets require more complex recovery methods and will take longer.
Advice for users
- If you created your Keplr wallet via Google or Apple login: do not add funds to those accounts, and move any remaining liquid assets to a wallet controlled by a recovery phrase or a hardware device as soon as possible.
- Beware of impersonators offering recovery help; only trust verified recovery addresses and official guidance from Keplr and Web3Auth.
- Keplr said it will provide a way for users to check whether their accounts were affected; follow official channels for updates.
Open questions and context
- Web3Auth has not disclosed a full technical postmortem or an exhaustive list of other third-party wallets that might have used the same vulnerable infrastructure. It also has not said how much of the at-risk crypto was ultimately secured versus taken by bad actors.
- Keplr has not announced a reimbursement policy for confirmed losses.
- This incident echoes prior wallet-security failures: an Injective compromise in July involving a malicious developer package and an October Qubic vulnerability that exposed weak seed generation. The recurring theme: third-party components and onboarding conveniences can introduce systemic risks.
Bottom line
The incident highlights the trade-off between convenience (social logins) and custody security in Web3. If you rely on social-login wallets, treat them as higher risk: move significant funds into seed-phrase or hardware-backed wallets and follow official updates from Keplr and Web3Auth as investigations and recovery efforts continue.
Keplr Wallet has temporarily disabled Google and Apple social logins after a security incident tied to Web3Auth — the third-party authentication provider used by Keplr — exposed private keys for many social-login accounts. The company first flagged unauthorized transactions on November 7 and immediately began working with Web3Auth and blockchain investigators.
What happened
- Keplr says the issue originated in Web3Auth’s infrastructure, not Keplr’s own wallet code. “This was not a hack of Keplr’s code,” Keplr co-founder Josh Lee said. Keplr estimated roughly 20% of its Google/Apple login accounts could be affected, though only a fraction were exploited.
- Web3Auth acknowledged an infrastructure problem affecting certain embedded wallets used by Keplr and temporarily suspended that embedded wallet service while investigating. The provider said it found no evidence MetaMask users were impacted.
- Web3Auth has not publicly detailed the exact technical entry point that allowed private keys to be exposed, nor released a full list of other wallets that may have relied on the same service.
Blockchain tracing and the money trail
- Blockchain intelligence firm Bitquery traced approximately $6.01 million in transfers tied to activity on November 6–7.
- Their analysis found 44,041 wallets across seven Cosmos networks and 7,603 affected addresses on Injective. After removing duplicates that appeared on multiple networks, Bitquery estimated about 44,700 unique affected wallets.
- Cosmos Hub accounted for roughly $3.5 million of the traced transfers. Other networks with activity included Osmosis, Celestia, Akash, Noble, Babylon, dYdX and Injective.
- The investigators recorded transfers of about 1.96 million staked ATOM. Attackers (or actors moving assets) used staking-share tokenization to transfer staked positions without waiting the standard 21-day unbonding period.
- Bitquery observed that ~86% of affected wallets on the seven linked networks had outgoing transfers after Keplr’s initial warning, and transactions continued during the observation window on November 7.
But not all transfers are confirmed thefts
- On November 8 Web3Auth said some of the addresses flagged in blockchain traces were actually verified recovery wallets used by its teams to protect at-risk assets. That includes a Cosmos Hub address tied to roughly $3.5 million and an Osmosis address with about $1.04 million — both matching entries in Bitquery’s data.
- Web3Auth and Keplr have been performing whitehat recovery operations, moving vulnerable funds into secure recovery wallets. Because recovery transactions used the same technical pathway that attackers exploited, some protective transfers were misinterpreted as theft by on-chain observers.
- Web3Auth published a list of verified recovery addresses that it says are controlled by its recovery teams (covering Cosmos Hub, Osmosis, Celestia, Akash, Noble, Injective, dYdX, Babylon, Axelar, Saga, Agoric and several EVM chains). For eight EVM-compatible chains it identified 0x413e4F4De7E5FF010913488F781E679e76f706dA as a recovery address.
What’s being done
- Web3Auth temporarily paused its embedded wallet service, continues investigating, and is updating the list of verified recovery addresses as additional wallets are validated.
- Keplr is working with Web3Auth on account assessments and recovery steps. They say accounts created using recovery phrases or hardware wallets were not affected.
- Keplr has warned that social-login accounts might show depleted or reduced balances as a result of recovery actions; staked or locked assets require more complex recovery methods and will take longer.
Advice for users
- If you created your Keplr wallet via Google or Apple login: do not add funds to those accounts, and move any remaining liquid assets to a wallet controlled by a recovery phrase or a hardware device as soon as possible.
- Beware of impersonators offering recovery help; only trust verified recovery addresses and official guidance from Keplr and Web3Auth.
- Keplr said it will provide a way for users to check whether their accounts were affected; follow official channels for updates.
Open questions and context
- Web3Auth has not disclosed a full technical postmortem or an exhaustive list of other third-party wallets that might have used the same vulnerable infrastructure. It also has not said how much of the at-risk crypto was ultimately secured versus taken by bad actors.
- Keplr has not announced a reimbursement policy for confirmed losses.
- This incident echoes prior wallet-security failures: an Injective compromise in July involving a malicious developer package and an October Qubic vulnerability that exposed weak seed generation. The recurring theme: third-party components and onboarding conveniences can introduce systemic risks.
Bottom line
The incident highlights the trade-off between convenience (social logins) and custody security in Web3. If you rely on social-login wallets, treat them as higher risk: move significant funds into seed-phrase or hardware-backed wallets and follow official updates from Keplr and Web3Auth as investigations and recovery efforts continue.




