<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Odeyemi Ibukun</title>
    <description>The latest articles on DEV Community by Odeyemi Ibukun (@odeyemi_ibukun_c67b4a147e).</description>
    <link>https://dev.to/odeyemi_ibukun_c67b4a147e</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F2732520%2F3d9c5d7e-1135-47f6-9e60-6f6458da2b8c.jpg</url>
      <title>DEV Community: Odeyemi Ibukun</title>
      <link>https://dev.to/odeyemi_ibukun_c67b4a147e</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/odeyemi_ibukun_c67b4a147e"/>
    <language>en</language>
    <item>
      <title>Nobody Needed to Steal the Key: How the $6.36B Hot Wallet Exploit Happened—and How to Stop It</title>
      <dc:creator>Odeyemi Ibukun</dc:creator>
      <pubDate>Thu, 05 Nov 2026 11:48:58 +0000</pubDate>
      <link>https://dev.to/odeyemi_ibukun_c67b4a147e/nobody-needed-to-steal-the-key-how-the-636b-hot-wallet-exploit-happened-and-how-to-stop-it-1ndn</link>
      <guid>https://dev.to/odeyemi_ibukun_c67b4a147e/nobody-needed-to-steal-the-key-how-the-636b-hot-wallet-exploit-happened-and-how-to-stop-it-1ndn</guid>
      <description>&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Flwi9vq7syytwmvncludl.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Flwi9vq7syytwmvncludl.webp" alt=" " width="600" height="338"&gt;&lt;/a&gt;&lt;br&gt;
I've been looking for ways to mitigate hot-wallet theft, particularly following the October 2026 crypto theft reported by TRM Labs.&lt;/p&gt;

&lt;p&gt;In that incident, an attacker exploited an exchange's existing signing infrastructure rather than extracting its private key. On Ethereum, the hot wallet had signed 50 EIP-7702 authorizations in advance. One matched the wallet's current nonce, allowing a sweeper contract to take control of the account.&lt;/p&gt;

&lt;p&gt;What caught my attention was that the signatures were valid. The signing system simply executed instructions it was authorized to sign.&lt;/p&gt;

&lt;p&gt;I started exploring a question: how can we prevent a hot wallet from blindly signing dangerous transactions, even when the application requesting signatures is compromised?&lt;/p&gt;

&lt;p&gt;That led me to &lt;a href="https://github.com/globalmpc/rwa-kit-js" rel="noopener noreferrer"&gt;https://github.com/globalmpc/rwa-kit-js&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;packages expecially &lt;a href="https://github.com/globalmpc/rwa-kit-js/tree/main/packages/sign-guard" rel="noopener noreferrer"&gt;@globalmpc/sign-guard&lt;/a&gt; &lt;/p&gt;

&lt;p&gt;A sign-guard puts a written policy in front of the key. Same requests, same key, one difference:&lt;/p&gt;

&lt;p&gt;✅ the normal call is signed&lt;br&gt;
❌ an unknown delegation, a full-balance send and a raw hash are refused&lt;/p&gt;

&lt;p&gt;Only what the policy names gets signed.&lt;br&gt;
&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fega6naqw14ud728ah9sc.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fega6naqw14ud728ah9sc.webp" alt=" " width="720" height="405"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;and &lt;a href="https://github.com/globalmpc/rwa-kit-js/tree/main/packages/hot-wallet-watch" rel="noopener noreferrer"&gt;@globalmpc/hot-wallet-watch&lt;/a&gt;, &lt;/p&gt;

&lt;p&gt;A Hot-wallet-watch reads your hot wallets every few seconds and alerts on the signs a takeover can't hide: a delegation you didn't approve, code at the address, a nonce you didn't move, outflows over a cap.&lt;/p&gt;

&lt;p&gt;Same night, replayed: alarm one block later, 6 sweeps stopped.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fhs6wv6bb5cyk7hnrlgrj.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fhs6wv6bb5cyk7hnrlgrj.webp" alt=" " width="720" height="405"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Together they shrink a breach from "drain everything" to "what the policy allows", and catch it fast &lt;/p&gt;

&lt;p&gt;for reference you can check this out Globalmpc documentations &lt;/p&gt;

&lt;p&gt;Resources:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;npm package: github.com/globalmpc/rwa-kit-js/sign-guard&lt;/li&gt;
&lt;li&gt;Source code, policy reference and refusal rules: github.com/globalmpc/rwa-kit-js&lt;/li&gt;
&lt;li&gt;Wallet monitoring: @globalmpc/hot-wallet-watch&lt;/li&gt;
&lt;li&gt;Incident analysis: TRM Labs&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>community</category>
      <category>discuss</category>
      <category>webdev</category>
      <category>web3</category>
    </item>
  </channel>
</rss>
