Binance Hack Chain: Fake Interviews, AI Tool, EIP-7702
By @sharedot · · 7 pages
- Programming
- Security
- Binance
- Eip 7702
- Supply Chain
Binance's initial findings trace the October 29 theft to fake job interviews, a tampered Homebrew install, its internal AI tool, and EIP-7702 abuse.
What Happened: A Months-Long Attack Chain
Binance's initial findings, published November 3, 2026, describe a patient intrusion that began months before the October 29 theft of approximately $6.34 billion in digital assets.
In June 2026, a wallet DevOps engineer downloaded a tampered Homebrew installation while trying to install a popular AI coding tool found via a search engine.
In September 2026, a software engineer was contacted through a legitimate job-hunting platform by someone posing as a project director, then ran staged interviews with a purported HR representative and a supposed CEO before downloading a coding assignment containing a malicious code repository onto a work computer.
Why It's Surprising: The Internal AI Tool as a Ladder
The striking detail for developers is that attackers apparently treated Binance's own internal AI tool as lateral-movement infrastructure.
According to Binance's disclosure, on October 20, 2026 the attacker used the compromised engineer's computer together with that internal AI tool to extend control to the wallet DevOps engineer and another wallet software engineer.
Fortune's coverage frames the same pivot, noting that speculation about AI-driven intrusion missed the point: the social engineering was conventional, but the AI tooling became part of the attack surface once a laptop that could reach it was compromised.
The Evidence: Nine Days of Foothold and the EIP-7702 Twist
The malware replaced a legitimate pyenv component and contacted an attacker-controlled server, and Binance says endpoint protection failed to detect the zero-day at the time.
On October 29, between 17:15 and 19:56 UTC, the attacker logged into the third engineer's computer and deployed a container that launched the wallet attack.
unite.ai reports the attacker then abused Ethereum's EIP-7702 delegation mechanism, with fifty signing transactions manipulating the account nonce and establishing malicious delegation authorizations over a Binance hot wallet — permissions that stayed valid even after withdrawals were suspended.
The Stakes: On-Chain Authority Outlives Containment
The EIP-7702 abuse created a containment problem that extends beyond malware detection: suspending withdrawals and shutting down hot-wallet services did not invalidate existing on-chain permissions, and because the wallet used multi-party computation, there was no single private key available for immediate revocation.
Binance says it set aside more than 100% of the funds needed to cover the loss, replenished 98% of impacted token assets by October 31, and froze or intercepted approximately $2.85 billion, while Fortune reports roughly $2.5 billion recovered after Tether and Circle froze stolen stablecoins.
What Comes Next: Rebuilds, Independent Review and Open Questions
As of November 3, Binance says it has rebuilt the affected wallet system in a new environment, rebuilt the internal AI tool and its access controls, replaced devices, rotated credentials, and expanded AI-based behavioral-anomaly detection, with independent third-party experts being engaged to validate the findings.
Binance is withholding some technical details to avoid helping attackers plan future strikes.
Fortune also notes Binance said it detected and prevented 57 North Korea-related hacking attempts in 2026, and that employees in non-public-facing roles are barred from maintaining LinkedIn profiles — a policy question the disclosure now puts front and center for engineering teams everywhere.