Binance Bleeds $5.28B Net Outflows As Native Withdrawals Resume
Key Summary
Binance recorded $10.97B in withdrawals against $5.69B in deposits during the first 46 hours after reopening, leaving $5.28B in net outflows as native asset withdrawals slowly resume.
Key Bullets
- Binance reported roughly $10.97B in customer withdrawals during the initial 46 hours after reopening platforms following the October 29 security incident.
- Data compiled by CoinDesk and co-CEO Richard Teng confirmed net outflows reached $5.28B as incoming deposits totaled only $5.69B.
- Cryptographic Proof of Reserves published by Binance for October 31 covered just 10 selected assets compared to the previous 55 tokens.
- Dogecoin community contributor Mishaboar warned users to verify native network selections and secure private wallet backups before initiating transfers.
Binance Bleeds Billions In Net Outflows
Binance registered $10.97B in customer withdrawals over the first 46 hours after reopening exchange access, according to operational figures shared by co-CEO Richard Teng and published by CoinDesk. Incoming deposits during the same 46-hour window stalled at $5.69B. That commercial imbalance left the platform with $5.28B in net outflows by early November 3. Heavy withdrawal pressure peaked on Sunday before hourly deposit velocity began matching outflows.
The massive liquidity drain followed a security breach involving $6.34B in digital assets across multiple blockchain networks. Binance disclosed that attackers compromised engineering staff through malicious software, fake job interviews, and a tampered devtool installer. The perpetrators then bypassed wallet-signing controls by exploiting an internal artificial intelligence tool and stolen deployment credentials. The platform subsequently froze or intercepted $2.85B of the compromised funds.
Reserves Scrutinized As Insurance Funds Tap
Binance stated that it replaced the vast majority of missing token balances using internal corporate resources, including the SAFU fund and the Futures Insurance Fund. Published replenishment percentages showed internal discrepancies regarding exact asset recovery metrics. Security analysts noted that replacing stolen funds with insurance capital alters the internal risk profile for remaining depositors. Insurance allocations don't equal actual fund recovery from attackers.
The exchange published a cryptographic Proof of Reserves snapshot based on October 31 balances covering only ten selected assets. That count represents a sharp drop from the 55 assets included in previous exchange snapshots, leaving numerous smaller tokens unverified. Dogecoin community figures noted that native DOGE withdrawals were prioritized in the first reopening phase. Users rushed to secure funds on private hardware.
Dogecoin Contributors Issue Urgent Safety Warnings
Dogecoin community member Mishaboar published safety guidance advising token holders to verify proper network settings before moving coins off centralized venues. The advisory emphasized selecting the native Dogecoin network rather than wrapped alternatives such as Binance-pegged tokens on BNB Smart Chain. Community leaders urged traders to avoid panic and prioritize proper offline wallet backups before executing transfers.
On-chain analysis revealed that attackers utilized malicious EIP-7702 authorizations on Ethereum to continue shifting funds even after normal withdrawal halts took effect. Security observers questioned why multi-sig signing controls permitted those authorizations for nearly four hours during the containment phase. Independent forensic reviews remain pending across several affected blockchain protocols.
About CryptoNewsFree Market Intelligence Wire
The CryptoNewsFree Market Intelligence Wire provides rapid, objective coverage of breaking crypto developments, regulatory actions, and market liquidity trends. Our reporting strictly follows our Editorial & Verification Standards.