CryptoReal
CASE FILE — Nov 6, 2026

Binance Hot Wallets Compromised in Record-Breaking $6.43 Billion Multi-Chain Breach

On October 28, CZ advised followers to avoid clicking on email links or attachments, cautioning that even trusted sources could be risky.

Less than 24 hours later, Binance experienced a massive breach, as hot wallets spanning 11 blockchains were emptied—Elliptic pegs the losses at $6.43 billion, with TRM Labs noting that the bulk vanished within about twenty minutes.

This figure is more than four times higher than the previous record set by the Bybit hack just 20 months earlier.

The FBI has attributed the attack to the TraderTraitor group, which is linked to North Korea.

Binance initially summarized the suspected breach vector in a single sentence: A DevOps engineer’s compromised laptop may have enabled unauthorized access to a service container, which was then used to process illicit withdrawals.

A November 3 Binance update provided further details: The intrusion began with a fraudulent job interview, the misuse of an internal AI tool, and credentials from one engineer were used via another engineer’s device to deploy a container and execute a malicious script.

Binance reported that the attacker was able to gain illicit access to its internal wallet-signing infrastructure, bypassing standard withdrawal procedures.

The company previously stated that there was no indication of a wallet private-key leak.

Approximately $2.85 billion of the stolen assets were frozen or intercepted, and Binance claims to have replenished most affected assets, reserving sufficient funds to cover all losses.

Binance has now outlined the chain of access leading to its signing service.

Who authorized the signing service to approve these transactions?

Credit: CZ, Elliptic, TRM Labs, Binance, FBI Cyber Branch, Spreek, Officer’s Notes, dogetosh, Jeremy Allaire, Paolo Ardoino, Watcher.Guru, Richard Teng, Ethereum, Blockaid, Limited Supply, banteg, Aave, Chainalysis, Yonhap News Agency

The first public reports came from blockchain observers, not Binance itself.

At 20:32 UTC on October 29, Spreek noticed suspicious activity: A Binance wallet was drained into a new externally owned account, funded through Tornado Cash.

Eight minutes later, Officer’s Notes shared the transaction hash:
0x53bd38b816c23e74134786c29a8c18d792777998a3b9326047b583100e88e2f3

This transaction transferred 167,464 ETH, 1.615 billion USDT, and numerous other tokens, from the hot wallet labeled Binance 14 to a single address.

Destination Address:
0x5227f603C1eE34CE3C06eFe6477003BDfCCB2f8c

By 20:46 UTC, dogetoshi estimated the cross-chain total at nearly $3.5 billion.

Other blockchains were hit first. Binance's November 3 report details that five hot wallets transferred 233.46 million XRP to an attacker-controlled address between 20:05 and 20:09 UTC, with additional outflows of about 970,500 SOL and 44.2 million OP from Solana and Optimism wallets.

An internal alert at Binance, triggered by unusually large transfers, initiated an investigation.

At 21:15 UTC, CZ acknowledged the likelihood of a hack, expressing gratitude to Tether and Circle for freezing assets and assuring users that all funds would be restored.

At 21:18 UTC, Circle’s Jeremy Allaire confirmed that $800 million in USDC was frozen in cooperation with authorities, followed closely by Tether’s Paolo Ardoino reporting over $1.567 billion in USDT frozen.

At 21:29 UTC, Binance formally acknowledged "reports of a potential security issue."

At 21:42 UTC, Watcher.Guru published an early breakdown of losses: $1.45 billion in BTC, $875 million in ETH, $1.57 billion in USDT, $823 million in USDC, and hundreds of millions more in additional assets.

At 22:15 UTC, Binance announced that withdrawals would resume once the security issue was resolved.

In other words, withdrawals were suspended.

At 02:23 UTC on October 30, Binance published its official estimate: Roughly $6.3 billion was affected, with around $3 billion frozen on-chain. The company committed to covering all losses via SAFU and company reserves.

Their preliminary statement was concise: A compromised laptop belonging to a DevOps engineer might have enabled unauthorized withdrawals by granting access to a service container. Binance reaffirmed that there was no evidence of a private-key leak.

At this early stage, details about how access led to transaction authorization were missing. Binance would not clarify the full technical path until its November 3 release.

Having access to a withdrawal service does not automatically grant spending authority.

What connected that access to actual permission?

Permission Escalation

Binance’s explanation evolved in phases.

The initial account focused on a laptop and a service container.

On October 30, co-CEO Richard Teng emphasized that the attacker "did not simply use one engineer's permissions."

Later, Teng explained that “additional breach points were uncovered,” and that the attacker used "a self-destruct mechanism that erased evidence as they progressed, complicating the investigation.”

Teng also stated: “The attacker used a known multi-signature protocol EIP-7702, to obtain on-chain execution approval over a hot wallet.”

EIP-7702 is not a multisignature protocol; it allows an externally owned Ethereum account to delegate code execution, without requiring multiple signatures itself.

According to the specification: “The code specified by an authorization has unrestricted access to the account and must always be closely audited by the wallet.”

Teng’s statement was significant: “That delegation did not pass through our normal approval controls.”

On November 3, Binance published a more detailed account, revealing that the compromised laptop was just one stop on a broader path.

Binance now contends that a fraudulent recruitment process led one engineer to download malicious code. The attacker then used an internal AI tool to gain further access, logging onto another engineer’s computer and using stolen credentials from a Wallet DevOps engineer to deploy a container and activate a harmful script.

Three engineers’ devices and credentials were compromised, though Binance clarifies this does not mean all three were independently phished or involved in the unauthorized transfers. One breach point enabled escalation into additional privileges.

Engineer A, identified in Binance’s report, had previously downloaded a tampered Homebrew installer in June, after searching for an AI coding tool. The security team detected the issue, replaced the device, and rotated credentials. The breach highlighted the engineer’s role and teammates, but it is unclear if the June compromise continued into October.

The September breach involved social engineering: Software Engineer B was contacted through a legitimate job platform by someone impersonating a project director. During the initial video interview, a fake HR representative shared personal media to build trust.

In round two, held over a social chat app with someone posing as a fictitious CEO, Engineer B was asked to download and run an “assignment” containing malicious code.

Binance reports the malware swapped a legitimate development tool with a compromised version to run attacker commands and communicate with an external server, specifically replacing pyenv at /opt/homebrew/Cellar/pyenv/2.8.0/libexec/.

The malware evaded existing endpoint protection solutions.

Binance described it as “0-day malware”, though the report does not specify an exploited vulnerability.

By October 20, Binance says the attacker was using the internal AI tool to expand access beyond Engineer B. They next discovered a token on Engineer A’s computer that permitted container deployment.

The AI tool's precise impact remains unspecified. While Binance states it was used to “gain control over” two engineers, it does not detail the scope of this access or how the AI tool facilitated it.

The initial social engineering provided access, while the AI tool facilitated lateral movement. By October 29, stolen credentials were used for container deployment from a third engineer’s computer. The attacker also gained unauthorized access to the wallet signing service, which they used to initiate transfers and set up malicious EIP-7702 delegations.

The report leaves a crucial gap: it does not explain exactly how deployment access became signing authority, or why the signing service processed the malicious requests.

Binance’s November 3 update does not confirm if any of the three engineers were directly involved in the hot wallet’s MPC signing scheme. It focuses on compromised endpoints, without clarifying who possessed the signing shares.

The report dates Engineer B’s compromise to September, with the attacker leveraging access on October 20.

According to the latest figures, 57 North Korea-linked attacks were detected and stopped in 2026, though the timeline of Binance's discovery of Engineer B's compromise remains unspecified.

TRM Labs notes that Binance wallets on several chains sent assets to attacker-controlled addresses via validly signed transfers, despite utilizing various signing methods.

TRM concluded the attacker most likely gained the ability to have Binance’s hot wallet system “sign transactions of its choosing across chains.”

Binance’s own statements now reflect a similar assessment.

Elliptic's analysis also points to abuse of Binance’s signing framework, not simple theft of private keys.

Blockaid described an Ethereum transaction with 50 EIP-7702 authorizations, only one of which matched the current nonce for Binance 14, but did not clarify how the attacker acquired those signatures.

Bitcoin transfers, however, cannot be explained by EIP-7702. TRM Labs estimates that about 18,270 BTC were withdrawn from Binance.

The destination address’s BTC transaction history includes multiple deposits from a wallet labeled “Binance 4”:
bc1q0mtc2f5agpkvlq6hhahmfr3hlr55kyfjhl2mnm

[EIP-7702 alters Ethereum execution permissions, not Bitcoin. The explanation covers Ethereum, but not how the attacker secured valid BTC signatures.

In its October 30 update, Binance reiterated that no wallet private-key leak was found.

A valid signature does not necessarily mean a private key compromise: The attacker may have tricked Binance’s internal systems into signing the transactions.

Binance’s reports map the attacker’s access path, but do not clarify why the signing service ultimately permitted the withdrawals.

The November 3 update does not explain how Engineer A's credentials functioned on Engineer C’s machine, nor does it specify what permissions the deployed container inherited. Details about which checks—if any—were in place between deployment and access to the signing service remain absent, as do specifics regarding cross-chain signing authorizations.

Binance has stated that some technical information will remain confidential and that security firms are reviewing its investigation, though no external validators have been named and no independent assessment has been released to date.

The deployment step is mentioned, but it does not explain the conditions under which the signing service would accept requests.

Binance indicates that malicious on-chain authorizations worked independently of routine withdrawal systems.

How did a single delegation allow Binance 14 to keep processing withdrawal requests after the global pause?

EIP-7702 and the Persistent Delegation

Binance 14 was compromised using EIP-7702, which enabled continued unauthorized activity for close to four hours.

Following Ethereum’s Pectra upgrade in May 2025, wallets could sign delegations authorizing external code execution.

The delegation transaction includes the chain ID, the address of the code to execute, and the account’s nonce, all signed by the account.

Once installed, the delegation causes all calls to execute the new code in the context of that account. The process is only reversed by an explicit on-chain clearing or replacement authorization.

The attacker’s operator wallet was initially funded via three Tornado Cash withdrawals of about 0.1 ETH each, starting October 28.
Operator Wallet: 0x7C8601d4645b93cea45F71e118A729332e6B5CA0

On October 29, the same address deployed an initial sweeper contract, then tested type-4 multi-authorization transactions on test wallets that afternoon.

At 15:59 UTC, about four hours before the main event, the final sweeper contract was deployed:
0x63e842B054Bd624a465454D533C33F573e9c6fAe

This contract is not verified on Etherscan.

banteg reconstructed the contract in Solidity and confirmed a byte-for-byte match with the deployed code (excluding metadata).

The only authorized caller in the reconstructed code is the operator wallet:
0x7C8601d4645b93cea45F71e118A729332e6B5CA0

The sweeper targeted Binance 14:
0x28C6c06298d514Db089934071355E5743bf21d60

Binance 14 was highly active, sending multiple withdrawals per minute, causing its nonce to increment rapidly. Any delegation had to be signed for the current nonce to avoid becoming invalid before execution.

At 20:20:59 UTC, in Ethereum block 26,300,753, the operator sent a type-4 transaction containing 50 EIP-7702 authorizations signed by Binance 14, spanning consecutive nonces.

Binance’s November 3 report refers to this as “50 signing transactions,” designed to manipulate the account nonce and cement the delegation.

On-chain evidence shows a single type-4 transaction with 50 signed authorizations from Binance 14.

Delegation Transaction:
0xad99264d5532ae0dd04b2004eebda05f25657e70dacb764f7ac8d4ccd051298b

The reconstruction ties the attack to compromised access to an internal Binance service, but does not specify how the 50 signatures were acquired.

Binance 14 is identified as the signing account on-chain, but the actual signing process remains opaque.

Binance 14 was now delegated to run the sweeper contract’s code.

Three minutes and 24 seconds later, at 20:24:23 UTC, the operator initiated the main sweep via a separate transaction.

[This transaction drained 167,464 ETH, 1.615 billion USDT, 62.6 million RLUSD, and around 60 additional tokens to the main receiving wallet.]

Receiving Wallet: 0x5227f603C1eE34CE3C06eFe6477003BDfCCB2f8c

Sums referenced in this case file

Main Sweep: 0x53bd38b816c23e74134786c29a8c18d792777998a3b9326047b583100e88e2f3

The reconstructed contract logic shows that it iterates through each token, transferring the full balance if available, and logs failures without reverting the entire batch.

**The main sweep transaction recorded a SweepItemFailed event for a reverted token transfer, while 63 others succeeded.

When native ETH is included, the contract retains 1 ETH in the wallet, transferring the rest. This behavior does not apply to the separate withdrawETH function.

Another function, callExecute, restricted to the operator, allowed arbitrary contract calls in Binance 14’s context.

Binance’s report describes the EIP-7702 delegation as conferring "partial execution rights" over Binance 14.

The EIP-7702 standard itself does not impose spending limits; restrictions must be defined in the delegated code or external access controls.

The reconstructed contract allowed the operator to sweep tokens, withdraw ETH, and invoke external execute functions, depending on the called contract’s own permission logic.

Limited Supply’s on-chain analysis found that Binance 14 owned the smart-contract wallet Binance Hot Wallet 34:
0xEe7aE85f2Fe2239E27D9c1E23fFFe168D63b4055

Ownership can be verified via Contract → Read as Proxy → getNativeOwner, which returns Binance 14’s address:
0x28C6c06298d514Db089934071355E5743bf21d60

Limited Supply’s reconstruction, "One signature, four hours, $6 billion: What the chain shows about the Binance hot-wallet drain," shows Hot Wallet 34 accepted calls from its owner, Binance 14. The delegation enabled the attacker to make these calls as Binance 14 itself, so Hot Wallet 34 did not detect anything unusual.

Transfers of 780 million USDC at 20:41:23 UTC and 43 million USDC at 20:59:47 UTC were traced to the attacker’s receiving wallet.

The EIP-7702 delegation modified Binance 14’s behavior without altering the ownership recognized by Hot Wallet 34.

Limited Supply’s analysis indicates the malicious delegation remained in place until 00:10:35 UTC on October 30, lasting 3 hours, 49 minutes, and 36 seconds.

The delegation persisted after the primary sweep. Additional outgoing transactions from Binance 14 were identified during this window.

At 21:04 UTC, about 1,700 ETH, 3.9 million USDT, and other tokens were swept.

Sweep Transaction:
0x31c4c9fe287d54fb9d3b79980477a8c793a11f774b98d0a9a92de1dad888a91d

At 21:44 UTC, another sweep transferred about 200 million USDT and 370 ETH, plus additional tokens.

Sweep Transaction:
0x55ba4dabc41b468e580751373ad31acdee6f5ba398682df2c93e5a8340870556

At 22:39 UTC, numerous altcoins, including POL, GRT, and SKY, were moved to a second destination.

Sweep Transaction:
0x4a4aed833556814c16fe176fc8abc70ce124eadc73da3bcdf42a67ef44f9ad6b

Second receiving wallet:
0xA97bF7836F8A08F9Ed91D41453D371493FAE8d10

At 23:55:47 UTC, 2,961.99 ETH arrived in Binance 14. A sweep of approximately 2,961.9 ETH to this second address followed one minute later.

Binance’s report identifies this as the final unauthorized transfer, noting the transaction was broadcast earlier and finalized at 23:56 UTC; no initial broadcast timestamp was provided. No further unauthorized transfers were seen.

Incoming ETH Deposit:
0xc1f0fdb94fb909e3f12aa345e81c05d4adb0ea2d3243e844920d62a2936f4ae0

Final Sweep Transaction:
0x4395d51dc3f3c51230329efc3548f74edbced353ff3f795c517cc57fa650f89b

Binance states that while withdrawal suspension and hot-wallet shutdowns were enacted as containment, these actions did not invalidate the existing on-chain delegations. The delegation remained active until a separate on-chain transaction revoked it.

The withdrawal system was halted, but the smart contract authorization persisted.

Tether blacklisted Binance 14 for USDT at 22:06 UTC.

Circle blacklisted the address for USDC at 23:53.

Binance 14 still shows a balance of $1.35 million in USDT and a total of $2.18 million in tokens across 231 assets.

Activity continued until the delegation was explicitly removed.

During the period between the breach and the fix, Binance’s internal system signed 94 more transactions from Binance 14—including withdrawals and smart-account operations—per Limited Supply’s analysis. During that time, at least 133 ETH deposits totaling about 5,181 ETH were made from external addresses, along with further token deposits.

The EIP-7702 delegation was cleared by setting it to the zero address in this transaction.

Delegation-clearing Transaction:
0xafbf94c92a8d749988411669fa14d4f8866d9b4420b4ebd299f28e958dac7209

The delegation lasted 3 hours, 49 minutes, and 36 seconds on Ethereum. This measures only the duration of the on-chain permission, not the attacker’s access to Binance’s signing infrastructure.

Because Binance’s hot wallet used Multi-Party Computation (MPC), there was no single private key to immediately revoke the delegation. The team had to implement a custom revocation process, lengthening the response time.

EIP-7702 requires a valid signed authorization targeting the zero address to clear the delegation; the standard does not dictate how an MPC system should produce such a signature.

According to Binance, the attacker established malicious EIP-7702 delegations through its internal signing service earlier that evening. The MPC arrangement delayed revocation, but Binance did not provide specifics on the custom process or why existing infrastructure was insufficient.

Binance is re-evaluating its incident response, signing policies, and hot-wallet controls.

The breach spanned multiple blockchains. BTC, XRP, SOL, and OP were also transferred to attacker-controlled addresses.

The EIP-7702 delegation was one of several attack vectors. Binance attributes outflows of BTC, XRP, SOL, and OP to unauthorized access to its internal signing systems, used to process transfers outside its standard withdrawal workflow.

[According to the November 3 report, five hot wallets sent 233.46 million XRP to a single address between 20:05 and 20:09 UTC. Further unauthorized transfers included approximately 970,500 SOL, 44.2 million OP, and 18,270 BTC. The company believes these were made possible by unauthorized access to its internal signing service, bypassing regular controls.

On Ethereum, Binance 16’s sweep followed Binance 14’s by just 24 seconds. Blockaid details that 28,005.6 ETH, 55.7 million USDT, 25.9 million RLUSD, 84.5 WBTC, and additional tokens were transferred to the same destination.

Binance 16 Wallet:
0xDFd5293D8e347dFe59E90eFd55b2956a1343963d

ETH Transfer Transaction:
0x51f263fa50966df6bbd7f8c6e6e99e3791c94444f7c4343b2fef1ee2d62fd39f

USDT Transfer Transaction:
0xd4e08d3ef0cb02a75922913c61984fbf7fe4bbc4b95324735ef27f908fd6c49c

RLUSD Transfer Transaction:
0x2e1001627db976a77c5ce2feddef516f2c729b1de101c25d0d5af7699e5ffeb3

WBTC Transfer Transaction:
0x2c45d7874dd60a5f1fa6e400933378efbc96b66abb988b8e3ed9bc010e6f260b

On Arbitrum, Blockaid’s tracker shows that between 20:30 and 20:33 UTC on October 29, four Binance hot wallets sent about 74.56 million ARB and 8,426 ETH to the collection address.

Arbitrum Receiving Address:
0x5227f603C1eE34CE3C06eFe6477003BDfCCB2f8c

On Avalanche, Blockaid’s tracker recorded the transfers between 20:33 and 20:35 UTC. Four hot wallets sent roughly 1.81 million AVAX and 8.41 million USDT to the same address, matching Blockaid's written totals.

Avalanche Receiving Address:
0x5227f603C1eE34CE3C06eFe6477003BDfCCB2f8c

Blockaid distinguishes these from the EIP-7702-based attack on Binance 14: “None of these wallets had smart contract code. Each transfer was an ordinary transaction signed by the wallet’s own key and occurred during normal withdrawals.”

Still, some of the stolen assets were quickly frozen. Blockaid notes that Tether and Circle froze about $1.8 billion at the main collection address within 40 minutes of the first sweep.

Would the attacker or the blacklist react faster?

Asset Freezes and Conversion Tactics

Exfiltrating the assets was just the start; converting them before a freeze could be imposed was the next challenge.

Elliptic estimates the loss at $6.43 billion, including $3.46 billion in stablecoins (54% of the total).

This gave issuers a window to block large portions of the funds before they could be converted to assets beyond their control, such as ETH, TRX, or BTC.

Circle managed to freeze all $823 million of the stolen USDC before any was swapped, according to Elliptic.

On Ethereum, Tether imposed a freeze 37 minutes after the USDT hit the attacker’s wallet.

Before the freezes, the attacker managed to convert $434 million USDT to ETH via DEXs and another $234 million to TRX on Tron.

Elliptic calculates that about $786 million in stablecoins were swapped before blacklists took effect.

The haste came at a cost. TRM Labs tracked roughly 325 million USDT traded via UniswapX and other intent-based protocols for approximately 122,300 ETH, reflecting an implied price of $2,650 per ETH, while the market rate was around $2,300–$2,350.

The attacker accepted over 10% in slippage to evade freezes.

Some assets were leveraged rather than sold directly.

Aave reports that between 20:58 and 21:01 UTC on October 29, a wallet associated with the attacker deposited 60 million USDT on Aave V3 and borrowed 19,762 WETH, then valued at about $44.6 million.

Aave Borrowing Wallet:
0x8d53903625b8e839b9DF4bd28B0EFb1CD6b8639A

The stablecoins became collateral for the borrowed assets. Aave’s team stated the position was over-collateralized and did not threaten other users.

Aave’s guardians later froze new deposits and borrowing on the affected markets, though repayment, withdrawal, and liquidation were still possible. The freeze limited further action but did not seize funds already borrowed.

There was market risk for the attacker as well: Part of the position was liquidated on November 4 after ETH’s price rose, with a liquidator repaying about 9,900 ETH and receiving roughly 24 million USDT as collateral.

The rapid response resulted in a significant share of funds being blocked. Elliptic calculates about $2.85 billion frozen or seized, or 44%, compared to only 3% after the Bybit incident.

Binance’s November 3 update matches this figure, adding that the total is subject to reconciliation and market fluctuations.

However, frozen does not mean recovered. Blacklists stop further transfers, but do not restore funds to victims by default. Emergency network actions, like those taken by Arbitrum’s Security Council, can move assets to safety.

TRM Labs reports that Arbitrum’s Security Council used emergency powers to secure 8,426 ETH and 74.6 million ARB, about $30 million, from attacker control.

These measures are containment, not restitution.

Restoring customer assets is a separate process. Binance has pledged to cover the losses, setting aside more than 100% of the required funds.

By October 31, Binance reported 98% of affected token assets had been replenished, with the remainder, which were less liquid, still being acquired.

These are replacement measures by Binance, not actual recovery from the attacker.

The laundering phase began swiftly. In the first 3.5 days, Elliptic tracked about 12,000 wallets across 11 blockchains and over 40,000 transactions, averaging one new wallet every 25 seconds.

Tron became the primary early route, with around 1,300 attacker wallet transactions in one hour at peak on October 31. The funds were split and bridged to other chains.

This velocity led to speculation about AI involvement, but Elliptic found evidence of conventional automation: fixed schedules, set amounts, and stepwise introduction of new methods. No direct indication of AI-based decision-making was observed.

Chainalysis separately identified repeated patterns where addresses received exactly 1 TRX, then additional funds, before forwarding them, with some addresses reused.

Coincidentally, Chainalysis disclosed its own security incident on October 30, the same day it published the Binance investigation, later reporting exposed credentials and service outages, but stated this was unrelated to the Binance hack.

On October 31, the FBI attributed the theft to North Korea’s TraderTraitor campaign.

Kim Yo Jong, sister of North Korean leader Kim Jong Un, denied FBI’s claims in a KCNA statement: “It is a grave political provocation against the DPRK that the U.S. misleads the international public opinion as if all the cyber crimes in different parts of the world are our deeds.” She also suggested possible U.S. involvement, without providing evidence, referencing hypothetical plans to use confiscated cryptocurrency as a strategic reserve.

Elliptic reports that about $16 million reached addresses also implicated in the September Bitget exploit.

However, attribution does not mean all funds remain under attacker control: Elliptic warns that some stolen assets may already have entered broader money-laundering networks, which blockchain analysis alone cannot confirm.

As of Elliptic’s November 5 update at 09:15 UTC, roughly $3.35 billion remained in addresses linked to the theft.

The original 18,270 stolen BTC is spread across 19 addresses and remains unmoved.

Other assets are consolidating into bitcoin: Around 900 BTC, valued at $72 million, was accumulated by swapping stolen SOL, Tron, and ETH.

Some proceeds entered bitcoin coinjoins and Privacy Cash pools on Ethereum and Solana.

However, conversion is not equivalent to cashing out.

Elliptic believes that only a negligible fraction has been liquidated. Most of the funds remain on-chain, not yet realized as spendable currency. Final cash-out would require a counterparty, potentially an OTC broker or exchange.

Elliptic anticipates the ETH will be converted to BTC in small increments, then sold via OTC desks over months.

The blacklist may have stopped stablecoin conversion, but the next battle will be at the cash-out phase.

Who will intercept the final exit?

A combination of targeted social engineering, use of an internal AI tool, and misused deployment credentials formed the attack chain now described by Binance.

The heist, linked by the FBI to North Korea’s TraderTraitor group, resulted in an estimated $6.43 billion in losses across 11 blockchains, according to Elliptic.

Binance’s November 3 account covers a compromise involving three engineers’ devices and credentials. It also confirms that suspending withdrawals and halting hot wallet services did not immediately revoke malicious on-chain permissions.

Binance 14’s delegation remained in effect until 00:10 UTC the next day.

It remains Binance’s narrative. The company reports that independent cybersecurity firms are reviewing its findings, but some technical specifics are still confidential.

Its public explanation omits details on the controls applied to attacker requests. The company cites its MPC setup for the delay in revoking permissions but has not clarified why a specialized process was necessary.

Financial remediation has progressed further than public technical clarification.

Binance says around $2.85 billion in assets were frozen or blocked and that 98% of lost tokens were replenished by October 31, with reserves set aside to cover the rest.

But asset replacement does not equate to fund recovery: Elliptic’s November 5 review still finds roughly $3.35 billion in addresses linked to the theft.

Some of the exploit’s entry points are familiar: Engineer A installed a tampered Homebrew after searching for an AI coding tool.

Engineer B ran a suspicious interview “assignment” on a work computer, launching the malicious code.

These initial lapses opened the door; the key unknown is what internal controls, if any, stood between access and the ability to authorize multi-billion-dollar transfers.

A valid signature proves cryptographic authorization, not necessarily the owner’s intent.

Binance states that the attacker leveraged stolen deployment credentials to execute the breach.

However, the path from access to transaction signatures has yet to be fully detailed.

Elsewhere, another engineer is likely being lured to a staged interview.

What assets might be at stake next?

BinanceOperational Security
Investigation alerts

Get new scam files the moment we publish them — usually 2–3 emails a week.

Enter a valid email address.

No spam, unsubscribe anytime. We never sell your data. Crypto assets are volatile and high-risk; nothing here is financial advice.

You're on the list. Watch your inbox for the next scam file.