Elliptic Releases Binance Exploit Blocklist

Elliptic has released a free Binance exploit blocklist in CSV format, enabling crypto businesses to screen transactions linked to the attack. API access is expected to follow, and Elliptic says it will add addresses as investigators trace the stolen funds. The firm attributes the hack to North Korea-linked actors, raising potential sanctions exposure for businesses that handle the funds. Elliptic estimates the theft at $6.43 billion, making it the largest crypto theft on record and more than four times the $1.46 billion taken in the Bybit exploit in February 2025. It says $2.84 billion has been frozen, while the remaining funds may be laundered through the crypto industry over the coming months. The blocklist is intended to help platforms identify stolen funds and reduce laundering routes.
Bearish
The news is bearish for near-term sentiment toward crypto security and the platforms potentially exposed to stolen funds. Elliptic reports a record $6.43 billion theft and says much of the money remains in circulation, creating risks of laundering, sanctions exposure and tighter transaction screening. Traders may respond with caution around Binance-related assets and crypto firms linked to fund flows. The report does not establish that Binance itself suffered a direct loss to its exchange token, so any price effect on BNB is not certain. Large exploits have historically triggered short-lived risk aversion, heightened volatility and closer scrutiny of exchange and DeFi-related exposure. The immediate market reaction will depend on whether investigators identify further addresses, whether funds are frozen or moved, and whether exchanges announce restrictions. Over the longer term, wider use of blocklists and improved monitoring could reduce laundering opportunities and strengthen compliance, but the scale of the alleged theft may also increase regulatory pressure and weigh on confidence. The article provides no market-price or liquidity data, so the direction and size of any asset-specific move cannot be determined from this information alone.