<?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 Confirms Third-Party Zero-Day Behind $387.5 Million Cryptocurrency Theft]]></title><description><![CDATA[<p dir="auto"><strong>Bitget</strong> has confirmed that the <strong>$387.5 million</strong> theft it suffered last week was carried out by attackers exploiting a <strong>zero-day vulnerability</strong> in third-party security products. The exchange cited findings from an ongoing investigation conducted by <strong>SlowMist</strong>.</p>
<p dir="auto">According to the investigation, malicious activity involving third-party security products was identified, including the zero-day flaw. Investigators also recovered a customized tool that the attacker had used during the intrusion.</p>
<p dir="auto">Key points from the disclosure:</p>
<ul>
<li>Confirmed stolen amount: <strong>$387.5 million</strong></li>
<li>Root cause: zero-day vulnerability in <strong>third-party security products</strong></li>
<li>Investigation led by <strong>SlowMist</strong></li>
<li>A customized attacker tool was recovered as part of the probe</li>
</ul>
<p dir="auto">The exchange says its investigation remains ongoing. Notably, no specific CVE identifier has been disclosed for the zero-day at this time.</p>
<p dir="auto">Source: <a href="https://thehackernews.com/2026/10/bitget-confirms-third-party-zero-day.html" target="_blank" rel="noopener noreferrer nofollow ugc">The Hacker News</a></p>
<p dir="auto">Does your organization rely on third-party security tooling in ways that could widen your exposure to a supply-chain-style zero-day like this?</p>
]]></description><link>https://xploitlk.com/topic/526/bitget-confirms-third-party-zero-day-behind-387.5-million-cryptocurrency-theft</link><generator>RSS for Node</generator><lastBuildDate>Tue, 27 Oct 2026 10:12:56 GMT</lastBuildDate><atom:link href="https://xploitlk.com/topic/526.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 01 Oct 2026 06:30:35 GMT</pubDate><ttl>60</ttl></channel></rss>