Binance hack: what happened and how to prevent fraud

On October 29, 2026, attackers stole approximately US$6.3 to 6.4 billion in crypto assets from Binance.com's hot wallets. It is the largest cryptocurrency theft on record, about four times the 2025 Bybit hack (US$1.5 billion). Binance states that user funds are safe and that it will cover all losses. Blockchain analytics firms attribute the attack to TraderTraitor, a North Korean unit. To avoid the fraud that typically follows such an incident, never share codes or seed phrases, and verify everything through official channels.

Data

Status

Amount

Between US$6.3 and 6.4 billion, depending on the source

Entry point, according to Binance

Compromised laptop of a DevOps engineer and "additional breach points"

Attribution

TraderTraitor (Lazarus Group), according to TRM Labs and Chainalysis. Binance has not attributed the attack

Frozen funds

Between US$2.7 and 3 billion, primarily stablecoins

Users

Binance ensures they will not lose funds. Withdrawals temporarily suspended

What happened in the Binance hack?

Binance announced on the evening of October 29 that it was investigating a security incident. According to Chainalysis, funds began leaving the hot wallets around 4:20 p.m. (Eastern Time). TRM Labs indicates that the attacker moved about US$6.36 billion across ten blockchains, most of it in about 20 minutes.

On Ethereum, the attacker used an operational wallet funded through Tornado Cash. Using valid signed authorizations, they caused a Binance hot wallet to execute attacker-controlled code and swept its assets. On other chains, the affected wallets sent funds via seemingly normal signed transfers.

Binance suspended withdrawals and deposits, later clarifying that deposits were not affected. It estimates resuming withdrawals in about 45 hours and set aside more than US$6.3 billion to cover the incident using the SAFU fund and company funds.

How did the attackers get in?

Binance's account is preliminary. Its co-CEO, Richard Teng, stated that the attack may have begun with the compromised laptop of a DevOps engineer, which provided access to a service container from which unauthorized withdrawals were sent. He also clarified that it was not a "one-click" action and that no evidence of leaked private keys was found. The company promised a technical post-mortem report once the investigation concludes.

An Illumio analyst cited by the BBC suggested that an engineer might have been tricked into running a test, which could have introduced malware to their machine. This is a third-party hypothesis, not a finding confirmed by Binance.

Who is behind the attack?

TRM Labs and Chainalysis attribute it to TraderTraitor, a unit linked to North Korea also known as Lazarus Group or APT38. Chainalysis states it has "high confidence." Its strongest evidence is that the stolen funds were mixed in real time with those from the Bitget hack last month, which had already been attributed to North Korean actors. This attribution comes from private firms, not an official conclusion by authorities.

What does the hack mean for cryptocurrencies and traditional banking?

This section is analysis, not facts confirmed by Binance.

The hack reopens a fundamental debate. Cryptocurrencies were born from the idea of eliminating intermediaries and letting individuals control their own assets. Traditional banking was built on a different logic: a regulated institution that custodies money, answers to its clients, and is subject to oversight. Binance, a centralized exchange, sits in the middle: it concentrates custody like a bank, but operates under the rules of a much younger industry.

  • Setback for trust in centralized custody. According to Binance, the entry point was the computer of an employee with production access. Based on what has been reported so far, the problem was not a flaw in the blockchains, but rather the operational security of the custodian. This puts the question of who holds the assets and with what controls back in the spotlight.


  • The promise of crypto still stands, but with nuances. The coordinated response from stablecoin issuers, analytics firms, and law enforcement froze nearly half of the stolen funds within hours. However, according to BleepingComputer, the attacker still controls around US$2.4 billion that cannot be frozen. Traceability helps, but transaction irreversibility remains a risk.


  • Accountability shifts hands. Binance says it will cover all losses using the SAFU fund and its own capital. In traditional banking, liability to customers is largely defined by regulation. In the crypto world, it depends more on each company's solvency and discretion.


  • Disruption and recovery. Withdrawals suspended, Binance Alpha trading temporarily halted, and an updated proof of reserves pending. The BBC reports that tracing the money could take months.


  • Regulatory and regional attention. The UK regulator (FCA) said it was in contact with Binance. BBC Mundo reports an impact in Latin America. Binance.US stated it was not affected.

What are the implications and setbacks?

This section is analysis, not facts confirmed by Binance.

  • The weak link was operational. According to Binance, entry occurred via the device of an employee with production access. The security of devices, identities, and engineering environments matters just as much as key custody.


  • The coordinated response worked partially. Stablecoin issuers, analytics firms, and law enforcement froze nearly half of the stolen funds within hours. According to BleepingComputer, the attacker still controls around US$2.4 billion that cannot be frozen.


  • Disruption and trust. Withdrawals suspended, Binance Alpha trading temporarily halted, and an updated proof of reserves pending.


  • Slow recovery. The BBC reports that tracing the money could take months. Chainalysis observes automated laundering, with thousands of transactions in a short period of time.


  • Regulatory and regional attention. The UK regulator (FCA) said it was in contact with Binance. BBC Mundo reports an impact in Latin America. Binance.US stated it was not affected.

Frequently asked questions

Did Binance users lose money?

According to Binance, user funds are safe and the company will cover all losses. Withdrawals are temporarily suspended.

How much was stolen?

Binance estimates around US$6.3 billion. TRM Labs reports US$6.36 billion and Chainalysis US$6.4 billion. Figures vary depending on the source and the timing of the measurement.

Were private keys leaked?

Binance states that so far it has found no evidence of this. The investigation is ongoing.

Who is TraderTraitor?

It is a hacker unit linked to North Korea, also known as Lazarus Group or APT38.

Is Binance.US affected?

Binance.US reported that it was not affected. The incident occurred on Binance.com.

How to prevent fraud after a hack like Binance's?

The case demonstrates that attackers reach money through people and access permissions. Based on general security experience, a public incident of this scale is often used as bait to scam customers with fake refunds, fake support agents, and cloned sites. This is a known tactic, not a confirmed fact regarding this specific incident.

What financial institutions should do

  1. Communicate only through official channels and warn customers about what will never be requested: passwords, codes, or seed phrases.

  2. Monitor and take down spoofed domains and fake profiles impersonating the institution.

  3. Implement strong authentication and delays for payments to new payees and unusual high-value transfers.

  4. Monitor transactions in real time with behavioral signals, ensuring that a valid authorization alone is not enough to drain an account.

  5. Train support staff to verify identity and escalate suspicious contacts, and share indicators with peers, issuers, and authorities.

  6. Protect internal devices: device management, least privilege, temporary access, and hardware security keys for anyone interacting with production.

What individuals should do

  • Never share codes or seed phrases with anyone.

  • Type the official address directly into the browser instead of opening links from messages.

  • Return calls using the number listed on the official website.

  • Be wary of urgency and promises of recovering funds.

  • If you shared any information, change your passwords and report it immediately.

60-second checklist before taking action

Question

If the answer is yes

Did they reach out to me first?

Stop

Are they asking me for a code or a password?

Stop

Is there urgency or a threat?

Stop

Did I arrive via a link rather than the official address?

Stop

If any answer is yes, stop and verify through the official channel.

The lesson for the financial sector

Security works in layers: devices, privileges, transaction controls, rapid response, and customer education. None replaces the others. Institutions that explain this clearly and promptly preserve trust when an incident occurs. Bankingly publishes this analysis to help financial institutions across Latin America review their defenses against digital fraud. In security, trust is built before the incident occurs.

Sources