Binance Reveals Fake Interviews and AI Tool Behind $6.34B Security Breach

Binance Reveals Fake Interviews and AI Tool Behind $6.34B Security Breach


Key Highlights

Crypto exchange Binance released an initial report on November 3 detailing the multi-stage attack that led to the theft of approximately $6.34 billion in digital assets on October 29. 

In a detailed X update, the exchange said attackers used fake job interviews to deliver malware in September, later exploited an internal AI tool to reach wallet engineers, and then used stolen credentials to access a wallet signing service and abuse Ethereum’s EIP-7702 authorization mechanism.

The exchange said it would cover the full financial impact of the stolen funds. As of October 31, 98% of the impacted token assets had been replenished and were verifiable on its Proof of Reserves page. About $2.85 billion in assets have been frozen or intercepted. The U.S. Federal Bureau of Investigation has attributed the incident to North Korea.

Attack preparation and initial access

According to Binance, the campaign began months before the October theft. In June, a Wallet DevOps engineer downloaded a tampered Homebrew installation while searching for an AI coding tool. Security staff detected the anomaly, replaced the device and rotated credentials, but the engineer’s role and connections within the wallet infrastructure team were exposed.

In September, a software engineer was contacted through a legitimate job-hunting platform by someone posing as a project director. After a video interview and a second conversation on a messaging app, the engineer was instructed to download an assignment containing a malicious code repository onto a work computer. 

The malware used obfuscation techniques, replaced a legitimate development tool component, and established communication with an external server. Endpoint security tools did not detect the zero-day malware at the time.

On October 20, the attackers used the compromised machine and an internal AI tool to gain control of additional wallet engineers. They obtained a container deployment permission token. On October 29, between 17:15 and 19:56 UTC, they logged into another engineer’s computer, used the stolen credentials, deployed a container, and launched the attack, according to Binance.

How the October 29 hack unfolded

The attacker gained unauthorized access to an internal wallet signing service and initiated transactions outside normal withdrawal processes. 

Between 20:05 and 20:09 UTC, five hot wallets sent 233.46 million XRP to an attacker-controlled address. Additional transfers included approximately 970,500 SOL, 44.2 million OP, and 18,270 BTC.

The attackers then used the signing service to exploit Ethereum’s EIP-7702 mechanism, which allows an account to delegate execution rights to a smart contract without exposing the private key. This enabled continued movement of assets independent of Binance’s normal withdrawal infrastructure. 

Binance said 50 signing transactions were submitted to manipulate account nonces and establish the malicious authorizations.

Because the hot wallet used multi-party computation (MPC), no single private key existed that could immediately revoke the authorizations. Binance had to follow a specialized procedure to address the issue. The final unauthorized transfer of 2,961.9 ETH finalized at 23:56 UTC. At 00:10 UTC on October 30, Binance cleared the EIP-7702 delegation code.

Containment and recovery steps

Binance suspended withdrawals, coordinated with partners to freeze tokens, and rebuilt affected systems. The exchange said it closed the entry points used in the attack, replaced devices, decommissioned credentials, and completed enhanced security scans across employee devices. It also strengthened wallet-service risk controls and expanded AI-based behavioral anomaly detection.

An independent third-party cybersecurity review is underway. The company said it is increasing investment in AI-enabled detection, endpoint protection, and developer-environment security. It is also working on a security research fund focused on AI risks in blockchain environments.

Context for the South Korean market

The detailed findings arrive as South Korean authorities continue reviewing domestic exchange security following the incident. 

The Financial Services Commission held an emergency meeting on November 2 with major local platforms and is examining whether to raise the required cold wallet storage ratio above the current 80 percent minimum.

The Binance report underscores that the breach involved compromised internal systems and authorization processes rather than a simple shortfall in offline storage.

Also Read: Binance Lacks Cyber Insurance for $6.3B Hack — So Who Pays for the Losses?


Disclaimer: The information researched and reported by The Crypto Times is for informational purposes only and is not a substitute for professional financial advice. Investing in crypto assets involves significant risk due to market volatility. Always Do Your Own Research (DYOR) and consult with a qualified Financial Advisor before making any investment decisions.





Leave a Reply

Your email address will not be published. Required fields are marked *