NEPTUNE Token Honeypot

Reported loss Not disclosed
BNB Chain
Honeypot

What happened

NEPTUNE Token (NPTN) is a BEP-20 token on BNB Chain whose transfer function blocks every holder by default. While the owner-controlled TIME flag is on, which it is from deployment, any transfer that is not from the owner, to the owner, or out of the stored pancake address reverts with a fake message saying sales are limited to one per 30 minutes. No timer exists in the code.

Tokens can flow out of the pancake address to buyers, but holders cannot sell or even send tokens to another wallet. The owner can also set a sell cap, block individual wallets outright and set a fee of up to 10%. De.Fi's REKT database lists NPTN as an exit scam/honeypot, with no loss figure.

How it happened

  1. The constructor mints 1,000,000,000,000,000 NPTN to the deployer, who is the owner. TIME starts as true.
  2. Every transfer the owner sends stores its recipient as pancake (if(sender == owner()){ pancake = recipient; }), and addPancake(address) sets it directly. When the owner's liquidity deposit goes to the PancakeSwap pair, the pair becomes pancake.
  3. _transfer then applies if(sender != owner() && recipient != owner() && sender != pancake && TIME == true){ revert("FOR VALUE PROTECTION, YOU CAN ONLY SELL 1 Sale PER 30 MIN"); }. A buy (sent from pancake) passes, while a sell or wallet-to-wallet transfer by a holder reverts. No timestamp is ever compared.
  4. The owner can lift or restore the block with setTIME(bool). It can also cap transfers into any address flagged with POOL() using fire(uint256) (require(amount <= MAX, 'Syntax Error. Please Re-Submit Order')), and block a wallet completely with GTYA(address, true), because require(amount <=0, "bots......") can never pass when _transfer already requires amount > 1000.
  5. setFee allows txFee up to 100 out of 1000 (10%), despite the comment "capped to 1%". The sender is debited the full amount, and the fee goes to feeDistributor if one is set. Ownership can be renounced via renounceOwnership(), but the on-chain owner is still the deployer.

Protocol details

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

Evidence

Same attack technique

Browse all hacks →
BNB Chain LuckyDoge Loss not disclosed BNB Chain WhereLambo Loss not disclosed BNB Chain WOODEN Token Loss not disclosed BNB Chain GEMROCKET 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