Harmony Horizon Bridge incident, 2022-06-23
What happened to Harmony Horizon Bridge?
On 23 June 2022 attackers that the FBI later identified as North Korea's Lazarus Group (APT38) used compromised validator keys to drain about $100M from Harmony's Horizon Bridge. At least two validator keys were enough to move funds; none of the money was recovered.
Sources: HarmonyFBIDefiLlamaBlockscout
Key facts
- Date (UTC)
- Protocol
- Harmony's Horizon Bridge (Ethereum and BNB Chain ↔ Harmony)
- Reported loss
- ≈ $100M in 14 bridged assets (USDC, ETH, USDT, BNB and others) FBIHarmonyDefiLlama
- Root cause
- Key compromise — attackers compromised at least two of the bridge validators' private keys, enough to approve withdrawals, after phishing a developer and gaining server access HarmonyFBI
- Chains
- Ethereum, BNB Chain, Harmony
- Recovery
- Not recovered
- Official post-mortem
- Summary of the Horizon Bridge Incident
Timeline
All dates and times in UTC.
- 2022-06-02 — Server logs later suggest the attackers began reviewing the bridge implementation. Harmony
- 2022-06-23 11:06 — Transfers of 14 bridged assets to the attacker's account begin. Harmony
- 2022-08-03 — Harmony publishes its incident summary; bounty raised to $10M. Harmony
- 2023-01-13 — More than $60M of stolen ETH laundered via RAILGUN. FBI
- 2023-01-23 — FBI attributes the theft to Lazarus Group / APT38. FBI
Where did the funds go, and was anything recovered?
Funds were moved through new wallets into Tornado Cash. Harmony offered a $1M, later $10M, bounty without a legitimate response (Harmony forum). On 13 January 2023 the attackers laundered more than $60M of the stolen ETH through the RAILGUN privacy protocol; part was converted to bitcoin at exchanges (FBI).
Which routes and bridges were affected?
All assets held by the Horizon Bridge on Ethereum and BNB Chain were at risk; bridged tokens on Harmony (for example 1USDC) lost their backing, and holders who never used the bridge themselves were hit through those tokens. Harmony is not among the chains upswap samples.
Why did it happen?
Horizon's Ethereum side was controlled by a multisig of bridge validators, and only a small number of signatures — Harmony's own summary says the attackers compromised "at least two out of four" keys — were needed to move funds (Harmony forum). On-chain, the Ethereum multisig required 2 of its 4 owners just before the attack (Blockscout), not the 2-of-5 often reported. Harmony believes a developer was phished into installing malware, which let the attackers read internal chats, access non-public bridge code and gain backdoor server access, where the encrypted keys could be decrypted. The contracts and the Harmony chain were not compromised.
This is the most common failure mode among large bridge thefts: a low signing threshold held by people inside one organisation, protected by operational security rather than cryptography. The same group was later linked to other bridge thefts, and the FBI tracked the proceeds publicly.
A larger threshold spread across independent organisations, hardware-backed signing and withdrawal rate limits are the standard mitigations; none would have made a phishing attack impossible, but each would have raised the number of organisations the attacker needed to breach.
Harmony's case also shows how long the aftermath lasts. Seven months later the stolen ETH was still being laundered and tracked by the FBI, while bridged tokens on Harmony traded far below their nominal value. For users, the practical loss was not only the theft but the collapse of every asset that depended on the bridge.
What should users have done then, and what should they do now?
At the time
Users could not defend against key theft, but they could limit exposure: holding bridged "1"-prefixed tokens on Harmony meant trusting a multisig with a very low signing threshold. Treating such a threshold as a red flag and keeping balances small was the practical defence.
Now
Before using any multisig-secured bridge, look up its threshold and signer list (L2Beat and the project's docs usually list them). A threshold of two, or signers from one company, is a reason to bridge only what you need and move it on promptly.
Sources
4 independent publishers. Links checked on the date shown.
- Summary of the Horizon Bridge Incident — Harmony · Official · checked
- FBI Confirms Lazarus Group Cyber Actors Responsible for Harmony's Horizon Bridge Currency Theft — FBI · Government · checked
- DefiLlama Hacks — Harmony Bridge, 2022-06-23 — DefiLlama · Database · checked
- Horizon MultiSigWallet 0x715C…6De6 (Ethereum) — required() = 2, 4 owners at block 15,011,360 — Blockscout · Database · checked
How do I cite this page?
Burn, A. / upswap.io (2026). Harmony Horizon Bridge incident (2022-06-23). Updated 2026-10-24. https://upswap.io/incidents/harmony-horizon-2022#summary. CC BY 4.0. Accessed ____.
Stable anchors: #summary #facts #timeline #funds #affected #analysis #then #now #sources #cite
