Connect with us

NEWS

Binance Caught a June Breach Then Lost $6.34 Billion

Binance caught a June Homebrew infection on a wallet engineer’s laptop, then still lost $6.34 billion after a fake interview and its own AI tool.

Published

on

Binance lost $6.34 billion on 29 October after a wallet-team breach it had already flagged in June. The exchange replaced that first laptop and rotated the credentials. The names on the wallet team had already left the building.

In initial findings on the October incident, published on 3 November, Binance described a months-long campaign that used a poisoned developer install, a fake job interview, the company’s own internal AI tool and a container token on a third Mac. Users are not paying the bill. About $2.85 billion is frozen. The rest of the hole is being filled from company money.

Binance Caught the June Infection and Still Lost the Wallets

The first foothold, Binance said, came in June 2026. Engineer A, on the Wallet DevOps team, searched for a popular AI coding tool and downloaded a tampered Homebrew installer found via search to put that tool on his machine. Homebrew is the package manager many Mac developers use to install software. Security staff spotted the anomaly, replaced the device and rotated every related credential. Binance called that a proactive step. It also said Engineer A’s role, and the colleagues on the wallet infrastructure team, had already been exposed to the hacker.

That is the part the fake-interview headlines skip. The laptop left the network. The org chart did not.

THE 2026 COUNT BEFORE 29 OCTOBER

  • Blocked cases: Binance says its security team stopped 57 suspected North Korea-linked cyber threat cases during 2026, including fake interviews, poisoned developer tools, bad packages and browser extensions, fake video-call apps and credential theft.
  • First foothold: A Wallet DevOps engineer installed a tampered Homebrew package in June while trying to add an AI coding tool.
  • Company response: The device was replaced and related credentials were rotated after the anomaly was found.
  • What leaked anyway: The engineer’s role and the names of colleagues on the wallet team were already in the attacker’s hands.

A work Mac that can install a search-result package manager, on a team that can deploy wallet containers, is not a side device. Treating the June machine as the whole problem left the people around it as the map for the next stage.

Fake HR, a Fictitious CEO and a Poisoned Assignment

In September, Software Engineer B was contacted through a real job-hunting site by someone posing as a project director. His profile on that site mentioned his Binance experience. The project director set a first-round live video interview with a purported HR representative, then a second round with someone claiming to be CEO of a company that did not exist.

In the first round, Binance said, the HR stand-in shared a social media account that included personal photos and videos, a step the company called more advanced and deceptive than social engineering it had seen before. The second interview ran on a popular chat app. Near the end, Engineer B was told to download an “assignment,” a code repository, onto his work computer. The code ran during setup.

The malware swapped a real developer-tool file for a malicious copy and opened a channel to an attacker-controlled server. Binance said endpoint tools did not flag the 0-day at the time, and the attacker wiped traces, which later slowed the investigation. The swap targeted pyenv, a version manager for Python, under Homebrew’s Cellar path for version 2.8.0. The script created a 3,414-byte pyenv_ file, deleted the valid 3,344-byte pyenv binary, renamed the fake file into its place, removed the copy in /opt/homebrew/bin, created a new symlink and spawned a zsh shell.

This should not have happened, and we apologise for the concern, disruption and uncertainty it caused our users, partners and the wider industry.

Binance, Initial Findings and Response Update, 3 November 2026

The same post is the company’s public account of the path from that assignment to the wallets.

A take-home test on a company laptop is a remote-access request with a job description attached. Binance’s write-up does not say the assignment was reviewed before it ran. The later rebuild list includes tighter device controls, which is the quiet admission that this machine was allowed to install code the security stack had never seen.

How the Attackers Reached the Wallet Signing Service

On 20 October the attacker used Engineer B’s compromised computer and an internal AI tool to take control of Wallet DevOps Engineer A and another wallet software engineer, labelled Engineer C. Binance has not described the AI tool’s product name or the exact control method, and says some technical detail will stay confidential. What it did say is that Engineer A’s computer still held a container deployment permission token, even after the June device swap and credential rotation on that earlier machine.

THREE ENGINEERS ON THE PATH

Person Role What the attackers used
Engineer A Wallet DevOps June Homebrew install exposed the team; a container deployment token was later found on his computer
Engineer B Software engineer September fake interviews; malware on his work computer replaced pyenv and opened a back door
Engineer C Wallet software engineer Login on 29 October; container deployed from this machine with credentials stolen from A

On 29 October, between 17:15 and 19:56 UTC, the attacker logged onto Engineer C’s computer, used credentials stolen from Engineer A, deployed a container and triggered a malicious script. That script, Binance said, reached an internal wallet signing service and started transactions outside the normal withdrawal process. The company has found no evidence that wallet private keys leaked. The signing service itself was instructed to move funds.

A container token on a DevOps laptop is a hot-wallet remote. The June rotation closed one set of logins and left a deploy permission sitting where a later foothold could pick it up.

Fifty On-Chain Authorizations Outran the Off Switch

The drain that customers felt began after that login window, once the signing service was in the attacker’s hands. Binance received an internal alert on large-volume transfers and started investigating while the outflows were still running.

The First Transfers Hit XRP, Solana and Bitcoin

THE 29 OCTOBER CLOCK

  1. 17:15 to 19:56 UTC: The attacker is on Engineer C’s computer, deploys a container with credentials stolen from Engineer A and launches the script against wallet signing.
  2. 20:05 to 20:09 UTC: Five Binance hot wallets send 233.46 million XRP to an attacker-controlled address. Hot wallets on Solana and Optimism send about 970,500 SOL and 44.2 million OP.
  3. After the internal alert: A Binance hot wallet sends 18,270 BTC to an attacker-controlled address.
  4. On Ethereum: The signing service is used to abuse EIP-7702, which lets an account delegate execution rights to a smart contract without exposing a private key. The attackers submit 50 signing transactions to manipulate the account nonce and plant malicious delegations on a Binance hot wallet.
  5. 23:56 UTC: The last unauthorised transfer, 2,961.9 ETH, finalises on-chain. The transaction had been broadcast earlier and was still pending. Binance says no further unauthorised transfers were seen after that.
  6. 00:10 UTC, 30 October: Binance executes a new authorisation from the Binance14 hot wallet to the zero address, clearing the EIP-7702 delegation code.

From the first XRP burst at 20:05 UTC to that last ETH print at 23:56 UTC is 3 hours and 51 minutes.

On-Chain Delegations Kept Moving After the Halt

Binance suspended withdrawals, coordinated freezes and moved to revoke the unauthorised permissions. Suspending withdrawals did not stop every movement, because the EIP-7702 authorisations already existed on-chain and did not need Binance’s normal withdrawal stack. The hot wallet used multi-party computation, so there was no single private key that could sign an immediate revoke. The team had to build and run a special procedure while funds were still leaving. Shutting hot-wallet services did not, by itself, cancel those on-chain delegations.

Co-CEOs Yi and Richard, in a 30 October support note, said the first look had pointed at a compromised laptop and that later work found more points of breach. They also said they had found no evidence of a private-key leak. The 3 November report is the fuller sequence: the laptop was real, and so was the signing-service path that kept moving after the withdrawal halt.

The FBI Names TraderTraitor After Earlier Attempts

On 31 October the FBI said North Korea was responsible for the theft and used the name TraderTraitor for this activity. The bureau, with the U.S. Secret Service and IRS Criminal Investigation, said it had watched those actors converting stolen assets mainly into ether, and expected further laundering through DeFi and instant swap services. FBI San Diego posted the same notice and pointed firms toward a list of addresses to block, including THORNode operators, RPC nodes, instant exchanges and analytics shops.

Elliptic, the blockchain-analytics firm, had already pointed at TraderTraitor and compared the drain with the $1.46 billion theft from Bybit in February 2025, which it said was also tied to that group. In both cases, Elliptic wrote, the cryptography around the wallets held; the people and systems that instruct those wallets did not. Binance’s own 2026 case list, with fraudulent interviews and malware dressed as developer tools, matches that method even before the FBI’s note.

WHAT WE KNOW

  • Company total: Binance puts the impact at $6.34 billion and the frozen or intercepted total at about $2.85 billion, subject to reconciliation and price moves.
  • Attribution: The FBI names North Korea’s TraderTraitor unit; Binance’s 3 November report cites that finding.
  • User losses: Binance says it will absorb the financial impact from the Secure Asset Fund for Users and corporate treasury, and that it has set aside more than 100% of the funds required.

WHAT IS UNCONFIRMED

  • The AI tool: Binance has not named the internal AI product or published how it was used to reach Engineers A and C.
  • The fake firm: The job-site, the fictitious company and the social accounts used in the interviews are not identified.
  • Independent review: Binance has hired outside cybersecurity firms; that review is not finished, and the company says the investigation remains open.

Binance is sharing the initial report, it said, because security improves when the industry learns together. The gaps it is still holding back are the same gaps a copycat would want.

$2.85 Billion Frozen, the Rest Left in Bitcoin and Ether

Stablecoins were the half of the haul that an issuer could still touch. Elliptic’s on-chain freeze and seizure tally matches Binance’s $2.85 billion frozen figure and says almost all of that lock is USDT and USDC. Circle froze 823 million USDC. Tether’s first blacklist landed 37 minutes after stolen USDT reached the attacker’s main Ethereum wallet. Ripple, World Liberty Financial, Paxos and First Digital froze other tokens. The Arbitrum Security Council moved assets out of reach, and Optimism’s governance later moved 44 million OP from an attacker address.

WHAT ISSUERS COULD AND COULD NOT STOP

Asset What moved, per the primary accounts Freeze path
USDT and USDC Elliptic puts stablecoins at $3.46 billion of the stolen funds, including 823 million USDC Issuers blacklisted addresses; this is most of the $2.85 billion freeze
Bitcoin 18,270 BTC left a Binance hot wallet No issuer can freeze native BTC; Elliptic said the coins were split across 19 addresses
Ether and other native coins Last unauthorised print was 2,961.9 ETH at 23:56 UTC; XRP, SOL and OP moved in the first minutes Elliptic says native assets on Bitcoin, the XRP Ledger, Solana and NEAR have no issuer freeze

Before those freezes landed, Elliptic said, the attacker converted hundreds of millions of dollars of stablecoins into ETH and TRX, accepting poor prices for speed. The bitcoin peel-chain and the ether stash are the part no ticker issuer can claw back from a blacklist. Binance’s recovery of user balances does not depend on winning that chase. It depends on the treasury sitting behind SAFU.

Binance Is Paying Users From Its Own Treasury

On 30 October, Yi and Richard said Binance would cover stolen funds through SAFU and corporate treasury, with more than $6.34 billion already set aside and $5 billion held in the same tokens that were taken, including USDC, USDT, BTC, ETH and BNB, about 80% of the impacted amount. The rest was being bought on the market and over the counter. Founder Changpeng Zhao said the firm covered the loss without seeking outside financing.

As of 31 October, Binance said, 98% of the impacted token assets had been replenished and could be checked on its Proof of Reserves page for replenished tokens. The last slice is the illiquid names still being purchased. Withdrawals began reopening on 1 November, starting with bitcoin, according to Elliptic’s incident log. A 3 November support note on Binance’s site said withdrawals were reopening for more assets.

WHAT BINANCE SAYS IT HAD DONE BY 3 NOVEMBER

  • Wallet rebuild: The affected wallet system was rebuilt in a new environment, and wallet-service risk controls were tightened.
  • AI rebuild: The affected internal AI tool was rebuilt and its access controls were strengthened, while the company also expanded AI-based behavioural anomaly detection and said it would put more money into AI-enabled detection, endpoint protection, developer-environment security and behavioural monitoring.
  • People and devices: Affected devices were replaced, credentials and tokens tied to the affected engineers were decommissioned, and enhanced scans were run across all employee devices.
  • Outside review: Independent cybersecurity firms are being hired to validate the findings, and Binance says it is working on a security research fund with AI companies and security firms focused on AI in blockchain environments.

The same report that traces the theft through an internal AI tool is the report that promises more AI on the defensive side. The June detection, the 57 blocked cases and the withdrawal halt were all real. None of them reached a container token, a pyenv binary on a work Mac or an EIP-7702 delegation that no longer needed Binance’s off switch. The last illiquid tokens are still being bought, and the independent review has not yet filed its own account.

Disclaimer: This article is news reporting and analysis of a cryptocurrency-exchange security incident. It is for information only and is not investment, legal or cybersecurity advice. It does not recommend moving, holding or withdrawing digital assets, and it does not rate the safety of any platform. Readers should consult a qualified financial adviser before making decisions about crypto holdings and a qualified information-security professional before changing workplace or wallet controls. Amounts, freeze totals and replenishment figures come from Binance, the FBI and blockchain-analytics firms on the dates named above and can change as tracing, freezes and the independent review continue.

Harry is the editor of IAQABA, an independent publication he owns and runs. A decade in journalism, beginning as a reporter and now as the editor of his own titles, has left him with a clear test for what deserves a story: it has to change what a reader knows or decides, and it has to rest on something he can point to. That rules out recycled press releases, forecasts with no data behind them and rumours that no document supports. It leaves room for a great deal, and the site covers news, business, science and technology alongside sports, entertainment and lifestyle, with travel, auto and gaming given the same standard rather than lighter treatment. Sources are primary wherever possible: the regulator's filing, the company's own statement, the transcript, the dataset, or the product on Harry's desk. Figures are checked before they are published and rechecked if a reader questions them. Mistakes are corrected under a published policy. Readers across the world can reach him directly at support@iaqaba.com.

Click to comment

Leave a Reply

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

Trending