Pulse2 Binance Hack Estimated at $6.3 Billion; 90% of Losses Covered
Article Content
- •Binance's security breach resulted in an estimated $6.3 billion impact.
- •90% of the losses have been covered using company funds and SAFU.
- •Withdrawals are expected to resume on November 1, 2026.
Binance reported a significant security incident with an estimated impact of $6.3 billion, attributed to unauthorized withdrawal transactions facilitated by a compromised employee laptop. The exchange has successfully covered 90% of the losses using corporate funds and its Secure Asset Fund for Users (SAFU). Approximately $3 billion of affected assets have been frozen on-chain, and Binance is collaborating with law enforcement to trace and recover the stolen funds. The remaining 10% of losses are in less liquid tokens, which may take longer to source. Withdrawals were temporarily paused but are expected to resume on November 1, 2026. Binance has confirmed that no wallet private keys were leaked during the incident. The breach has drawn attention to operational security risks within cryptocurrency platforms.
Ask AI about this cluster
Answers cite the sources they use
Timeline
More articles in this cluster (7)
Following this threat?
Track Binance in your own feed — you're alerted when they show up in new reporting, leak sites or exploitation.
Free account · no card needed
Common questions
How much of the loss has been covered?
What caused the breach?
When will withdrawals resume?
Continue Reading
North Korean Hackers Steal $6.3 Billion from Binance in Record Crypto Heist On October 29, 2026, Binance, the world's largest cryptocurrency exchange, reported a massive security breach resulting in the theft of approximately $6.3 billion across ten blockchains. The attack is attributed to North Korea's TraderTraitor hacking group, which gained access via a compromised DevOps engineer's…
Chinese Actor Compromises US Government Networks via PHP2Shell Exploit A suspected Chinese nation-state actor exploited vulnerabilities in Palo Alto Networks firewalls using a chained PHP2Shell exploit and a Linux kernel privilege escalation flaw. The attack, which began on October 23, targeted 25 servers across the US, Japan, Taiwan, and South Korea, with a focus on US…