<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Keplr on Mr.Yam</title><link>https://mr.nickyam.com/tags/keplr/</link><description>Recent content in Keplr on Mr.Yam</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 09 Nov 2026 14:28:00 +0800</lastBuildDate><atom:link href="https://mr.nickyam.com/tags/keplr/index.xml" rel="self" type="application/rss+xml"/><item><title>What a Wallet Breach Reveals About Four Key-Custody Models</title><link>https://mr.nickyam.com/Crypto/What-a-Wallet-Breach-Reveals-About-Four-Key-Custody-Models/</link><pubDate>Mon, 09 Nov 2026 14:28:00 +0800</pubDate><guid>https://mr.nickyam.com/Crypto/What-a-Wallet-Breach-Reveals-About-Four-Key-Custody-Models/</guid><description>&lt;p&gt;Bitcoin is back at 75k, and there is not much to say about the price action itself. What was waiting this morning was another security incident in wallet infrastructure.&lt;/p&gt;
&lt;p&gt;Keplr&amp;rsquo;s social-login wallets were compromised, with assets drained from several thousand accounts. The official explanation points to a vulnerability in Web3Auth&amp;rsquo;s infrastructure[1]. Most of the users who lost funds did nothing wrong; they simply chose convenience when they created the wallet with a Google or Apple login.&lt;/p&gt;</description></item></channel></rss>