DeFiPie Hack

TOTAL LOST $269K
Low Other

Summarize with AI

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

Incident Overview

The hacker's address on Ethereum:

https://etherscan.io/address/0xf6f43f77…6c0fe1

BSC:

https://bscscan.com/address/0xf6f43f77…6c0fe1

Polygon:

https://polygonscan.com/address/0xce1f4b4f…ff6ede

The transaction behind the attack on the BSC:

https://bscscan.com/tx/0x45f6f792…9c6d75

The hacker:

- created a token contract (X token) with a modified transfer function:

https://etherscan.io/token/0xf8dFD22A…966e4B#readContract

https://etherscan.io/token/0xb5337f26…6362Ef

- created pools for X tokens and deposited liquidity

- provided collateral (USDT, DAI, USDC, etc)

- borrowed X tokens and real tokens (PIE and others) and with a modified transfer function in X token, could able to borrow more than he provided as collateral

- after that from his second account he liquidated loans of X tokens in the first account thereby returning the collateral

- repeated with each pool.

Stolen funds were deposited into Tornado Cash and Typhoon mixers.

Incident Report

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

Protocol Information

Protocol Type Exploit/Other
Affected Token PIE
Official Website defipie.com/
Protocol Twitter/X @defipiepie
Team Public / Doxxed
Source Code Unverified

Market Context at Time of Hack

Token Categories
DeFi Ethereum Ecosystem Governance Lending & Borrowing BNB Chain Ecosystem
Protocol Links
GitHub

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 DeFiPie's contract logic - root cause: yield aggregator
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 DeFiPie, these are the critical security checks that could have prevented this incident (July 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 DeFiPie

The DeFiPie 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