【New developments in the Binance incident: The suspected source was a DevOps engineer’s laptop】
Binance update, October 30: Preliminary investigations indicate that the attacker may have gained access to a service container through a compromised DevOps engineer’s laptop and submitted unauthorized withdrawal transactions. No wallet private-key leaks have been found so far. Binance estimates the impact at approximately $6.3 billion, with about $3 billion frozen on-chain (approximately 1.57 billion USDT by Tether and 800 million USDC by Circle). Binance has pledged to cover all losses using SAFU and its own funds. A detailed postmortem will be published after the investigation is complete.
CoinDesk also reported that the affected hot wallet appeared in the October 1 Proof of Reserves. Based on the data available at the time, the transfer of approximately 204,500 ETH would have brought ETH reserve coverage down to around 94%. The November 1 reserve snapshot is worth watching.
Security tips from an engineer’s perspective:
1. No private-key leak doesn’t mean you’re safe—the weak points may be the development machine, container permissions, and withdrawal risk controls;
2. Beware of phishing attempts impersonating customer support or offering “official compensation.” Trust only official channels;
3. Spread your assets around. Don’t keep everything on a single platform; self-custody larger amounts and enable a withdrawal whitelist.
Will this incident change how you distribute your funds? Share your thoughts in the comments.
$BNB $BTC $ETH
#币安 #安全事件 #ProofOfReserves
DYOR, not investment advice
Binance update, October 30: Preliminary investigations indicate that the attacker may have gained access to a service container through a compromised DevOps engineer’s laptop and submitted unauthorized withdrawal transactions. No wallet private-key leaks have been found so far. Binance estimates the impact at approximately $6.3 billion, with about $3 billion frozen on-chain (approximately 1.57 billion USDT by Tether and 800 million USDC by Circle). Binance has pledged to cover all losses using SAFU and its own funds. A detailed postmortem will be published after the investigation is complete.
CoinDesk also reported that the affected hot wallet appeared in the October 1 Proof of Reserves. Based on the data available at the time, the transfer of approximately 204,500 ETH would have brought ETH reserve coverage down to around 94%. The November 1 reserve snapshot is worth watching.
Security tips from an engineer’s perspective:
1. No private-key leak doesn’t mean you’re safe—the weak points may be the development machine, container permissions, and withdrawal risk controls;
2. Beware of phishing attempts impersonating customer support or offering “official compensation.” Trust only official channels;
3. Spread your assets around. Don’t keep everything on a single platform; self-custody larger amounts and enable a withdrawal whitelist.
Will this incident change how you distribute your funds? Share your thoughts in the comments.
$BNB $BTC $ETH
#币安 #安全事件 #ProofOfReserves
DYOR, not investment advice