FDB Hack

TOTAL LOST $104K
Low Rugpull

Summarize with AI

Affected Chain 2022 Incident surface
Recovered - No recovery reported
All-Time Rank #1519 By amount stolen
Protocol Type Exit Scam/Rugpull Target category

Incident Overview

FDB token was rugpulled by the deployer-related EOA address. The total profit of the scammer reached 103,540 $USD.

FDB is a BEP20 token trading on PancakeSwap. The deployer-related EOA address drained liquidity for the total amount of 103,540 $USD. The scammer transferred 30,000 $BUSD to other addresses, and the remaining 12,861 $BUSD and 221.7 $BNB stay at the original address.

Scammer address:

https://bscscan.com/address/0x485ba16c…abecb9

Liquidity drain transactions:

https://bscscan.com/txsInternal?a=0x485ba16c…abecb9

https://bscscan.com/token/0x55d39832…197955?a=0x485ba16c…abecb9

Incident Report

Protocol / Project FDB
Date of Incident
Attack Technique Rugpull
Classification Token
Primary Source View Post-Mortem

Protocol Information

Protocol Type Exit Scam/Rugpull
Affected Token FDB
Team Anonymous
Source Code Verified On-Chain

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 rugpull 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 FDB's contract logic - root cause: token
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? Hard to catch — private key / OpSec failures are outside smart contract audit scope

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

  • Verify all logic paths related to Rugpull 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

Learn to Prevent the Next FDB

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