Flare Token Hack

TOTAL LOST $17.0M
High Rugpull

Summarize with AI

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

Incident Overview

Flare Token was possibly rugpulled. An EOA address was able to remove funds from the PancakeSwap pool for a total of 17,010,503 $USD after claiming roughly 4,000,000,000 $FLARE tokens from a vault contract.

Flare Token is a BEP20 token trading on PancakeSwap and can't be confused with Flare Network with the $FLR token symbol. An EOA address called a withdrawProfit() function on a contract with an unverified source code and received 3,973,277,600 $FLARE tokens. The part of the claimed tokens was used to perform a swap and drain of liquidity.

The exploiter profited 17,010,503 $USD and transferred funds to another EOA address.

Scammer addresses:

https://bscscan.com/address/0xa0a613ca…53d898

https://bscscan.com/address/0xE55D77F7…68Eb20

Malicious transaction:

https://bscscan.com/tx/0xa0913502…51c027

Liquidity drain transaction:

https://bscscan.com/tx/0x2af9b1c4…1c1d51

Incident Report

Protocol / Project Flare Token
Date of Incident
Attack Technique Rugpull
Classification Token

Protocol Information

Protocol Type Exit Scam/Rugpull
Affected Token FLARE
Official Website pipeflare.io/
Protocol Twitter/X @PipeFlare
Team Anonymous
Source Code Unverified

Market Context at Time of Hack

Token Categories
Collectibles & NFTs Gaming Polygon Ecosystem Play To Earn

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

Post-Incident Timeline

  • 2022-11-17

    On 17 November, an EOA address that received the funds transferred all the stolen amount through TornadoCash.

Sources & References

Learn to Prevent the Next Flare Token

The Flare Token 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