Binance Details Multi-Stage Social Engineering Attack Involving Fake Job Interviews and Malware-Laden Repositories That Resulted in $6.3 Billion Theft
Binance has published new details about a complex, multi-month attack that resulted in the theft of $6.3 billion from the cryptocurrency exchange. The incident combined social engineering, malicious code disguised as developer tools, compromised devices, and artificial intelligence.
The attack began when one of the exchange’s engineers was contacted through a job-search platform by an individual posing as a project manager. The engineer then participated in an interview conducted via messenger with a person claiming to be the company’s chief executive. The purported company did not exist; instead, the test assignment repository contained genuine malicious code that infected the engineer’s device.
According to Binance co-chair Richard Teng, the breach cannot be attributed to a single employee error. Attackers employed fake job interviews, malware presented as developer utilities, compromised endpoints, and AI capabilities. The specific role of artificial intelligence in the operation was not disclosed in the report.
The incident first became public on 29 October when Binance reported a possible compromise of an engineer’s laptop. Subsequent investigation revealed additional points of entry. Binance and the FBI have linked the theft to North Korean hackers; North Korea rejects the accusations.
Following the incident, partners assisted in freezing nearly $3 billion. This does not yet constitute recovery of the funds. Binance stated that it has almost fully replenished the stolen assets using corporate resources and two insurance funds. Withdrawals, suspended for nearly two days, began to be restored in stages on Sunday.
The detailed findings were published in a report dated 3 November and were first reported by Bloomberg.
Related articles
Scammer Leverages Unstoppable Domains to Redirect ATOM Transfers via Fake IBC Address
A journalist investigating a Telegram crypto investment pitch discovered an elaborate social engineering scheme that abused Unstoppable Domains. The scammer instructed the target to append -ibc.x to a shared Bybit XRP deposit address, causing the Edge wallet to resolve the string as a Web3 domain pointing to an attacker-controlled Cosmos address. The technique exploited Bybit’s shared deposit infrastructure and the wallet’s native support for Unstoppable Domains records. Analysis of the receiving Cosmos wallet showed 147 incoming ATOM transactions totaling more than 22,000 tokens between July and October. The author subsequently registered several .x and .crypto domains to demonstrate legitimate use of the same resolution mechanism in Edge, Trust Wallet, and OKX Wallet.
Lazarus Group Behind Record $6.3 Billion Binance Hot Wallet Theft: Anatomy and Cassandra Index Impact
Binance reported on October 29, 2026, that attackers stole approximately $6.3 billion in digital assets from its hot wallets, surpassing the previous record of $1.5 billion taken from Bybit in February 2025. The FBI attributed the breach to the TraderTraitor group, widely identified as the North Korean Lazarus Group, which has a history of high-profile operations including the 2014 Sony Pictures attack. The stolen tokens are being converted to Ethereum and laundered through decentralized finance platforms and instant exchangers. Binance covered 90 percent of losses using its SAFU fund, futures insurance reserves, and corporate treasury totaling around $6.34 billion, though this represents replacement of assets rather than recovery from the attackers. Blockchain analysis by TRM Labs linked the operation to prior campaigns against Bybit and KelpDAO through timing patterns and preparatory withdrawals via Tornado Cash. The incident contributed 2.3 percentage points to the Cassandra Index rise to 72, with the largest regional impact observed in East Asia.
Binance Confirms Record $6.3 Billion Crypto Theft via Compromised Hot Wallet and EIP-7702
Binance reported on October 30, 2026 that attackers stole approximately 6.3 billion dollars in cryptocurrency, equivalent to roughly 34 billion reais, marking the largest theft in the sector. The unauthorized transfers occurred on October 29 and were completed in about 20 minutes after the attacker compromised the system authorizing withdrawals. According to TRM Labs, the intruder leveraged Ethereum's EIP-7702 feature to seize control of a hot wallet following at least 36 hours of preparation. Initial reports pointed to a compromised DevOps engineer's laptop as the entry point, but the exchange later stated the incident involved multiple factors and was not a single-click action. Roughly 3 billion dollars have been traced, with Tether freezing over 1.57 billion USDT and Circle blocking more than 800 million USDC. Binance has committed to covering all losses through its SAFU fund and internal capital while cooperating with the FBI and U.S. Secret Service. Attribution remains disputed, with TRM Labs and Chainalysis linking the operation to the TraderTraitor group connected to Lazarus, though Binance has not confirmed the perpetrators.
EIP-7702 Explained: How Ethereum's New Signature Standard Enables Persistent Wallet Delegation Attacks
EIP-7702, activated in May 2025 as part of the Pectra upgrade, allows Externally Owned Accounts to delegate execution to smart contract code while retaining their original address and private key. The mechanism introduces powerful features such as batch operations, gas sponsorship, and limited permissions, but also creates new attack surfaces when users sign malicious delegations. Attackers exploit social engineering to obtain EIP-7702 authorizations that install sweeper contracts capable of draining ETH, ERC-20 tokens, and NFTs without further signatures. Unlike ERC-20 approvals, the delegation persists on-chain until explicitly revoked and can affect future incoming funds across multiple networks when chain_id is set to zero. Research from 2026 identified over 900 malicious delegated accounts linked to more than $2.3 million in confirmed losses. The standard itself is not inherently vulnerable; risk stems from unsafe contract implementations and user errors when signing authorizations. Users are advised to verify delegations via Etherscan or eth_getCode and revoke them through trusted wallet interfaces when necessary.