Platypus Finance Hack

TOTAL LOST $52K
Low Reentrancy

Summarize with AI

Affected Chain 2023 Incident surface
Recovered - No recovery reported
All-Time Rank #1711 By amount stolen
Auditors 3 Prior security audits

Incident Overview

Platypus Finance, an Avalanche-based DEX, was exploited in a reentrancy attack causing a loss of 51,840 $USD.

Platypus Finance faced an exploit that caused a loss of approximately $51k. The exploit emerged due to an issue with the liquidity conversion calculation for LP-USDC, which resulted in an excessively large quantity calculation for USDC.e when swapping USDC for USDC.e. The call to asset.addLiability() in the _deposit function caused an increase in the asset.liability() parameter in withdrawFrom, allowing the hacker to withdraw more USDC.e than the amount of USDC previously deposited.

The funds remain in the attacker's address, amounting to $31,120 worth of assets in Avalanche and $20,450 worth of $DAI in Ethereum chain.

Attacker Address:

https://showtrace.io/address/0xc64afc46…79521a

Malicious Transaction Example:

https://showtrace.io/tx/0x5e785b87…bab388

Malicious Contract Address:

https://showtrace.io/address/0x16a3c9e4…8f1ed8

Incident Report

Protocol / Project Platypus Finance
Date of Incident
Attack Technique Reentrancy
Classification Exchange (DEX)
Primary Source View Post-Mortem

Protocol Information

Protocol Type Dexs
Affected Token PTP
Official Website platypus.finance/
Protocol Twitter/X @Platypusdefi
Team Anonymous
Source Code Verified On-Chain

Market Context at Time of Hack

Token Categories
Avalanche 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 smart contracts and deploy a custom exploit contract
Protocol Analysis Identification of the exploitable vulnerability in Platypus Finance's contract logic - root cause: exchange (dex)
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 $52K. 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 (July 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 →

Sources & References

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.

Recreate exploit patterns safely Free Trial