Binance Security Response Faces Fresh Scrutiny
Binance security response faces scrutiny as CZ demands accountability after an attack and reports cite 98% asset replenishment.
- CZ says Binance must explain the October 29 attack and address security weaknesses rather than dismissing them as unavoidable.
- The reported attack involved a prolonged campaign targeting hundreds of employees and systems, raising questions about internal safeguards.
- Binance reportedly replenished 98% of assets linked to a $6.34 billion hack, although recovery details remain unclear.
Binance security response faces renewed scrutiny after co-founder Changpeng Zhao demanded accountability, while separate reports cited substantial progress replenishing assets.
CZ Demands Answers Over Binance Security Failures
Binance co-founder Changpeng Zhao has criticised the exchange’s handling of security weaknesses. His comments followed an attack reported on October 29. He said unavoidable cyber threats cannot excuse failures that stronger safeguards could prevent.
In remarks shared publicly, CZ rejected the idea that no platform remains completely secure. He argued that each incident exposes weaknesses requiring examination. He also described some details surrounding the incident as embarrassing.
CZ’s comments carry weight because he helped establish Binance. He remains a shareholder and expects the company to explain what happened. He also wants those responsible to address the failures.
His criticism focuses on accountability rather than general cybersecurity assurances. He expects Binance to identify preventable weaknesses and take responsibility. The exchange’s explanation will therefore remain central to the discussion.
Reported Attack Targeted Employees and Systems
The October 29 incident reportedly involved a prolonged campaign. It targeted hundreds of employees and multiple systems, according to the supplied account. This description points beyond an isolated breach or individual account compromise.
However, the available information does not identify the attackers. It also provides no confirmed entry point or technical method. The precise sequence of events therefore remains unclear.
A campaign involving numerous employees raises questions about internal protections. Access controls, employee safeguards and monitoring procedures may require examination. Yet the supplied details do not confirm which measures failed.
CZ said the exchange should not treat such incidents as unavoidable. His remarks place responsibility on Binance to examine its systems. They also call for an explanation beyond broad statements about cyber risks.
Reported Asset Replenishment Raises Further Questions
Additional support from Sahara Reporters reported that Binance replenished 98% of assets. The report linked the figure to a $6.34 billion hack. However, the supplied information does not establish whether this was the October 29 incident.
The word replenished also requires careful interpretation. Replacing affected assets does not necessarily mean recovering the original cryptocurrency. An exchange could use reserves or other resources to compensate affected users.
The report does not explain how Binance achieved the stated recovery figure. It also leaves the remaining two percent insufficiently detailed. Further disclosure would clarify the outstanding balance and compensation arrangements.
These recovery claims and CZ’s criticism concern different aspects of exchange security. One focuses on reported asset restoration, while the other addresses internal safeguards. Binance’s explanations will be needed to clarify both matters.




