How much was lost in the FlokiMoon hack?

The FlokiMoon hack resulted in $148K in losses on May 31, 2022.

What attack technique was used in the FlokiMoon exploit?

The FlokiMoon exploit utilized Rugpull. Understanding this attack vector is critical for smart contract auditors and developers building secure DeFi protocols.

How can developers prevent similar smart contract attacks?

Preventing smart contract hacks requires a combination of secure coding practices, thorough security audits, and understanding common attack vectors like reentrancy, oracle manipulation, and access control flaws. Smart Contract Hacking (SCH) provides hands-on training to help developers and auditors identify and prevent vulnerabilities before deployment.

FlokiMoon Hack

TOTAL LOST $148K

Low May 31, 2022 Rugpull

Affected Chain 2022 Incident surface

Recovered - No recovery reported

All-Time Rank #1401 By amount stolen

Protocol Type Exit Scam/Rugpull Target category

Incident Overview

FlokiMoon has been rugpulled by the contract creator.

Token address: 0x085Ac603…4AF9e1

Contract creator: 0x5bD2474D…D3939c

Contract creator removed liquidity on PancakeSwap when price was rised:

https://bscscan.com/tx/0x941cb271…6e0ed0

https://bscscan.com/tx/0xa4d9b189…b8000b.

Then tokens were transfered to 0x5CE8c609…43aab2 in this transaction: https://bscscan.com/tx/0xea37e76e…099d3b

All BNB were laundered via TornadoCache

Example transaction: https://bscscan.com/tx/0x672b5e9f…a33e6e

Incident Report

Protocol / Project FlokiMoon

Date of Incident May 31, 2022

Attack Technique Rugpull

Classification Token

Protocol Information

Protocol Type Exit Scam/Rugpull

Affected Token FlokiMoon

Team Anonymous

Source Code Unverified

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 FlokiMoon'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 FlokiMoon, these are the critical security checks that could have prevented this incident (May 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

Threat Assessment

Severity Level

LOW

Attack Vector Rugpull
Root Cause Token
Year 2022

Learn to Prevent the Next FlokiMoon

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