NEVER Hack

TOTAL LOST $240K
Low Rugpull

Summarize with AI

Affected Chain 2024 Incident surface
Recovered - No recovery reported
All-Time Rank #1229 By amount stolen
Protocol Type Dexs Target category

Incident Overview

NEVER token on the BSC chain was rug-pulled by the team with a loss of about  240K USD.

The NEVER token was exit scammed via an insider job. The smart contract backdoor allowed the scammer to sell a significant amount of tokens without having it on his balance. EOA which performed an exit scam via token dumping on the DEX (Pancake Swap) earned 428 BNB or approx 240K USD.

Scammer:

https://bscscan.com/address/0xd7c358b8…908b84

Sell tx:

https://bscscan.com/tx/0x90254b3b…5e77e4

Incident Report

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

Protocol Information

Protocol Type Dexs
Affected Token NEVER
Official Website neverdie.com/
Protocol Twitter/X @malounever
Team Anonymous
Source Code Unverified

Market Context at Time of Hack

Token Categories
Solana Ecosystem Meme Solana Meme

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 NEVER'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 NEVER, these are the critical security checks that could have prevented this incident (July 2024).

  • 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 NEVER

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