Platypus Finance Hack

TOTAL LOST $2.2M
Medium Reentrancy avalanche

Summarize with AI

ChatGPT Perplexity Claude Grok
Affected Chain avalanche Incident surface
Recovered - No recovery reported
All-Time Rank #622 By amount stolen
Auditors 3 Prior security audits

Incident Overview

Platypus combined stableswap and stablecoin, masterfully utilizing its underlying assets to bring next-level capital efficiency.

This is classified as a Reentrancy . Compare similar hacks →

Incident Report

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

Protocol Information

Protocol Type Dexs
Smart Contract Language Solidity
Official Website platypus.finance
Protocol Twitter/X @Platypusdefi

Market Context at Time of Hack

Token Categories
Avalanche Ecosystem
Protocol Links
Telegram

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 avalanche smart contracts and deploy a custom exploit contract
Protocol Analysis Identification of the exploitable vulnerability in Platypus Finance'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, Audit Report 2, Audit Report 3 — still lost $2.2M. Prior audits don't guarantee safety, especially after post-audit code changes.

If you're auditing a protocol with similar architecture to Platypus Finance, these are the critical security checks that could have prevented this incident (October 2023).

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

Reentrancy

Proof-of-Concept Exploits

1 PoC available
poc-exploits - platypus finance
$ Platypus Business Logic Flaw

On-Chain Evidence & References

Sources & References

Browse all hacks

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

1Inch $2.6M
Reentrancy
StepHeroNFTs $90K
Reentrancy
Clober Liquidity Vault $500K
Reentrancy
Clober $500K
Reentrancy
Penpie $27.0M
Reentrancy
PolyNetwork $5.0M
Reentrancy

Learn to Prevent the Next Platypus Finance

The Platypus Finance 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