KingSwap Honeypot

Reported loss Not disclosed
BNB Chain
Honeypot

What happened

KingSwap (KING) is a BEP-20 token on BNB Chain with an owner-controlled sell block hidden in its fee logic. Every transfer calls calculateFeesBeforeSend, which reverts with Error: Can not sell this token whenever the recipient is flagged in the PanCakeSwapReciever mapping, and the owner can flag any address, such as the PancakeSwap pair, with setPanCakeSwapReciever. Once the pair is flagged, holders can still buy but every sale reverts.

The fee settings are decorative: calculateFeesBeforeSend always returns the full amount and a zero fee. 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 99000e18 KING to the deployer, who is the owner.
  2. Every transfer and transferFrom runs _transfer, which calls calculateFeesBeforeSend(sender, recipient, amount) before crediting the recipient.
  3. That function contains if(PanCakeSwapReciever[recipient]){ revert("Error: Can not sell this token"); }.
  4. The owner can set the flag for any address with setPanCakeSwapReciever(_recipient, true). If the PancakeSwap pair is flagged, every sale sends tokens to the pair and reverts, while buys, where the pair is the sender, still succeed.
  5. The owner can clear the flag again at will. renounceWhitelist only disables the feeless-whitelist setters and does not touch this flag; only renounceOwnership would remove the power, and owner() still returned the deployer when read on 2026-09-30.

Protocol details

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

Build your security review skills

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