Poly Network 🌉 Bridge

On August 10, 2021, an anonymous attacker drained roughly $610–612 million in crypto assets from Poly Network, a protocol that locks tokens on one chain and releases equivalents on another so value can move between Ethereum, BNB Smart Chain and Polygon. It remains one of the largest single thefts in DeFi history (Chainalysis). No private key was stolen and no flash loan was used — the breach was a flaw in how the protocol's own contracts authorized each other, described as an access-control failure in the cross-chain verification logic (rekt.news).

How the attack worked

On each chain, Poly Network split responsibility between two contracts: one stored the current "keeper" public keys — a rotating list of addresses whose signatures were required to approve a cross-chain transfer — and a manager contract that executed relayed transactions once a valid keeper signature was attached. The manager contract, however, was built to call almost any function on almost any contract with attacker-supplied data, including its own key-storage contract. A contract identifies which function to run by the first four bytes of the hashed function signature; the attacker crafted call parameters whose hash collided with those four bytes for the function that overwrites the keeper keys (rekt.news). That let them invoke the key-replacement function directly through the manager's own execution path — a caller the storage contract was built to trust unconditionally. The attacker got a legitimate protocol contract to call a privileged function it should never have exposed to arbitrary input, then rewrote the keeper list to an address under their control. From that point, any "release these locked coins" instruction on all three chains carried a signature the protocol itself accepted, and the attacker drained the collateral.

What happened next

Poly Network went public immediately and appealed to exchanges, miners and the attacker to help block the funds. Within about a day the attacker began returning assets, attaching messages to the return transactions that framed the theft as a demonstration of the protocol's weakness rather than a straightforward robbery. Part of the movement trail was tied to identifiable exchange accounts, which likely pushed the attacker toward returning funds rather than cashing out (Chainalysis). By August 12–13, several hundred million dollars had come back; about $33 million in USDT could not be, since Tether had already frozen it. A final tranche, held in an account requiring both the attacker's and Poly Network's keys, was released by August 25, bringing total recovery close to the full amount taken (Wikipedia). Poly Network publicly thanked the attacker as "Mr. White Hat," offered a $500,000 bug bounty and a symbolic "chief security advisor" title — a gesture security professionals criticized, since a private protocol has no authority to grant immunity from prosecution. No arrest or prosecution followed, and the attacker's identity was never officially confirmed. The protocol kept operating and later ran a bug-bounty program on Immunefi.

What follows from this

• Bridges concentrate risk rather than spreading it. A single access-control bug exposed the entire multi-chain collateral pool at once, not just one network's funds. Any bridge with one shared keeper/verifier layer inherits this shape of risk.
• The flaw was invisible to users. Nothing in the interface or docs signaled that the manager contract could call its own key-storage contract with attacker-chosen data — an architecture defect visible only in a code-level audit, not a user checklist.
• The recovery is not a template. The near-full return depended on partial de-anonymization of the attacker plus one issuer's ability to freeze stablecoins. Most later bridge exploits (Ronin, Wormhole, Nomad) were not returned.
• The industry shifted toward decentralizing verification itself. Later cross-chain designs lean more on threshold/multi-party signatures and narrower contract permissions than one manager contract with broad call rights, and bug bounties became standard rather than an afterthought.