NEOBUX Honeypot

Reported loss Not disclosed
BNB Chain
Honeypot

What happened

NEOBUX (NBX) was a BNB Chain token whose transferFrom function stores the first recipient it ever sees in a variable called newun and then rejects every later transfer to that address with the error "please wait". The first transferFrom is normally the router moving tokens into the PancakeSwap pool when liquidity is added, so the pool becomes the blocked address: buyers can receive NBX from the pool, but holders cannot send it back into the pool to sell. The owner can also repoint newun to any address through transfernewun.

De.Fi's REKT database lists NEOBUX as an exit scam / honeypot dated 2021-03-29, the day the contract was deployed.

How it happened

  1. The deployer receives the entire supply at deployment (balances[owner] = _totalSupply;), and newun starts empty.
  2. The first transferFrom call finds newun unset and stores its recipient: if(from != address(0) && newun == address(0)) newun = to;. When liquidity is added through the router, that recipient is the PancakeSwap pair.
  3. From then on, both transfer and transferFrom run require(to != newun, "please wait");. A sell moves NBX from the holder into the pair, so it reverts. A buy moves NBX out of the pair to the buyer, so it succeeds.
  4. The owner can change the blocked address at any time with transfernewun(address _newun) public onlyOwner. The contract has no renounce function; ownership can only pass through transferOwnership and acceptOwnership, and the deployer is still the owner.
  5. Nothing restricts tokens leaving the pair, so whoever holds the pool's LP tokens can remove liquidity while other holders cannot sell. The sources reviewed do not show whether or when that happened for NEOBUX.

Protocol details

Classification Token
Protocol Type Exit Scam/Honeypot
Affected asset / contract NBX

Build your security review skills

Work through hands-on labs covering real exploit mechanics, review techniques, and defensive patterns.