Statement of BlockShoals Technologies Inc. on the Binance Security Incident
- Published
- Updated
- Since then
- 2 new reports
- In
- Exchanges
BlockShoals acknowledged Binance’s security incident and the temporary pause in deposits and withdrawals. Binance later said the October 29 incident involved unauthorized wallet-signing access and that its response included freezes, revocations, and loss absorption. BlockShoals also relayed Binance’s confirmation that funds are safe, losses will be covered through SAFU and company funds, and no Philippine user personal information was affected.
Key claims & sources
What it means
Binance’s security incident sits inside a familiar exchange-risk pattern: wallet access, account controls, and user trust all come under scrutiny when an exchange says it has had to intervene in its own systems. BlockShoals is acting as a local point of contact for that event in the Philippines, where users will care about whether deposits and withdrawals stay open and whether their data was touched. The fact that Binance addressed both funds and personal information shows how exchange incidents now overlap custody, operations, and privacy in one case.
For users and builders around Binance, the practical issue is not just the incident itself but the service changes that follow it. Freezes and revocations change how wallets and transfers work for the moment, and any temporary suspension of deposits and withdrawals forces users to wait before moving assets through the platform. The statement that losses will be covered through SAFU and company funds matters because it points to the exchange using its own backstops rather than leaving all exposure with users. (per blockchain.news)
This case puts a spotlight on how centralized exchanges manage operational failure while trying to reassure users that balances and records are intact. The tension is between fast containment and the concentration of control that exchanges keep over signing, access, and recovery tools. Binance’s handling of the incident also shows how one platform’s internal security event can become a customer communications issue across markets, including the Philippines. (per bitpinas.com)
Still open is the full scope of the October 29 incident and how the affected controls were accessed in the first place. The Binance statement names unauthorized wallet-signing access, but it does not settle exactly which systems were touched or how broad the disruption was. The remaining question for users is whether any additional service changes or follow-up disclosures will appear once the response is complete.
Market reaction i
Coverage timeline
Every piece in order, with the time its news medium declares — if it is not believable we use ours and say so — and what it added to what was already known at that point. Arriving first is not the same as adding something.
Other recent incidents
| When | What happened | Figure |
|---|---|---|
| 2 days ago | Degen Coin Flip · Smart contract vulnerability incident | $10k |
| 3 days ago | FLOKI Trading Bot incident | no figure in dollars |
| 3 days ago | TENDRIL · Swap Logic Flaw incident | $550k |
| 3 days ago | $TENDRIL · Smart contract vulnerability incident | $555k |
| 5 days ago | InsurancePool/CoreVault · Flash loan attack incident | $112.3k |
4285 incidents stored