SaintElon Honeypot
What happened
SaintElon (ELON) is a BEP20 token on BNB Smart Chain whose transfer code reverts any transfer sent to one stored address, newun. The first transferFrom call made while newun is empty stores that call's recipient there, and from then on transfer and transferFrom revert with "please wait" for that recipient. If the stored address is a trading pair, buying still works because the pair is the sender, while selling reverts because the pair is the recipient.
The owner can overwrite newun through transfernewun. De.Fi's REKT database lists the token as an Exit Scam/Honeypot and says the contract owner could restrict users from selling. A published write-up by CryptoT3ddyBear describes the same newun condition in other BSC tokens and does not mention SaintElon.
How it happened
- The constructor mints the whole supply to the deployer, who is also
owner:balances[owner] = _totalSupply;. transferFromrunsif(from != address(0) && newun == address(0)) newun = to; else require(to != newun, "please wait");. The firsttransferFromcall made whilenewunis empty therefore stores its recipient innewun. Which address that was on-chain is not shown by the source.- After that,
transferrunsrequire(to != newun, "please wait");andtransferFromruns the samerequire. Neither has an exemption for the owner or for any other address, so every transfer tonewunreverts. - If
newunis a liquidity pair, a buy moves tokens out of the pair to the buyer and is not affected. A sell makes the router calltransferFrom(holder, pair, amount), sotoequalsnewunand the call reverts. The balance of the holder is never debited. transfernewun(address _newun) public onlyOwnerlets the owner replacenewun. Pointing it at an unused address lifts the block. Setting it to the zero address re-arms the capture, and the nexttransferFromstores a new recipient.- What happened on-chain (which address
newunheld, whether holders' sells reverted, whether liquidity was removed) is not established by the opened sources. De.Fi's REKT database lists the token as a honeypot.
Protocol details
Evidence
- report @Token_Sniffer incident report twitter.com
- address BscScan verified source, SaintElon 0x5ca65a51c1ae3dd5b5ed43fd2f8c607a098bcc15 bscscan.com
- analysis Scam explained: BSC stealthy LP block (CryptoT3ddyBear) cryptot3ddybear.gitlab.io
- analysis Sourcify match, chain 56, SaintElon repo.sourcify.dev
Build your security review skills
Work through hands-on labs covering real exploit mechanics, review techniques, and defensive patterns.