Skip to content
Basis Desk

New from Basis Desk: free Telegram proxies for places where Telegram is blocked or slowed down.Connect in one tap →

Security & Hacks · 2 min read

Binance Details Breach Path in $6.34 Billion Hot Wallet Theft

A tainted developer software install and a fake job interview led to an internal credential compromise and the EIP-7702-enabled drain of hot wallets.

Editorial oversight: Julian Mercer, Chief Editor
Bearish

At a glance

What happened
Binance disclosed that a four-month campaign involving tainted software and a fake job interview enabled attackers to steal $6.34 billion on Oct. 29.
Why it matters
The incident demonstrates vulnerabilities where targeted social engineering combined with EIP-7702 contract delegations can circumvent standard multi-party computation hot wallet safeguards.
Who is affected
Binance and its wallet infrastructure operations.
What's next
Binance plans to conduct an independent third-party security review and establish a security research fund.
Primary source
unchainedcrypto.com: Binance Details Four-Month Path From Tainted Developer Install to $6.34 Billion Drain

Key points

  • Breach began in June via a tampered Homebrew install and escalated through a fake hiring assignment containing zero-day malware in September 1.
  • Attackers drained 18,270 BTC, 233.46M XRP, 970,500 SOL, 44.2M OP, and 2,961.9 ETH using stolen deployment tokens 1.
  • Perpetrators leveraged Ethereum's EIP-7702 to delegate hot wallet permissions, requiring a custom MPC remediation script to stop 1.

Binance published its initial post-incident review detailing the four-month security compromise that culminated in the Oct. 29 theft of roughly $6.34 billion in digital assets 1. According to the exchange, the campaign began in June when a wallet DevOps engineer downloaded a tampered Homebrew package while searching for an artificial intelligence coding tool 1. While Binance detected the initial compromise, replaced the engineer's device, and reset credentials, the attacker retained exposure across the wallet infrastructure team 1.

In September, an attacker contacted a second engineer through a recruitment platform under the guise of an executive interview 1. Following a live video screening, the engineer was directed during an assessment to download a repository containing zero-day malware onto a company-issued computer 1. Binance stated that the malware bypassed endpoint detection tools 1. By Oct. 20, the intruder leveraged the compromised device alongside an internal AI tool to pivot into the machines of the initial engineer and a third team member, ultimately securing a container deployment token 1. The incident follows reports where the FBI blamed North Korea for the multi-billion exploit targeting the platform.

Execution and EIP-7702 Delegation

On Oct. 29, the perpetrator deployed a container and initiated malicious scripts using the compromised third engineer's environment 1. Unauthorized outbound transactions began at 20:05 UTC, draining 233.46 million $XRP alongside approximately 970,500 $SOL, 44.2 million $OP, and 18,270 $BTC across multiple hot wallets 1.

The attacker then used Binance's internal signing service to exploit Ethereum's EIP-7702 standard, granting an external smart contract partial authority over an Ethereum hot wallet across 50 signing transactions 1. Because the infrastructure utilized multi-party computation (MPC), single-key revocations were ineffective, forcing the exchange's engineering team to draft a custom remediation process to cancel the delegations 1. The final unauthorized transfer of 2,961.9 $ETH cleared at 23:56 UTC, and the delegations were fully neutralized at 00:10 UTC on Oct. 30 1.

Binance reported that it has rebuilt the affected wallet infrastructure, decommissioned compromised internal tools, and initiated an independent third-party audit 1. While Binance noted in the report that 98% of impacted assets were replenished by Oct. 31, separate exchange updates reported recovery levels at 90% on Oct. 31 and roughly 95% on Nov. 2, following its previous decision to allocate corporate capital to absorb the losses 1.

Sources

  1. [1] Binance Details Four-Month Path From Tainted Developer Install to $6.34 Billion Drain — unchainedcrypto.com, November 3, 2026

Written by Basis Desk's newsroom system from the primary sources above and machine-verified against them before publication. Market figures marked "at the time of writing" come from live exchange data. Report an error: corrections@basisdesk.news · corrections policy.

Community read
How do you read this story for the assets involved? One vote a day, anonymous.
Be the first to vote

The Daily Brief, in your inbox at 07:00 ET

Five stories, the numbers that moved, what to watch. Three minutes. No hype, no advice, unsubscribe in one click.

Not financial advice. Basis Desk publishes information, not recommendations. Crypto assets are volatile and you can lose what you invest.