SafeVice Honeypot

Reported loss Not disclosed
BNB Chain
Honeypot

What happened

SafeSpice (SAFESPICE) is a BEP-20 token on BNB Chain, recorded here as SafeVice, whose owner can mark any address as a blocked recipient. Every transfer passes through calculateFeesBeforeSend, which reverts with "Error: Can not sell this token" when the recipient is flagged in the PanCakeSwapReciever mapping. The owner sets that flag with setPanCakeSwapReciever, and unlike the fee-whitelist setters it is not switched off by renounceWhitelist.

Once the PancakeSwap pair is flagged, holders can still buy and move tokens between wallets, but any sell into the pair reverts. The txFee setting has no effect, because calculateFeesBeforeSend always returns the full amount and zero fee. De.Fi's REKT database lists SafeSpice as a honeypot.

How it happened

  1. The constructor mints the full 100,000,000 SAFESPICE supply to the deployer, who is also the owner and the feeDistributor.
  2. Buyers get SAFESPICE from the PancakeSwap pair; the pair is the sender, so the recipient check does not stop buys.
  3. The owner can call setPanCakeSwapReciever(pair, true). This setter has no canWhitelist gate, so it remains available even after renounceWhitelist.
  4. From then on, every transfer or transferFrom into the pair reaches calculateFeesBeforeSend, sees PanCakeSwapReciever[recipient] is true and reverts with "Error: Can not sell this token", so no holder can sell.
  5. The owner can clear the flag with the same setter. The flag has no owner exemption, so the owner would also have to clear it before selling into the pair. Ownership can be handed over or renounced, which would freeze the flag in its current state.

Protocol details

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

Build your security review skills

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