Skip to content
Binance $6.3B Hack: 4-Month Attack Chain via Fake Interviews & EIP-7702

Binance $6.3B Hack: 4-Month Attack Chain via Fake Interviews & EIP-7702

A detailed analysis of the $6.34 billion Binance hack revealing a four-month attack chain involving supply chain compromise, fake recruitment malware delivery, lateral movement via internal AI tools, and exploitation of Ethereum's EIP-7702 authorization mechanism that bypassed withdrawal pauses.

ITPUB
ITPUB
ITPUB

Event Timeline: 4 Months, 4-Step Attack Chain

Step 1: June – Supply Chain Reconnaissance

A wallet development team engineer downloaded a tampered Homebrew installer while searching for AI coding tools. Binance's security team later detected the anomaly, replaced the device, and reset credentials, but the attackers had already mapped the engineer's role, wallet team permissions, and internal team structure. This step did not directly steal assets but completed critical reconnaissance: identifying who controlled wallets, who held permissions, and how the team was organized.

Step 2: September – Fake Recruitment Malware Delivery

Attackers targeted another Binance engineer on a legitimate job platform, posing as HR and the "company CEO." They conducted two video interviews, even sharing social media accounts, personal photos, and videos to lower suspicion. At the end of the interview, the attackers sent an "interview assignment code package." The engineer downloaded and ran it on a company computer, where the malicious program silently replaced the legitimate pyenv development tool, planted a backdoor, and established a connection to the attacker's server. Binance stated the malware was not detected by endpoint security tools at the time.

Step 3: October 20 – Internal AI Tool as Lateral Movement Pivot

After compromising Engineer B's computer, the attackers did not rush. Instead, they leveraged Binance's internal AI tool to move laterally within the intranet, gaining control of Engineer A's and Engineer C's devices. On Engineer A's machine, they found a critical token with container deployment permissions. Possessing this permission brought them a major step closer to the wallet signing service.

Step 4: October 29–30 – Theft Execution

Attack diagram showing malicious container deployment and wallet signing service compromise
Attack diagram showing malicious container deployment and wallet signing service compromise

The attackers logged into Engineer C's computer, used the stolen permissions from Engineer A to deploy a malicious container, and triggered a malicious script to gain unauthorized access to the wallet signing service. They then exploited the EIP-7702 mechanism to submit a malicious delegation authorization to the hot wallet, granting execution rights to an attacker-controlled contract. Because this authorization was written on-chain, Binance's withdrawal pause could not automatically revoke it; a separate on-chain revocation transaction was required. From the first anomalous transfer to the revocation of the malicious authorization, the process lasted several hours. Ultimately, approximately $6.34 billion in assets were moved across multiple chains.

Why Pausing Withdrawals Failed to Stop the Theft

Many initially assumed that pausing withdrawals would halt the attack. However, this attack did not simply "initiate a withdrawal from the backend"; it directly reached the wallet signing and on-chain authorization layers. Binance's hot wallet uses an MPC (Multi-Party Computation) multi-signature architecture with no single private key that can be instantly revoked. The attackers, via EIP-7702, obtained on-chain delegation rights. In effect, the exchange shut down the frontend withdrawal channel, but the on-chain "automatic money-moving program" remained active . This is the most dangerous aspect: the attackers did not bypass risk controls; they made the risk controls "unable to see and unable to stop" the theft.

Public Outcry: Security Awareness and Permission Management Gaps

Binance loses $6.3B, hackers hunt engineers for 4 months
Binance loses $6.3B, hackers hunt engineers for 4 months

Public criticism focused on two points:

Insufficient employee security awareness: Downloading an interview code package of unknown origin on a work computer clearly violated basic security policies.

Enterprise permission management shortcomings: Why did the wallet team managing billions allow development tools to be replaced? Why could an internal AI tool become a lateral movement springboard? Why could a high-privilege token be used to deploy malicious containers?

Observers noted this was not merely "one person making a low-level mistake" but "a continuous failure of a trust chain." From endpoints, permissions, signing services, to on-chain authorizations, each layer had some protection, but the trust propagation between layers was fully exploited by the attackers.

Latest Progress: Assets Replenished but Recovery Remains Complex

As of November 13, Binance announced it had completed replenishment of all affected assets and released a latest proof-of-reserves snapshot. Two concepts must be distinguished:

Asset replenishment: The platform used its own funds, the SAFU fund, and insurance funds to cover user balances, so user account balances are unaffected.

Fund recovery: Whether stolen assets truly return to the platform or law enforcement control depends on freezing, on-chain tracking, and legal proceedings.

Previously, Binance disclosed that approximately $2.85 billion in assets had been frozen or intercepted; the U.S. Department of Justice also announced authorization to seize or restrict over $1.2 billion in related assets. However, "frozen" does not equal "recovered"; some funds may continue to move via mixers, cross-chain bridges, and low-liquidity token swaps.

Three Industry Warnings

The biggest vulnerability is often not code, but people. Attackers did not frontally breach Binance's core systems; they infiltrated via job platforms, development tools, and internal AI tools. For high-value institutions, employee devices are the front line.

AI tools must not only boost efficiency but also prevent misuse. If an internal AI tool is invoked from a compromised endpoint, it can become a lateral movement springboard. Enterprises must bring AI tools within permission boundaries, audit scopes, and anomaly behavior monitoring systems.

New on-chain features can become new attack vectors. EIP-7702 was designed to make accounts more flexible, but once maliciously authorized, it creates an "on-chain backdoor." Exchanges, wallets, and protocol teams need stricter approval, monitoring, and emergency revocation processes for such new authorization mechanisms.

Conclusion

The most shocking aspect of this incident is not the $6.34 billion figure, but the completeness of the attack path: reconnaissance → malware delivery → lateral movement → high-privilege acquisition → abuse of on-chain authorization → multi-chain theft . It reminds all institutions that security is not just about buying firewalls and conducting audits. As long as one link among people, endpoints, permissions, AI tools, and on-chain authorizations fails, the entire system can be pried open. For users, the event reiterates that no platform, however large, equals absolute safety. Diversifying asset storage, enabling multi-factor authentication, and cautiously approving contract permissions remain the most basic self-protection measures.

Original Source

Signed-in readers can open the original source through BestHub's protected redirect.

Sign in to view source
Republication Notice

This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactadmin@besthub.devand we will review it promptly.

incident-responselateral movementsupply chain attackBinanceEIP-7702cryptocurrency exchange hackfake recruitmentMPC wallet
Reader feedback

How this landed with the community

Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.