skip to content

Déjà Vu, Lazarus Crew: $387.5m Bitget Exploit Repeats a Pattern

🐱‍💻 Déjà Vu, Lazarus Crew: $387.5m Bitget Exploit Repeats a Pattern - thumbnail

This article originally appeared in Galaxy Research's weekly newsletter. Subscribe to get timely insights delivered to your inbox every Friday morning.

Late last week, Bitget disclosed that attackers had stolen $387.5 million from its hot and warm wallets through a series of unauthorized transfers, and it temporarily halted all withdrawals.

There's a specific feeling you get reading a crypto hack post-mortem and realizing you've already read it. Not just a similar one, the same one, with the nouns swapped.

First, let’s recap what happened with Bitget. The losses span 11 blockchains, including Ethereum, XRP, TRON, Arbitrum, Base and BSC, and the largest single-chain loss was about $83 million in XRP. According to Bitget CEO Gracy Chen, private keys and cold wallets were not compromised, and her statement is confirmed by hundreds of millions of dollars in tokens remaining in the exploited addresses (more on this distinction in OUR TAKE below). Instead, attackers exploited two third-party security products (utilizing a zero-day exploit to obtain high-level internal credentials), inserted fraudulent withdrawal commands into the wallet backend, and deleted those commands after the funds were sent out. SlowMist, a security firm hired by Bitget, traced the earliest malicious activity to Aug. 31 and recovered a custom withdrawal tool built around Bitget's withdrawal logic. It all points to a highly researched, targeted exploit of Bitget’s wallet management. Bitget attributes the attack to North Korean actors, citing IP behavior and onchain analysis, and onchain sleuthing firms Elliptic and TRM found wallet overlaps with prior hacks.

Much of the stolen funds moved through THORChain, which declined Chen's request to refuse service on the grounds that it is decentralized and permissionless (just ignore the security freezes it has done in the past). NEAR Intents took the opposite approach, blocking more than $50 million in attempted laundering flows and freezing about $503,000 mid-execution. Bitget's protection fund, and applicable Proof of Reserve (PoR) overcollateralization, covered the exploit amount, with Bitget covering the entirety of the exploit from the protection fund, which has since been topped up to $300m.

Then on Thursday, NEAR Intents got hit with an exploit. A bug in its Omni deposit and withdrawal infrastructure led to roughly $3.8 million in losses, which it says it will fully compensate. ZachXBT flagged multiple abnormal outflows from the BSC hot wallet, with the funds sent to KuCoin and bridged onward to Bitcoin.

Our take

If this episode sounds familiar, it should. In February 2025, the North Korean hacker group Lazarus took $1.5 billion from Bybit the same way. Instead of stealing Bybit's keys, they compromised Safe{Wallet}'s infrastructure, served the signers a doctored interface, and the signers approved what looked like a routine transfer. The cryptography worked perfectly. It signed exactly what it was told to sign.

Nobody attacks the private-key math. They attack whoever, or whatever, tells the math what to do.

That's the landscape for major exploits these days. Nobody attacks the private-key math, because that math is (for now) unbreakable. They attack whoever, or whatever, tells the math what to do.

A private key is a perfect (depending on the cryptographic protocol’s quantum resistance) mathematical way to protect your funds. It will sign anything anyone puts in front of it, so protecting it is utmost. Exchanges’ private key security is some of the best in the world, and we haven’t seen a private key exploit from a major crypto venue in years. Phemex had a private key exploit in January 2025 for only ~$50m, and Coincheck had a major $500m+ exploit in 2018, but that might as well be the Paleozoic era in crypto years. Private key security is mostly solved, so for exploiters the valuable target isn't the key; it's whoever or whatever decides what gets put in front of the key.

We don't know the full details yet, but the shape of the theft tells you most of what you need. If you had the keys, you'd take everything. Instead, Bitget's first notice described unauthorized transfers from a limited number of hot wallets, and SlowMist believes the haul would have been larger if two forged BTC withdrawal orders hadn't errored out. That's what impersonating an approval pipeline looks like: you only get what the pipeline will process, one convincing request at a time. A partial drain is the fingerprint of an exploit in an intermediary service, not a key exploit.

Bitget still hasn't named the vendors that were exploited. The forensic reports call them "Product A" and "Product B." Hopefully it isn't Gnosis Safe again. SlowMist described multiple “nodes” of Product A being infected with malicious code from the zero-day exploit.

Nick Szabo wrote "Trusted Third Parties Are Security Holes" in 2001. Every year, the industry rediscovers this lesson, each time at a cost of roughly nine figures. The cryptographic math is secure; it’s the structure around it that needs hardening. The AI industry learned a similar lesson this summer when frontier labs’ misaligned agents exploited third-party integrations to escape testing sandboxes.

The aftermath has its own déjà vu. The bulk of the stolen funds was moved and converted, some through THORChain, and THORChain’s X handle replied that it is decentralized and permissionless, so its hands were tied. The Bybit loot (as well as portions of ColdCard and countless other exploits) followed a similar chain-hopping path through THORChain, so at this point it's less a bridge than a getaway car for the DPRK.

One more thing. Nobody has attributed Thursday's exploit of NEAR Intents, and we want to be clear that we are not attributing it either. We simply observe that on Monday NEAR Intents confiscated $500,000 of what looks like Kim Jong Un’s lunch money, and on Thursday someone pilfered $3.8 million from the multichain transaction protocol’s BSC hot wallet. Through the deposit and withdrawal infrastructure. Which is, if you've been following along, the intermediary layer.

Déjà vu. Again.

You are leaving Galaxy.com

You are leaving the Galaxy website and being directed to an external third-party website that we think might be of interest to you. Third-party websites are not under the control of Galaxy, and Galaxy is not responsible for the accuracy or completeness of the contents or the proper operation of any linked site. Please note the security and privacy policies on third-party websites differ from Galaxy policies, please read third-party privacy and security policies closely. If you do not wish to continue to the third-party site, click “Cancel”. The inclusion of any linked website does not imply Galaxy’s endorsement or adoption of the statements therein and is only provided for your convenience.