Binance Details Fake-Interview Attack Behind $6.34B in Affected Crypto Assets

· Original article ↗

Summary

Binance’s preliminary report traces an attack to a fake job interview and compromised developer systems, which attackers used to reach wallet signing operations. The company says $6.34 billion in assets were affected; an independent review is pending.

Key points

  • Binance’s preliminary report traces an initial June 2026 compromise to a tampered Homebrew installation, followed months later by a fake recruitment process targeting another engineer.
  • A malicious coding assignment installed a custom implant that replaced a pyenv component and could execute commands from an attacker-controlled server; Binance identifies no exploited zero-day vulnerability.
  • The attackers used compromised endpoints, stolen credentials, an internal AI tool and a container deployment token to move toward wallet operations; Binance has not explained the AI tool’s role in detail.
  • On October 29, attackers used Binance’s signing service to authorize an EIP-7702 delegation from the Binance14 hot wallet. One of 50 signed authorizations took effect.
  • Binance says about $6.34 billion in assets were affected, about $2.85 billion was frozen or intercepted, and roughly 98% of impacted token assets had been replenished by October 31.
  • Binance says an independent review is forthcoming. Its preliminary report does not provide malware hashes or C2 infrastructure, or explain the signing policies that allowed the authorizations.

Article Details

Attack Vectors
  • In June 2026, a Binance wallet DevOps engineer downloaded a tampered Homebrew installation after searching for an AI coding tool. Binance says its security team detected the anomaly, replaced the device, and rotated related credentials.
  • In September, the adversary allegedly posed as a recruiter, arranged video interviews with an ostensible HR representative and CEO, and persuaded a second engineer to download and run a coding assignment from a repository on a Binance work machine.
  • The assignment created a malicious pyenv component in the Homebrew directory, replaced the legitimate pyenv, rebuilt a symbolic link, and spawned zsh. Binance says the component could execute commands from an attacker-controlled server and used obfuscation and evasion techniques.
  • On October 20, the adversary used Engineer B's compromised computer and an internal AI tool to gain control over two other wallet-team engineers, then discovered a container-deployment permission token on Engineer A's computer.
  • On October 29, the adversary used credentials stolen from Engineer A to access Engineer C's computer, deploy a container, and trigger the script that launched the theft.
  • Binance says the adversary used its signing service to create EIP-7702 authorizations granting an attacker-controlled contract partial execution rights over the Binance14 hot wallet. One of fifty authorizations took effect, enabling unauthorized transfers.
Defensive Notes
  • Binance says it replaced the device affected by the June compromise and rotated related credentials, but the later operation used knowledge about the wallet team gained during that earlier access.
  • After the incident, Binance says it rebuilt the affected internal AI tool and strengthened its access controls.
  • Binance says it is reviewing signing-policy coverage and hot-wallet controls; its preliminary report does not explain what policy permitted the authorizations or why the pattern did not trigger an alert.
  • Binance developed and sent a new on-chain authorization to clear the malicious delegation. It also reported that about US$2.85 billion was frozen or intercepted and roughly 98 percent of impacted token assets had been replenished by October 31.

MITRE ATT&CK

Threat Actors

Products

Countries

Industries

Related Articles