Wallet vacuum 11/2026

Are there any official reports, procedures, or verification regarding a compromise of Keplr?
I really wouldn’t want my ATOMs drained. That would truly hurt…
Is there any emergency procedure I should follow?
I have liquid staking disabled. I use Atomic Wallet, and I use Keplr in both Firefox and Chrome.
According to AI, it’s fine.
Is it possible to convert an existing wallet into a multisig wallet?
And require, for example, 2 out of 3 signatures for transactions?
Thanks.

Just use a ledger or keystone hardware wallet to store your atom tokens. Use dice rolls if you don’t trust their entropy. Slap a passphrase on it too while you’re at it and you’re golden.

Nothing is safe at the moment, stay on high alert & never allow any AI access to your private keys via software evaluation. Agentic hacking is at a all time high.

Reposting from Cosmos Hub’s X - Follow updates on Keplr’s and Web3Auth’s official channels.

Cosmos Hub ⚛️ (@cosmoshub) on X

Web3Auth (@Web3Auth) on X

From what Keplr has shared so far, the issue is with accounts created through Google or Apple login (the Web3Auth option). Keplr says accounts set up with a recovery phrase or a hardware wallet are not affected.

So the first thing to check is how you created your Keplr account. If it was with Google or Apple, Keplr’s advice is to stop depositing to it and move any liquid assets to a wallet secured by a recovery phrase or hardware wallet. Staked ATOM takes longer, since unstaking has a waiting period.

On multisig: you can’t convert an existing address into a multisig. A multisig is a new, separate address, so you’d create it and then move your funds there.

And please be careful with anyone who DMs you offering to “recover” funds. Only follow Keplr’s and Web3Auth’s official channels.

Web3Auth has published its verified recovery addresses now (Web3Auth on X: "Update on Keplr asset recovery: As part of our ongoing response to the security incident affecting certain Keplr wallets, we have been transferring assets into secure recovery wallets, with assistance from Keplr. 🧵" / X), and the Cosmos Hub one, cosmos1atuap9kfnt6y8ykvn3437e7j3z8qffh3qtnmwu, is the address the 7 Nov “lsm recovery batch” transaction sent the tokenized stake to. So if your staked ATOM left that day with that memo, it went to their recovery wallet. Follow their instructions in that thread, not anyone who DMs you.

That transaction is also why keeping liquid staking disabled matters, as you have. It tokenized delegations from six accounts with MsgTokenizeShares and moved the shares in a single block, with no unbonding. With tokenizing disabled, someone holding your key can only start a 21 day unbond or the 21 day wait to turn tokenizing back on, and both show on chain.