Pulse2 Binance Security Incident Estimated at $6.3 Billion
Article Content
- •Binance estimates a $6.3 billion impact from a security incident.
- •A compromised laptop of a DevOps engineer is suspected as the attack vector.
- •Binance has frozen $3 billion in affected assets and temporarily suspended withdrawals.
Binance reported a security incident on October 31, 2026, with an estimated impact of $6.3 billion. The breach is believed to have occurred due to a compromised laptop of a DevOps engineer, allowing unauthorized withdrawal transactions. Approximately $3 billion of affected assets have been frozen on-chain with the help of blockchain partners. Binance confirmed that no wallet private keys were leaked and that user funds are safe. The company plans to cover losses through its Secure Asset Fund for Users (SAFU) and company funds. Withdrawals were temporarily suspended while security checks are conducted. Binance is working with law enforcement to trace and recover the funds. A detailed technical post-mortem will be published after the investigation is complete.
Ask AI about this cluster
Answers cite the sources they use
Timeline
More articles in this cluster (2)
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
What caused the security incident?
How much of the loss will Binance cover?
Are user funds safe?
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…