NFDAO Hack

TOTAL LOST $88K
Low Rugpull

Summarize with AI

Affected Chain 2023 Incident surface
Recovered - No recovery reported
All-Time Rank #1572 By amount stolen
Auditors 1 Prior security audit

Incident Overview

NFDAO project experienced a rugpull exit scam in which the token deployer-related address withdrew liquidity from PancakePool, resulting in a loss of 88,420 $USD.

NFDAO is a BEP20 token trading on PancakeSwap. The token's contract was exploited by its deployer-related address to remove all funds available in the liquidity pool. All stolen funds were transferred to another EOA address leaving investors holding worthless tokens.

Scammer Address:

https://bscscan.com/address/0x91b6854e…62c6cb

Deployer Address:

https://bscscan.com/address/0xA90ab5bE…9b6970

Funds Holder Address:

https://bscscan.com/address/0x7E0E658a…922eEc

Liquidity Removal Transaction:

https://bscscan.com/tx/0xb6d28af3…857d5f

Stolen Funds Transfer Transaction:

https://bscscan.com/tx/0x45317e4c…84471a

Incident Report

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

Protocol Information

Protocol Type Partially Algorithmic Stablecoin
Affected Token NFD
Official Website fxdao.io
Protocol Twitter/X @FxDAO_io
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 NFDAO'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
Audited by Audit Report 1 — still lost $88K. Prior audits don't guarantee safety, especially after post-audit code changes.

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

  • 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

Security Audit History

Sources & References

Learn to Prevent the Next NFDAO

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