MoonFintech Honeypot

Reported loss Not disclosed
BNB Chain
Honeypot

What happened

MoonFintech was a BNB Chain token that blocks every sale into its PancakeSwap pool. The first transferFrom the contract ever processes saves its recipient in a variable named newun. When the owner adds liquidity through the router, that recipient is the PancakeSwap pair.

After that, any transfer or transferFrom whose destination is newun reverts with "please wait", so holders can buy but cannot sell. The owner can repoint newun at any time with transfernewun, and the pair can still send tokens out, so removing liquidity keeps working. De.Fi's REKT database lists MoonFintech as an exit scam/honeypot; no loss figure or transaction was found.

How it happened

  1. newun starts empty. The first transferFrom sets it: if(from != address(0) && newun == address(0)) newun = to;. Adding liquidity through the PancakeSwap router calls transferFrom(owner, pair, amount), so the pair becomes newun.
  2. Every later transferFrom checks else require(to != newun, "please wait");. A router sell moves tokens from the holder to the pair, so it reverts.
  3. Plain transfer has the same check, require(to != newun, "please wait");, so sending tokens straight to the pair and calling swap does not work either.
  4. Buys are not affected, because the pair pays buyers with transfer to the buyer's address, not to newun. When liquidity is removed, the pair sends tokens back the same way, so the LP holder's exit still works.
  5. Only the owner can move the block: function transfernewun(address _newun) public onlyOwner { newun = _newun; }. Ownership can only move by transferOwnership plus acceptOwnership; there is no renounce function, and as of 2026-09-30 owner still returns the deployer.

Protocol details

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

Build your security review skills

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