Key points
- Web3Auth published recovery destinations on November 8 and says some protective transfers were mistaken for attacker activity.
- Keplr warns affected Google/Apple-login users to stop new deposits and move remaining liquid assets.
- Recovery-wallet custody does not establish final losses or completed repayment to users.
Web3Auth has published recovery-wallet addresses for the Keplr security incident, saying some transfers previously mistaken for attacker activity were its own protective operations. The November 8 update gives affected users a concrete way to investigate where funds went, while leaving the final loss and return-to-user accounting unresolved.
Keplr recovery wallets change how transfers should be read
In its official recovery thread, posted at 12:23 PM Dhaka time on November 8, Web3Auth says it has been moving assets into secure wallets with Keplr’s assistance. It identifies recovery destinations across eleven Cosmos networks and an address used across eight EVM chains, and says it will update the list as further addresses are verified.
The provider explicitly says those listed destinations are recovery wallets rather than attacker-controlled wallets. That is attribution supplied by Web3Auth, not an independent audit of who controls each key.
Crypto.news independently reports the address disclosure and explains why earlier transfer estimates need care. Its updated report says some destinations linked to suspected theft in Bitquery’s investigation match addresses Web3Auth now identifies as authorized recovery wallets.
The practical consequence is significant: an outgoing transfer is evidence that funds moved. Establishing theft requires knowing who received them and under what authority. A collection-address balance should not automatically become a final customer-loss figure.
What affected users have been told
Keplr’s November 7 user guidance links the incident to a Web3Auth infrastructure vulnerability exposing private keys for some accounts created through Google or Apple login. It warns that reduced or empty balances can reflect mitigation transfers, and says staked or locked assets complicate the recovery process.
Keplr tells potentially affected social-login users to stop sending new funds to those accounts and move any remaining liquid assets to a recovery-phrase or hardware-wallet account. It says accounts created with recovery phrases or hardware wallets are unaffected by this incident. That is the wallet provider’s assessment of this specific breach, not a general guarantee against other wallet risks.
For an affected holder, the useful record is the transaction hash, the chain, the complete destination and the relevant official update. Compare the full destination with the provider’s list on that same chain. Do not send assets to a published recovery address simply because it appears in the list: the announcement identifies destinations already used in the response, rather than giving users a deposit instruction.
Recovery custody still leaves a return question
Moving assets into a recovery wallet and returning them to their owner are separate milestones. The latest thread identifies destinations; it does not supply a complete final reconciliation or a timetable for returning every secured asset.
Keep that distinction when reading claims of a successful rescue. Users need an eventual account-level explanation of what was secured, what remains exposed and how ownership will be established. Until then, avoid treating every empty balance as proven theft or every protective transfer as completed reimbursement.
Panther’s wallet recovery-phrase guide explains why exposed credentials require a separate response from a restored application. In this incident, the immediate guidance should come from the verified Keplr and Web3Auth channels. Unsolicited recovery messages are another risk, especially when users are trying to locate missing funds.
Panther Takeaway
The new address list makes the recovery claim more inspectable. Match transactions to the correct chain and full destination, retain your records, and wait for a verified return process. Recovery custody is progress; it still needs to become an accountable return to users.
Responses
No responses yet. Start the conversation.
Panther Journal — The intelligence brief
Stay ahead of the story.
Free. New investigations delivered when published. Unsubscribe anytime.






