FairPluto Honeypot

Reported loss Not disclosed
BNB Chain
Honeypot

What happened

FairPluto's transfer and transferFrom both revert with "please wait" when the recipient equals a stored address, newun. In transferFrom, the first call made while newun is unset stores that call's recipient as newun without any check. If that recipient is the liquidity pair, every later sale that sends tokens to the pair reverts, while the owner-only transfernewun can point newun at any address.

The source header says "Ownership renounced", but the code has no renounce function and the on-chain owner read on 2026-09-30 is the deployer address 0x8007835f…603106. De.Fi's REKT database lists FairPluto as an exit scam/honeypot on BNB Chain dated 2021-04-07 and describes the owner as able to disable transfers so users could not sell.

How it happened

  1. The constructor sets balances[owner] = _totalSupply; with _totalSupply = 1000000000000000000000000 and decimals = 9, so the deployer starts with the whole supply. newun starts as the zero address.
  2. In transferFrom, if(from != address(0) && newun == address(0)) newun = to; stores the recipient of the first transferFrom call as newun and lets that transfer through. A router adding liquidity pulls tokens with transferFrom, so if the pair is that first recipient, the pair becomes newun. The source does not show which address that was for FairPluto.
  3. From then on, else require(to != newun, "please wait"); in transferFrom and require(to != newun, "please wait"); in transfer revert any transfer whose recipient is newun. A swap that sells the token sends it to the pair through the router, so that sale reverts.
  4. The owner can call transfernewun(address _newun) (onlyOwner) at any time. Setting it to an unused address lifts the block; setting it to the zero address makes the next transferFrom recipient the new newun.
  5. The header text promises "Ownership renounced" and locked liquidity. The code defines only transferOwnership and acceptOwnership and no renounce function, and the contract has no liquidity-lock logic.
  6. What the code allows is separate from what happened: the code does not show who added or removed liquidity. De.Fi's REKT database lists the token as an exit scam/honeypot.

Protocol details

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

Evidence

Same attack technique

Browse all hacks →
BNB Chain Voltage Loss not disclosed BNB Chain Setting Sun Loss not disclosed BNB Chain Quagmire Loss not disclosed BNB Chain JUSTMOON Loss not disclosed

Build your security review skills

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

Start Free Trial Explore attack classes