FDO Hack
Incident Overview
FDO token slippage happened on PancakeSwap. The attacker took 96,000 $FDO tokens from the project's vault contract and sold them for 160,441 $USD
FDO is a BEP20 token and can't be confused with other tokens with the same symbol. The EOA address claimed 96,000 $FDO from the project's vault smart contract with unverified source code. Consequently, the attacker sold them on PancakeSwap for 160,441 $BUSD and transferred them to another EOA address.
The relationship between the attacker and the project's team is not approved.
Attacker address:
https://bscscan.com/address/0x04718c58…6112F6
Funds transferred to:
https://bscscan.com/address/0xf5c54392…c61c1c
Malicious transaction:
https://bscscan.com/tx/0xa31bdcfa…9b2620
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 FDO, these are the critical security checks that could have prevented this incident (October 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 FDO
The FDO 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.