<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Hack on Armur</title>
    <link>https://armur.ai/blogs/tags/hack/</link>
    <description>Recent content in Hack on Armur</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 22 Feb 2025 15:20:22 +0530</lastBuildDate>
    <atom:link href="https://armur.ai/blogs/tags/hack/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Bybit’s $1.4 Billion ETH Hack and the Need for ARMUR</title>
      <link>https://armur.ai/blogs/posts/bybit_crypto_hack/</link>
      <pubDate>Sat, 22 Feb 2025 15:20:22 +0530</pubDate>
      <guid>https://armur.ai/blogs/posts/bybit_crypto_hack/</guid>
      <description>&lt;p&gt;The cryptocurrency industry was shaken on February 21, 2025, when &lt;a href=&#34;https://www.bybit.com/en/&#34;&gt;Bybit&lt;/a&gt;, confirmed a hack resulting in the loss of approximately $1.4 billion in Ethereum (ETH) and related tokens, marking it as the largest cryptocurrency theft in history. This incident, detailed in various reports, underscores the escalating sophistication of cyber attacks in the cryptocurrency space.&lt;/p&gt;&#xA;&lt;h4 id=&#34;a-glance-into-the-bybit-hack&#34;&gt;A Glance into the Bybit Hack&lt;/h4&gt;&#xA;&lt;p&gt;The Bybit hack involved a sophisticated attack on the exchange&amp;rsquo;s Ethereum cold wallet, a storage system designed to be offline for enhanced security The breach occurred during a routine transfer from the cold wallet to a warm wallet, a process that typically involves moving funds for operational purposes while maintaining some level of connectivity. Reports indicate that hackers manipulated the signing interface, deceiving wallet signers into unknowingly approving a malicious transaction. This manipulation displayed the correct address to the signers while altering the underlying smart contract logic, enabling unauthorized access and the subsequent draining of funds.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
