KINGLER Honeypot

Reported loss Not disclosed
BNB Chain
Honeypot

What happened

De.Fi's REKT database lists KINGLER (Kingler Detect) as an Exit Scam/Honeypot on Binance, noting that the contract owner could disable the transfer function, which restricted users in selling their tokens. In the verified source the control is narrower than switching off all transfers: the owner can flag any address as a blocked recipient with setPanCakeSwapReciever, and every transfer whose recipient is flagged reverts with "Error: Can not sell this token". The token contract at 0xfeb5f055…861845 does not show on its own which addresses were flagged, so what the code allows is described here separately from what the listing reports.

How it happened

  1. The constructor mints the whole supply to the deployer: _transferTO(msg.sender, 1000000000000e18);. The deployer is the initial _owner, and as of the 2026-09-30 on-chain read owner() still returns the deployer address 0x410cedc7…6dcdeb.
  2. The owner can call setPanCakeSwapReciever(address _recipient, bool _feeless) public onlyOwner, which stores PanCakeSwapReciever[_recipient] = _feeless; for any address. Unlike the whitelist setters it has no canWhitelist check, so renounceWhitelist() does not switch it off.
  3. Every transfer and transferFrom goes through _transfer, which first debits the sender (_balances[sender] = _balances[sender].sub(amount, ...)) and then calls calculateFeesBeforeSend(sender, recipient, amount).
  4. If the recipient is flagged, that function runs revert("Error: Can not sell this token");. The revert rolls back the whole call, including the balance debit, so the holder keeps the tokens but the transfer fails. Any recipient that is not flagged gets return (amount, 0);, so those transfers go through with no fee.
  5. The flag applies to the recipient of the transfer, not to a named holder. If a trading pair or router address that receives tokens during a sale is flagged, sales to it fail while transfers to unflagged addresses continue. The code does not show which addresses were flagged, and no transaction was opened that shows the owner calling setPanCakeSwapReciever.

Protocol details

Classification Token
Protocol Type Exit Scam/Honeypot
Affected asset / contract Kingler Detect

Evidence

Same attack technique

Browse all hacks →
BNB Chain Coinlix Loss not disclosed Ethereum safe-x.space Loss not disclosed BNB Chain ZirgonYield Loss not disclosed BNB Chain WhiteX Finance 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