🔥 Binance has confirmed that it will cover all losses resulting from the security incident using its SAFU fund and company funds.

💰 $3 BILLION IN CRYPTO ASSETS FROZEN! Binance is working with blockchain partners and law enforcement agencies to trace and recover the affected funds.

✅ No evidence of wallet private key leakage has been found in Binance’s initial investigation.

🛡️ Binance has reassured users that their funds are safe and is working around the clock to resolve the incident.

📢 Deposits and withdrawals have been temporarily suspended as a precaution while security checks and recovery efforts continue.

⚠️ The investigation is ongoing, and the full technical details have yet to be confirmed.

🚀 THE POSITIVE TAKEAWAY: Binance says it will cover all losses, while billions in affected assets have already been frozen.

2.According to the announcement from Binance, the exchange’s initial investigation suggests that a compromised DevOps engineer’s laptop may have enabled an attacker to access a service container and submit unauthorized withdrawal transactions. Binance said it has found no evidence that wallet private keys were leaked. The estimated total impact is around $6.3 billion, and the company said it has worked with blockchain partners to freeze affected assets, with approximately $3 billion frozen on-chain so far. Binance said it will cover all losses using funds from its SAFU fund and the company, and that user funds are safe. As an immediate precaution, the exchange temporarily suspended deposits and withdrawals while it conducts security checks and revoked authorization for the affected address. Binance has also engaged law enforcement and blockchain intelligence partners to trace and recover funds. The company said it will publish a detailed technical post-mortem after the investigation is complete and the facts are verified. It also plans to publish an updated Proof of Reserves after remediation is complete. The update was issued on 2026-10-30.

3.#NEWS Zilliqa’s CEO has resigned, and a security incident affected X-Bridge and ZRC2 proxy contracts used by some liquidity pools, including those involving zUSDT, SEED, kUSD and Zoge. According to ChainCatcher, the investigation is ongoing, while native ZIL and the Zilliqa EVM network were not affected. X-Bridge will remain paused, and users are advised not to use the bridge or the affected liquidity pools.