Binance reveals months-long North Korean campaign behind record $6.3B crypto heist

3 min read
Source: The Register
Binance reveals months-long North Korean campaign behind record $6.3B crypto heist
Photo: The Register
TL;DR

Binance disclosed that a record $6.3 billion theft resulted from a sophisticated, multi-stage attack by North Korean hackers, not a single breach. The campaign began in June with a supply chain attack involving a malicious Homebrew installer and continued in September with fake job interviews that led an engineer to download malware. Attackers then exploited internal AI tools to compromise additional staff and drain wallet systems on October 29. The FBI attributes the heist to the Lazarus Group-linked TraderTraitor, while North Korea denies involvement. Binance has replenished 98% of affected assets and restored withdrawals.

Key points

  • The attack was a multi-stage campaign spanning June to October 2026, involving social engineering, malware, and internal tool abuse.
  • In June, an engineer downloaded a malicious Homebrew installer via an ad, exposing wallet infrastructure team details to attackers.
  • In September, a second engineer was targeted via a fake job interview on a professional networking platform, leading to malware installation on his work computer.
  • On October 20, attackers used the compromised device and an internal AI tool to access the computers of two other wallet engineers.
  • On October 29, stolen credentials were used to deploy a malicious container and steal funds in approximately 20 minutes.
  • Binance has rebuilt compromised systems, rotated credentials, and replenished 98% of the stolen assets using its Secure Asset Fund for Users.

Background

This incident follows a series of earlier reports in late October and early November 2026 regarding the initial discovery of the breach, the suspension and resumption of withdrawals, and the FBI's attribution of the attack to North Korean actors. Previous coverage highlighted the scale of the theft and the immediate financial response by Binance, while the current disclosure provides the technical and social engineering details of the attack vector.

How outlets are covering it

The Register and The Washington Post emphasize the sophistication of the social engineering tactics, noting that the fake interview included sharing personal social media content to build trust, a method described as more advanced than typical phishing. Fortune highlights the specific use of a professional networking platform for the initial contact and notes that while AI tools were abused, the core breach relied on conventional phishing and malware. Yahoo Finance focuses on the executive response, quoting co-CEO Richard Teng on the complexity of the attack and the self-destruct mechanisms used by hackers, as well as founder Changpeng Zhao's assurance that user funds are covered. All sources agree on the multi-stage nature of the attack and the involvement of North Korean state-linked actors, though they vary in emphasis on the specific technical steps versus the broader security implications.

Why it matters

The breach underscores the vulnerability of major financial institutions to sophisticated social engineering and supply chain attacks, even with advanced security measures. It highlights the growing threat posed by state-sponsored cybercriminals using recruitment scams to infiltrate corporate networks. The incident also demonstrates the critical role of internal AI tools in modern attack chains and the importance of robust incident response and asset recovery mechanisms in mitigating the impact of large-scale cyber heists.

What to watch

Binance is working with law enforcement and blockchain intelligence firms to trace and freeze the remaining stolen assets. The company has hired independent cybersecurity experts to conduct a review and is establishing a security research fund to focus on AI security in blockchain environments. Ongoing efforts will likely focus on enhancing endpoint security, improving detection of social engineering campaigns, and strengthening controls around internal AI tools and deployment permissions.

Share this article

Want the full story? Read the original reporting

Read on The Register