Polynomial Protocol Hack
Incident Overview
The attacker could drain USDC balances of user addresses that approved their tokens to be spent by the PolynomialZap contract.
The swapAndDeposit() function of the PolynomialZap contract contains a bug: there are no limitations for two input parameters - swapTarget and swapData. This allows anyone to abuse the function and steal tokens approved to the contact.
All tokens that are approved to the vulnerable contract are still in danger.
The vulnerable contract:
https://optimistic.etherscan.io/address/0xB162f01C…D77c82#code
The attack contract:
https://optimistic.etherscan.io/address/0xf682e302…4e29a8#code
Incident Report
Protocol Information
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.
What Auditors Should Check
If you're auditing a protocol with similar architecture to Polynomial Protocol, these are the critical security checks that could have prevented this incident (November 2022).
- Verify all logic paths related to Other are guarded by proper access controls and input validation
- 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 TrialSources & References
Learn to Prevent the Next Polynomial Protocol
The Polynomial Protocol 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.