Pizza Hack

TOTAL LOST $9.9M
Medium Other

Summarize with AI

ChatGPT Perplexity Claude Grok
Affected Chain 2021 Incident surface
Recovered - No recovery reported
All-Time Rank #313 By amount stolen
Protocol Type Lending Target category

Incident Overview

Quick Summary

Exploitation of eCurve Tripool resulted in abnormal issuance of LP tokens and significant asset loss.

Details of the Exploit

The attacker cyclically deposited stablecoins into eCurve Tripool using a malicious contract, leading to abnormal issuing of eCurve Tripool LP tokens. The attacker then transferred 12,000,000 TRIPOOL into their EOA address (itsspiderman1). The attacker deposited these tokens into lend.pizza as collateral and drained all assets from lending, transferring them into the itsspiderman contract address.

The total assets lost include EOS, DFS, BOX, YFC, TAG, USDT, TPT, KEY, DAPP, PBTC, CHEX, OGX, ETH, USN, USDC, IQ, BTC, USDB, OUSD, BOXAI, and PETH.

Block Data Reference

The attacker's address:

https://bloks.io/account/itsspiderma1

The transaction behind the attack:

https://bloks.io/transaction/a7392b4e2b3ebc68345c91f538114eeb51cea48584783f2b162b7d4e94f725df

The contract used within the attack:

https://bloks.io/account/itsspiderman

The transaction of depositing TRIPOOL into lend.pizza:

https://bloks.io/transaction/a7392b4e2b3ebc68345c91f538114eeb51cea48584783f2b162b7d4e94f725df

Incident Report

Protocol / Project Pizza
Date of Incident
Attack Technique Other
Classification Other
Primary Source View Post-Mortem

Protocol Information

Protocol Type Lending
Official Website pizza.finance/
Protocol Twitter/X @PizzaProFi
Team Anonymous
Source Code Unverified

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 other and Solidity and EVM internals
Capital Required Seed capital to cover gas and initial position setup
On-Chain Access Ability to interact with smart contracts and deploy a custom exploit contract
Protocol Analysis Identification of the exploitable vulnerability in Pizza's contract logic - root cause: other
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? Likely — with a thorough Other audit checklist and test coverage

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

  • 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 Trial

Sources & References

Browse all hacks

These hacks used the same attack technique. Understanding the pattern helps prevent future exploits.

DeFiTuna $570K
Other
Cascade $1.3M
Other
Lumi Finance $264K
Other
Hinkal $820K
Other
AIDCToken $121K
Other
Polymarket $3.0M
Other

Learn to Prevent the Next Pizza

The Pizza 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.

Start Free Trial Browse Attack Library
Recreate exploit patterns safely Free Trial