BlueOrigin Honeypot

Reported loss Not disclosed
BNB Chain
Honeypot

What happened

BlueOrigin (BlueOrigin) is a BEP-20 token on BNB Chain built on a known "stealthy LP block" honeypot template. The first transferFrom call, which in practice is the owner adding PancakeSwap liquidity, silently stores its recipient (the liquidity pair) in the variable newun. After that, every transfer or transferFrom whose recipient is newun reverts with please wait.

Buying still works because the pair sends tokens out. Selling does not, because a sale sends tokens into the pair. The owner can repoint or clear newun at any time with transfernewun.

De.Fi's REKT database lists the token as an exit scam/honeypot; no transaction evidence of losses was found.

How it happened

  1. The constructor mints the whole supply to the deployer (owner).
  2. newun starts as the zero address. The first transferFrom from a non-zero address sets newun = to, and this call does not revert. When the owner adds liquidity through PancakeSwap, the router's transferFrom moves tokens into the pair, so the pair becomes newun.
  3. Buyers receive tokens through transfer calls made by the pair, which pass because the recipient is not newun.
  4. A holder's sale sends tokens to the pair through transferFrom or transfer, and require(to != newun, "please wait") reverts it.
  5. The owner can call transfernewun to set newun to any address, including zero, which reopens transfers to the pair until the next transferFrom sets it again. The owner can also withdraw any BNB held by the contract with clearCNDAO.

Protocol details

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

Build your security review skills

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