Binance announced a phased restoration of withdrawals after a security incident. Phase one includes Bitcoin and selected assets on other networks, so the restart is not limited to BTC. The exchange said services would return as stability and security checks are completed.
Binance began restoring withdrawals in phases after suspending them for security checks.
In an official update on November 1, 2026, Binance set a 06:00–09:00 UTC window for phase one. CoinDesk reported that the exchange began the phased restart on Sunday. This is a new development in the incident: it concerns service restoration, rather than a new report about the attack itself.
The phrase “starting with Bitcoin” needs context. BTC is included, but Binance’s official phase-one list also covers selected assets on other networks. The exchange said deposits remained open.
Phase one covers BTC and selected assets across 15 networks, including Ethereum, BNB Smart Chain, Tron, Solana, and XRP.
Binance’s published list includes BTC on Bitcoin; ETH, USDT, and USDC on Ethereum; BNB, USDT, and USDC on BNB Smart Chain; TRX and USDT on Tron; SOL, USDT, and USDC on Solana; and XRP, ZEC, and DOGE on their respective networks. Selected assets are also listed for TON, Polygon, Avalanche C-Chain, Arbitrum, Base, Optimism, and Sui.
This is the phase-one list, not a guarantee that every asset can be withdrawn on every network. Binance said additional networks and assets would be added as they become ready.
Binance said a phased rollout allows it to check the readiness, stability, and security of services for each network and asset pair.
The exchange said it prioritized networks and pairs using user-demand data from the previous week, and would restore access after the required checks. The approach avoids reopening every withdrawal route at once while technical and security checks are underway.
The reopening of some withdrawals does not establish that the incident investigation is finished or that every platform function has been restored. The available announcements describe a gradual service restart.
Check the specific coin and network in Binance’s withdrawal interface, and make sure the sending network matches the receiving address.
Binance directed users to its withdrawal page or network-status page for current availability. The announced phase-one list is not a substitute for checking the live status.
No. BTC is included, but Binance listed selected assets across 15 networks for the first phase.
Not necessarily. The announcements confirm a phased service restoration; they do not establish that the investigation is complete or that every withdrawal route is available.
Check Binance’s withdrawal interface or network-status page. Availability depends on both the asset and the selected network.
On October 29, 2026, Bitcoin traded below $77,000 and BNB was down 7.1% over 24 hours amid reports of a Binance security incident. The Block also reported substantial liquidations. These figures describe a specific market snapshot; they do not prove the incident was the sole cause of the broader decline.
In The Block's October 29 snapshot, Bitcoin was at $76,664 after a 4.5% 24-hour decline, while BNB was down 7.1%.
The Block reported that Bitcoin had slipped below $77,000 as several major crypto assets also declined. In the same snapshot, Ether was down 5.2% and XRP was down 7%. These are time-specific figures from the report, not current prices.
The move coincided with reports of a Binance security incident. That timing is relevant to understanding the market response, but it does not by itself establish what caused every part of the sell-off.
At the time of the reports, Binance said it was investigating a potential security issue; The Block reported that the exchange's co-CEO pledged to cover user losses.
The Associated Press described Binance as investigating a potential security issue and reported that the company’s founder said the event looked like a hack. The Block described an exploit and reported that co-CEO Yi He said Binance would cover user losses related to it.
Reports, preliminary estimates and confirmed technical findings are not the same thing. The sources reviewed here do not establish a definitive technical root cause, so a specific attack scenario should not be presented as proven.
The Block reported $1.55 billion in liquidations over 24 hours, including $1.34 billion in long positions.
Forced position closures can accompany sharp market moves and add pressure to prices. The liquidation total is a time-specific figure reported by The Block, citing CoinGlass, rather than a final tally for the entire period following the news.
For trading platforms, a practical takeaway is to review how margin monitoring, risk limits and alerts behave when liquidity or prices shift quickly. This is a general risk-management recommendation, not a claim about the precise mechanisms behind liquidations in this episode.
The episode underscores the value of security and market-risk readiness, but does not reveal a confirmed technical failure mode.
When a major security incident is reported, platform operators can use it as a prompt to review practical readiness in several areas:
This is a general review checklist, not a description of confirmed shortcomings at Binance. The sources do not specify which infrastructure changes the company will make after the incident.
The Block reported the move late on October 29, 2026. Its snapshot at about 10:00 p.m. ET put Bitcoin at $76,664.
The Block reported a 7.1% 24-hour decline in BNB in its October 29, 2026 market snapshot.
In the reports reviewed, Binance said it was investigating a potential security issue. Those reports do not establish a definitive technical root cause.
That is not established. The market decline coincided with reports of the incident, but the available data does not prove it was the sole cause of declines across crypto assets.
In an attack detected on October 25, 2026, an intruder took over five Bitonic customer accounts and withdrew bitcoin from three of them. Bitonic said it fully reimbursed affected customers, fixed the vulnerability, and is continuing its investigation.
Bitonic said an intruder accessed part of its systems on the evening of October 25 and took over five customer accounts.
Bitcoin was withdrawn from three accounts. An ANP report published on October 28 put the loss at approximately €200; the exact amount in BTC was not publicly specified. Bitonic said it fully reimbursed the affected customers.
Early reports described unauthorized access and changes to account login details. A later update said five accounts were taken over, while withdrawals occurred from three.
In an interview with BNR, Bitonic’s CEO linked the intrusion to a vulnerability in the PDF-upload feature used for verification, while the investigation remains ongoing.
The CEO said the vulnerability involved processing PDF files uploaded through the verification feature. This is the company’s explanation as reported in an interview, not a final published technical postmortem.
After discovering the issue, Bitonic took affected systems offline as a precaution, then fixed the vulnerability and restored services. The available reports do not provide a full technical account or final investigation results.
There is no final confirmation that other customers’ personal data was accessed or stolen; Bitonic said it could not rule out that possibility while its investigation continued.
As of October 28, the company said it had no indication that personal data beyond the affected accounts had been taken, but noted that its review was ongoing. The available information therefore supports neither a claim of a confirmed wider data leak nor a definitive claim that no access occurred.
Media reports say Bitonic preserved digital evidence and planned to provide it to police. The company also reported contacting relevant supervisory authorities.
Customers should follow Bitonic’s official notices, use app-based authentication, and never share login codes or send funds in response to suspicious requests.
Reports about the incident advised customers to review their account security and watch for messages impersonating Bitonic. Practical steps include:
These steps do not replace Bitonic’s official instructions. Customers with concerns should contact the company through verified channels.
An update on October 28 said five accounts were taken over. Bitcoin was withdrawn from three of them.
Yes. The company said it fully reimbursed the affected customers.
No. As of October 28, Bitonic had not reported a confirmed breach of data beyond the affected accounts, but it said access could not be ruled out while the investigation continued.
Bitonic’s CEO linked the intrusion to a vulnerability in the PDF-upload feature used for verification. The available reports did not include a final technical postmortem.