**$BNB | Binance Security Incident: Latest Update**
Binance’s preliminary findings suggest the incident may have started when an attacker compromised a DevOps engineer’s laptop. The attacker allegedly used that access to enter a service container and submit unauthorized withdrawal transactions.
So far, Binance says it has found no evidence that wallet private keys were exposed or leaked. After the investigation is finished and the facts are confirmed, the company plans to release a detailed technical post-mortem describing what happened and how the incident occurred.
**Financial impact and user funds**
The estimated total impact is approximately $6.3 billion. Binance is working with blockchain partners to trace and freeze the affected assets; around $3 billion in funds have reportedly been frozen on-chain so far.
Binance says the losses will be covered by the SAFU Fund and the company’s own resources, and that user funds remain protected.
Binance’s preliminary findings suggest the incident may have started when an attacker compromised a DevOps engineer’s laptop. The attacker allegedly used that access to enter a service container and submit unauthorized withdrawal transactions.
So far, Binance says it has found no evidence that wallet private keys were exposed or leaked. After the investigation is finished and the facts are confirmed, the company plans to release a detailed technical post-mortem describing what happened and how the incident occurred.
**Financial impact and user funds**
The estimated total impact is approximately $6.3 billion. Binance is working with blockchain partners to trace and freeze the affected assets; around $3 billion in funds have reportedly been frozen on-chain so far.
Binance says the losses will be covered by the SAFU Fund and the company’s own resources, and that user funds remain protected.
