NONAME Hack

TOTAL LOST $30K
Low Rugpull ethereum

Summarize with AI

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

Incident Overview

The contract deployer used the proxy contract to mint tokens and send them onto his wallet at:

https://etherscan.io/tx/0xda6f43af…0096d4

The contract deployer added initial liquidity at:

https://etherscan.io/tx/0x03b4dcfa…5c4c20

The contract deployer removed liquidity at:

https://etherscan.io/tx/0xfce75c90…168715

The contract deployer has sold tokens at:

https://etherscan.io/tx/0x04d42088…b9fe17

In addition, the project was holding a fundraising event, using NonameCrowdsale smart contract. The list of transactions, where the sale contract gathered ETH from investors:

https://bloxy.info/txs/transfers_to/0x1a9f9c40…a02f40?currency_id=1

The raised funds had the final recipient - the proxy contract, which received ETH from the sale contract:

https://bloxy.info/txs/transfers_from/0x1a9f9c40…a02f40?currency_id=1

After, the proxy contract distributed ETH into 2 external wallets at:

https://etherscan.io/tx/0x57cf8745…a31bdd

https://etherscan.io/tx/0xd494ea26…f25bc1

Incident Report

Protocol / Project NONAME
Date of Incident
Affected Chain(s) ethereum
Attack Technique Rugpull
Classification Token

Protocol Information

Protocol Type Exit Scam/Rugpull
Affected Token NONAME

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 ethereum smart contracts and deploy a custom exploit contract
Protocol Analysis Identification of the exploitable vulnerability in NONAME'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 NONAME, these are the critical security checks that could have prevented this incident (February 2021).

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

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