Binance founder Changpeng Zhao: This hack is more complex than the advice
On October 30, 2026, Binance founder Changpeng Zhao (CZ) replied on X to his security advice post published on October 28, saying that he hoped everyone would follow that advice. He pointed out that this hack is more complex than the situation the advice was aimed at, but that all hacks usually involve a compromised device (or algorithm) at some stage.
CZ’s original post on October 28 said: “Do not click links in emails. Do not download attachments. Even if they come from people you trust, their computers may also be infected with a virus without them knowing it.” This reply came after Binance announced preliminary investigation results (possibly beginning with a DevOps engineer’s laptop being compromised and no wallet private key leakage being found).
Original sources:
Title: I wish everyone followed that advice. Publisher: CZ 🔶 BNB (@cz_binance) Publication date: 2026-10-30 URL: https://x.com/cz_binance/status/2116082886810218831 Source type: original post by the person involved Verification status: the full post and conversation context were actually read for this report, verification date 2026-10-30 Supporting content: hopes everyone will follow his earlier security advice; this hack is more complex than that advice; all hacks usually involve a compromised device (or algorithm) at some stage
Title: Do NOT click links in emails. Publisher: CZ 🔶 BNB (@cz_binance) Publication date: 2026-10-28 URL: https://x.com/cz_binance/status/2115516716331536682 Source type: original post by the person involved Verification status: the original post content was actually read for this report, verification date 2026-10-30 Supporting content: do not click email links, do not download attachments; even if they come from someone you trust, their computer may already be infected with a virus
ABAB AI Insight
Changpeng Zhao stepped down as Binance CEO in 2023 due to related U.S. Department of Justice allegations and remains the company’s main shareholder. This reply was made after Richard Teng had already clarified that the attack was not a one-click operation with a single engineer’s access, and it adds to his own terminal security advice published on October 28. That advice stressed not clicking links or downloading attachments, even from trusted sources, because the other party’s device may already be infected with a virus.
The current Binance incident initially points to a DevOps engineer’s laptop being compromised, which then allowed access to service containers and the submission of unauthorized withdrawals, consistent with the “compromised device” path emphasized by CZ. In 2019, Binance suffered a theft of about $40 million from its hot wallet; CZ then immediately paused withdrawals for about a week and completed a system migration. Compared with Bybit’s roughly $1.5 billion incident in 2025, in which the FBI determined that North Korea’s TraderTraitor group infiltrated the signing interface through a third-party developer’s device, both cases involved a compromised endpoint or interface rather than direct private key leakage, but Binance’s case is larger in scale and occurred at the internal service container layer.
CZ characterizes this attack as “more complex than the advice,” while also placing it within the general pattern that all hacks usually involve a compromised device or algorithm at some stage, helping shift attention from a single employee mistake to an industry-wide endpoint security issue. This does not change the fact that Binance has promised to cover losses with SAFU and company funds, but it reinforces his public statement as a shareholder about the complexity of the incident.
This statement changes the external interpretive frame for Binance’s internal controls: it further anchors the incident not in “a single engineer having too much access” but in a device compromise, a common industry entry point, while making clear that the attack process was more complex than the scenario addressed by ordinary phishing advice. For Binance, this temporarily reduces immediate criticism of a specific operational process, but it shifts the focus of the subsequent technical review to privilege separation and monitoring between devices and service containers; the key indicator will be whether the official review discloses the specific intrusion path and privilege boundaries of that engineer’s device.
ABAB News · Cognitive Law
All hacks usually involve a compromised device or algorithm at some stage, and a single-access-permission advisory cannot cover a more complex attack process.
A compromised endpoint can serve as an entry point for an attack, but that does not mean a single engineer’s privileges alone are enough to complete a funds transfer on the scale of tens of billions of dollars.