PolyNetwork Hack

TOTAL LOST $5.0M
Medium Reentrancy polynetwork

Summarize with AI

Affected Chain polynetwork Incident surface
Recovered - No recovery reported
All-Time Rank #425 By amount stolen
Auditors 1 Prior security audit

Incident Overview

Poly Network is a global cross-chain protocol for implementing blockchain interoperability and building Web3.0 infrastructure. Poly Network has also integrated over 20 blockchains.

Incident Report

Protocol / Project PolyNetwork
Date of Incident
Affected Chain(s) polynetwork
Attack Technique Reentrancy
Classification Protocol Logic
Primary Source View Post-Mortem

Protocol Information

Protocol Type Bridge
Smart Contract Language Solidity
Official Website www.poly.network
Protocol Twitter/X @PolyNetwork2

Market Context at Time of Hack

Token Categories
Platform DeFi Scaling Ethereum Ecosystem

What the Attacker Needed to Succeed

Understanding the prerequisites for this type of attack helps auditors identify protocols that are most at risk and helps developers build better defenses.

Technical Knowledge Deep understanding of reentrancy and Solidity and EVM internals
Capital Required Seed capital to cover gas and initial position setup
On-Chain Access Ability to interact with polynetwork smart contracts and deploy a custom exploit contract
Protocol Analysis Identification of the exploitable vulnerability in PolyNetwork's contract logic - root cause: protocol logic
Execution Speed Precise transaction ordering and timing to exploit the vulnerability within a single atomic block
Obfuscation Plan A strategy to launder and move stolen funds - typically through mixers, cross-chain bridges, or decentralized DEX swaps to resist tracing

What Auditors Should Check

Could this have been caught in audit? Yes — skilled auditors routinely flag Reentrancy vulnerabilities in code review
Audited by Audit Report 1 — still lost $5.0M. Prior audits don't guarantee safety, especially after post-audit code changes.

If you're auditing a protocol with similar architecture to PolyNetwork, these are the critical security checks that could have prevented this incident (August 2024).

  • Verify all logic paths related to Reentrancy are guarded by proper access controls and input validation - see the Reentrancy attack class for patterns
  • Check that all state-changing functions follow the Checks-Effects-Interactions (CEI) pattern to prevent reentrancy and logic ordering bugs
  • Review privileged functions (owner, admin, governance) for potential abuse vectors - centralization risks should be documented and bounded with timelocks or multi-sigs

Master these auditing techniques with hands-on labs and real exploit scenarios in the Smart Contract Hacking course.

Free Trial

Security Audit History

Related Attack Classes

The technique used in this hack maps to these vulnerability classes in our security curriculum:

See all Reentrancy examples →

Sources & References

Learn to Prevent the Next PolyNetwork

The PolyNetwork hack is one of many attacks that skilled auditors are trained to detect before deployment. Master real exploit patterns and defense techniques with hands-on Web3 security training.

Recreate exploit patterns safely Free Trial