Blockchain

Binance Lacks Cyber Insurance for $6.3 Billion Hack, Bloomberg Law Reports

Read full article at source ↗

Based on a feed excerpt; full article content has not been acquired. Source evidence retrieved 03/11/2026, 12:12:24 UTC.

Briefings

Bloomberg Law reports that Binance has reserved over $6.34 billion in company funds and emergency reserves to replace stolen assets following a major hack. The exchange is drawing from its own reserves rather than external insurance, though the specific coverage status of this reserve remains unclear. This action occurred in late 2026, with the exchange stating it is drawing on emergency and futures reserves to replace stolen assets.

Key points

• Binance reserved more than $6.34 billion in company funds and emergency reserves to replace stolen assets following a major hack.
• The exchange is drawing from its own reserves rather than external insurance, though the specific coverage status of this reserve remains unclear.

Context

Bloomberg Law reports on Binance's response to a significant cyber incident in late 2026, where the exchange reserved over $6.34 billion in company funds and emergency reserves to replace stolen assets. This action occurred in late 2026, with the exchange stating it is drawing from its own reserves rather than external insurance, though the specific coverage status of this reserve remains unclear.

Limitations

The evidence is limited to a single Bloomberg Law report published in late 2026. It does not specify the exact date of the hack, the number of stolen assets, or the specific types of assets lost. The report does not confirm whether the $6.34 billion reserve is fully covered by insurance or if it is a general emergency fund. The source does not provide details on the timeline of the hack or the specific impact on user funds.

Generated by Bittrees-hosted qwen35-2b sha256:aaf42c8b7c3c on 08/11/2026, 20:35:22 UTC. Based on publisher-provided feed evidence; may not cover the full original article. Check the source for details.

View archived briefing on IPFS
bafybeig2eome63lhlx7izzoysry3zn5os2olxsjswvo3x2htb37fg7tnn4