Olympus Honeypot
What happened
This Olympus (Olympus) token is a BEP-20 token on BNB Chain, unrelated to OlympusDAO, that blocks every sale into its liquidity pool. The first transferFrom the contract sees, normally the PancakeSwap router pulling the owner's tokens into the new pair when liquidity is added, stores that recipient in a variable named newun. After that, both transfer and transferFrom revert with please wait whenever the recipient is newun, so holders can buy from the pool but cannot sell back into it.
The owner can repoint newun at any time with transfernewun. The same newun trap was documented in April 2021 in BNB Chain tokens such as SafeRocket; De.Fi's REKT database lists this Olympus token as an exit scam/honeypot, with no loss figure.
How it happened
- The constructor credits the whole supply,
10000000000000000000raw units (100,000,000,000Olympusat 8 decimals), to the owner;newunstarts asaddress(0). - When liquidity is added through the PancakeSwap router, the router calls
transferFrom(owner, pair, amount). Becausenewun == address(0), the lineif(from != address(0) && newun == address(0)) newun = to;records the pair asnewunand lets that first transfer through. - Buys still work: the pair sends tokens to the buyer with
transfer, and the buyer is notnewun. - A sell sends tokens to the pair, through the router's
transferFromor a directtransfer. Both checkrequire(to != newun, "please wait"), so every sell reverts with a message that suggests a temporary delay. transfernewun(address _newun)isonlyOwner, so the owner can move the block to another address, which would reopen sells, or reset it to zero so the nexttransferFromrecipient is blocked instead.- Removing liquidity sends tokens out of the pair rather than into it, so the block does not stop whoever holds the LP tokens from withdrawing the pool's BNB.
clearCNDAO()lets the owner withdraw any BNB held by the token contract itself. There is norenounceOwnership; ownership changes only when a new address callsacceptOwnershipaftertransferOwnership.
Protocol details
Evidence
- report @Token_Sniffer incident report twitter.com
- address Olympus (Olympus) verified contract source, BscScan bscscan.com
- analysis BSC-SCAM: Stealthy Liquidity Pool Block on PancakeSwap, CryptoT3ddyBear cryptot3ddybear.gitlab.io
- analysis Sourcify match, chain 56, 0x65698755f47fd63d0b9228f6c3a0b2c75bc2184c repo.sourcify.dev
Build your security review skills
Work through hands-on labs covering real exploit mechanics, review techniques, and defensive patterns.