<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Bitget resumes Bitcoin withdrawals after $387.5 million crypto heist]]></title><description><![CDATA[<p dir="auto"><strong>Bitget</strong> has restored <strong>Bitcoin</strong> withdrawals after a security breach that led to the theft of more than <strong>$350 million</strong> in crypto assets. The exchange had suspended withdrawals following the incident, which is attributed to suspected <strong>North Korean</strong> hackers.</p>
<p dir="auto">The heist is now estimated at approximately <strong>$387.5 million</strong>. Bitget has not disclosed specific technical details about the intrusion vector, and no <strong>CVE</strong> identifiers or advisory numbers have been provided in connection with the breach.</p>
<p dir="auto">Key points:</p>
<ul>
<li><strong>Bitget</strong> suspended <strong>Bitcoin</strong> withdrawals after detecting the breach</li>
<li>Losses exceed <strong>$350 million</strong>, with the total now reported at <strong>$387.5 million</strong></li>
<li>The attack is linked to suspected <strong>North Korean</strong> threat actors</li>
<li><strong>Bitcoin</strong> withdrawals have since been resumed</li>
</ul>
<p dir="auto">Source: <a href="https://www.bleepingcomputer.com/news/security/bitget-resumes-bitcoin-withdrawals-after-3875-million-crypto-heist" target="_blank" rel="noopener noreferrer nofollow ugc">Unknown</a></p>
<p dir="auto">Has your organization reviewed its crypto exchange counterparty risk or withdrawal controls in light of this incident?</p>
]]></description><link>https://xploitlk.com/topic/492/bitget-resumes-bitcoin-withdrawals-after-387.5-million-crypto-heist</link><generator>RSS for Node</generator><lastBuildDate>Tue, 27 Oct 2026 08:20:32 GMT</lastBuildDate><atom:link href="https://xploitlk.com/topic/492.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 28 Sep 2026 10:30:20 GMT</pubDate><ttl>60</ttl></channel></rss>