Keplr’s recent incident affected some wallets created with Google or Apple login. Keplr says wallets created with a recovery phrase or hardware wallet were not affected. This is a reminder that the login method changes what you trust.

A familiar login is not the whole wallet

An embedded wallet is built into an app. Some use a single key; others split control using key shares and multi-party computation, or MPC. Designs differ: signing may combine shares without reconstructing a complete private key. Do not assume every social-login wallet uses the same architecture.

Your device, the wallet app, its key-management provider and its recovery service can all be dependencies. Ask who can authorize a transaction, what happens if the provider goes offline, and whether you can export or independently recover the wallet.

Compare the trust model

With a conventional seed-phrase wallet, the recovery phrase can recreate the keys. You take responsibility for keeping that backup secret and available. A software wallet still exposes signing to the security of its device and app.

A hardware wallet keeps signing keys on a separate device and asks you to confirm transactions there. It does not make malicious approvals safe. Verify the destination and action on its trusted display, and protect the recovery backup.

Social login can remove the need to manage a phrase directly, but it does not remove recovery risk. Depending on the design, access to your email, Google or Apple account may help an attacker unlock or recover the wallet. Extra factors and independent shares may limit that path; check rather than assume.

Recovery is part of the security boundary

Read the recovery process before funding a wallet. Find out which factors it needs, who can reset them, whether recovery changes signing authority, and how you would move assets if the provider stopped working. Convenience is useful only when those dependencies are understood.

After an incident, fake support accounts may offer recovery through direct messages or look-alike pages. Web3Auth has warned about fraudulent recovery requests. Open official channels independently, rather than following a message link. Never give anyone a seed phrase, private key or login code.

Practical habits

Protect the linked account with a unique password and phishing-resistant multi-factor authentication where available. Secure its recovery email and review active sessions. Keep wallet software and devices updated.

Keep everyday spending separate from long-term holdings. For larger balances, consider a hardware wallet whose backup you control. Test the documented recovery process with an empty or low-value wallet, and know your exit route before you need it.