Security and scams · Explainer
What Happened in the Poly Network Hack?
In August 2021, an attacker used a flaw in Poly Network’s cross-chain system to move more than $600 million in crypto. Most of the assets were later returned, but the incident showed why bridge security matters.
By the HelpfulCoin editorial team · Updated

What happened in the Poly Network hack?
In August 2021, an attacker exploited Poly Network’s cross-chain system and moved cryptocurrency worth more than $600 million. The incident was one of the largest reported crypto thefts at the time, and most of the assets were later returned.
Poly Network was a decentralized finance protocol designed to move assets and messages between blockchains. The attack did not involve breaking into every user’s wallet. Instead, it targeted the protocol’s smart contracts—the programs that carry out transactions on a blockchain—and the rules those contracts used to approve cross-chain instructions.
The reported haul was valued at roughly $610 million when the theft was discovered. That figure covered many tokens and depended on their market prices. As the story unfolded, the attacker returned assets in stages, while some funds were frozen by token issuers.
The episode matters beyond Poly Network. A bridge can expose users to risks in the contracts and authorization systems that connect separate blockchains. A transaction may look routine to a user even though it depends on several technical components working correctly behind the scenes.
How did the Poly Network exploit work?
The attacker exploited weaknesses in the way Poly Network checked whether cross-chain commands were authorized. In simple terms, the protocol’s contracts accepted instructions that should not have been accepted, allowing the attacker to move assets held in connected systems.
A cross-chain protocol has to decide whether a message from one blockchain is genuine before acting on it elsewhere. That can involve contracts, designated signers or validators, and rules for checking messages. If those checks are implemented incorrectly, an attacker may be able to forge or manipulate an instruction without stealing a user’s password or recovery phrase.
Public accounts of the incident describe a flaw in Poly Network’s cross-chain authorization logic. The important takeaway is not a code recipe: the security boundary failed, so the system treated an unauthorized command as valid. That let the attacker transfer tokens across supported networks.
This differs from phishing. In a phishing attack, a victim is tricked into giving away a secret or approving a transaction. In the Poly Network incident, the target was the protocol’s own infrastructure. Users still face phishing risks, but changing a wallet password would not have fixed this contract-level weakness.
Why are cross-chain bridges vulnerable to this kind of attack?
Cross-chain bridges matter because they hold or control assets while coordinating activity between blockchains, and that creates extra points of failure. A bridge is software that lets users move value or messages between networks that do not share the same transaction history.
Depending on how it is built, a bridge may lock tokens on one network and issue a corresponding token on another, or rely on a group of validators or a relayer system to confirm transfers. In either case, the destination network must trust some process to confirm that a transfer really happened on the source network. A mistake in that process can put assets at risk.
Bridge security can depend on more than the visible smart contract. It may also involve administrator permissions, validator keys, message-verification code, token contracts, and the security of each connected chain. A weakness in one part can have consequences across several networks.
That does not mean every bridge works the same way or has the same risks. It does mean a bridge is not simply a neutral pipe. Before using one, consider what controls its contracts, who can change them, what assets it holds, and what happens if a transfer is delayed or disputed.
Were the stolen funds returned?
Most of the stolen assets were later returned, but the recovery involved several stages and did not make the original exploit harmless. Reports at the time described the attacker sending back large portions of the assets after Poly Network publicly asked for their return.
Some tokens, including stablecoins, can be frozen by the organizations that issue them. That means a token issuer may be able to stop transfers from a particular address. Frozen assets cannot be treated like freely transferable crypto, and the amount recovered can depend on how each token is controlled. The dollar value of the haul also shifted as market prices changed.
The attacker claimed to have acted as a white-hat hacker—a person who finds vulnerabilities and says they are trying to expose them rather than profit from theft. That claim does not change the fact that the exploit moved assets without authorization. A claimed good motive is not a security control and should not be assumed to make similar incidents safe.
For users, the practical lesson is to distinguish between an exploit being contained, assets being frozen, and assets being returned. Those are different outcomes. A recovery story does not guarantee that users in another incident will get their funds back.
Is Poly Network safe to use in 2026?
The 2021 recovery does not prove that Poly Network, or any bridge, is safe to use in 2026. A past exploit is relevant history, but current safety depends on the system’s present contracts, permissions, reviews, operations, and response plans. A returned asset is not the same thing as a repaired or independently verified system.
Before using any bridge, check whether the project currently publishes details about its security reviews, contract upgrades, administrator controls, and incident response. An audit is a review of code, not a promise that the code has no flaws. Also check whether the asset and destination network are supported by the project itself; fake bridge sites often imitate real services.
Poly Network’s current operating status and current security arrangements should be checked through its official channels before any use. Do not assume an old announcement, a familiar name, or a search result means a bridge is currently active or safe. If the project does not publish information you need to assess its current security, treat that as a reason to pause rather than fill in the gaps with guesses.
Cross-chain transfers can be difficult to reverse. Only consider moving an amount you can afford to have delayed or lost, and understand the route before signing a transaction.
What should you do if a bridge exploit affects your funds?
If you think an exploit or suspicious transaction affected your funds, first stop interacting with the suspected app and preserve the transaction details. Do not rush to sign another transaction or follow a recovery offer sent through social media or direct messages.
Use these steps:
- Record what happened. Save transaction IDs, wallet addresses, the network, token name, and the time of the transfer. Do not post your recovery phrase or private keys.
- Check official notices. Look for a security announcement from the project and confirm that the account or channel is genuinely official. Be wary of copycat accounts and fake support staff.
- Contact relevant providers. If an exchange, wallet service, or token issuer is involved, use its verified support route. A token issuer may be able to freeze certain tokens, but this is not available for every asset and cannot guarantee recovery.
- Review approvals only if relevant. If you personally approved a suspicious transaction, check and revoke affected token permissions using a trusted tool. Revoking an approval cannot undo a completed transfer or repair a compromised bridge.
- Report the incident. Keep records and report it to the appropriate platform or local authorities if needed.
Never pay an upfront “recovery agent” or share a seed phrase to get help.
What mistakes should you avoid when using a crypto bridge?
The most common mistakes are assuming that a familiar interface or a successful past transfer proves a bridge is safe. A bridge can change its contracts, permissions, supported routes, or security arrangements, and previous transactions do not test every possible failure.
Watch out for these errors:
- Treating an audit as a guarantee. An audit can identify problems in reviewed code, but it has a scope and date. It cannot guarantee that every bug was found or that later changes are safe.
- Sending the wrong asset or using the wrong network. Similar token names can refer to different contracts. Check the token and destination network before approving a transfer.
- Ignoring permissions. Read what a wallet asks you to approve. A token approval may give a contract ongoing permission to move tokens, not just permission for one transfer.
- Trusting urgent messages. Attackers often impersonate project teams after an incident and direct users to fake recovery pages or claim a wallet must be “verified.”
- Assuming transfers are reversible. Blockchain transactions are usually difficult to undo once confirmed. A support team may not be able to retrieve funds sent to the wrong address or route.
Take time to verify the official app, the contract address, the network, and the amount. If any detail is unclear, do not sign until it is resolved.
What does the Poly Network hack teach crypto users?
The Poly Network hack shows that a protocol can fail even when users do not give an attacker their wallet credentials. Crypto security includes the contracts and authorization systems that process a transaction, not just the user’s device and recovery phrase.
For users, this means checking both personal and protocol-level risks. Keep recovery phrases offline and private, use a wallet you can verify, and inspect transaction requests. Separately, look at how a bridge verifies transfers, whether its contracts can be upgraded, who controls privileged permissions, and how the project communicates during an incident. No single check removes the risk.
It also helps to distinguish between a bridge and a decentralized exchange. A bridge moves assets or messages across chains; a decentralized exchange swaps assets on a supported network. Different systems have different failure modes, and using one does not eliminate the risks of the other. Across is one example of a cross-chain bridge, but its presence in a category does not establish that it is safer than another bridge.
The practical rule is simple: understand the route, check current security information, and limit exposure. The Poly Network attacker’s later return of assets was unusual; users should not count on an attacker, token issuer, or project team restoring funds after a future exploit.
Frequently asked questions
How much was stolen in the Poly Network hack?
In August 2021, an attacker exploited Poly Network’s cross-chain authorization system and moved assets worth more than $600 million. The attack targeted the protocol’s smart-contract logic, not the private keys of every Poly Network user.
Did the Poly Network hacker return the money?
Most of the stolen assets were later returned. Some stablecoins were frozen by their issuers, so recovery did not mean every asset was returned through an ordinary transfer.
How did the Poly Network exploit work?
The attacker exploited flaws in the system that checked whether cross-chain commands were authorized. In effect, the contracts accepted commands the attacker should not have been able to issue.
Does the Poly Network hack mean all crypto bridges are unsafe?
No. The incident is a warning about smart-contract and cross-chain risks, not proof that every bridge is equally unsafe. Any bridge can still have bugs, faulty permissions, or other security weaknesses.
What should I do if I think a bridge exploit affected me?
Do not share your recovery phrase or pay anyone who promises to recover funds. Save transaction details, check official project announcements, and contact the wallet, exchange, or token issuer involved through verified channels.
Mentioned in this guide
dApps in this guide
Across is a cross-chain crypto bridge with fast relayer-based transfers; it is worth a look, but check route costs and bridge risks.
Crypto.com is a crypto app and exchange with broad trading and euro deposit options; it merits a look, but check fees and product risks.
Poly Network is a cross-chain bridge with a major 2021 exploit and unclear current status, so using it carries substantial risk.
Save is a lending protocol on Solana and Eclipse; it offers crypto lending and borrowing, but carries smart-contract and collateral risks.
Keep reading
Related guides
Security and scams · Explainer
Why Are Crypto Bridges Hacker Targets?
Blockchain bridges connect networks, but the code, keys and liquidity that make transfers possible can also create valuable attack points. Learn why bridges attract hackers, how common exploits work and what to check before transferring crypto.
Security and scams · Explainer
What Happened in the Harmony Horizon Bridge Hack?
In June 2022, attackers stole about $100 million in crypto from Harmony’s Horizon bridge. Here’s how the incident worked, what it means for bridge users, and how to take precautions before moving tokens across chains.
Security and scams · Explainer
What Happened in the QiDao Superfluid Exploit?
QiDao’s Superfluid-related contract was reportedly exploited for about $13 million. Learn what that figure does—and does not—tell you, how to check whether you may be exposed, and what to do before using either protocol.
Blockchain · Chain guide
What Is TON, or The Open Network?
TON, short for The Open Network, is a blockchain that supports Toncoin, digital assets and apps, including services accessible through Telegram. Learn what the network does, how its connection to Telegram works, and how to use it more safely.
Security and scams · Explainer
Was Polygold a Scam or a Token Collapse?
A token’s collapse can leave holders with real losses, but a fall in price alone does not prove that Polygold was a scam. Learn how to assess the evidence, protect your wallet and avoid recovery fraud.
Security and scams · Explainer
Did an OpenSea Upgrade Put Users at Risk?
A headline about an OpenSea upgrade “throwing the door open” to hackers needs evidence of a specific flaw. The incidents commonly associated with OpenSea include phishing and a past listing issue, but they do not show that an upgrade caused them.
Security and scams · How-to
How to Prevent Crypto Wallet Drainers in 2026
A wallet drainer tricks you into revealing recovery words or approving actions that let it move your crypto. Learn how to spot dangerous requests, reduce your exposure, and respond if you think you signed one.
Security and scams · Explainer
How Do OpenSea Phishing Emails Steal NFTs?
Fake OpenSea emails can steer NFT traders to lookalike sites or trick them into approving wallet actions that transfer assets. Learn how the scams work, how to check an alert, and what to do if you clicked or signed something suspicious.