Chain
bsc
Primary network
Recovered
-
No recovery reported
Protocol Type
Exit Scam/Honeypot
Target category
What happened
A BNB Chain token record from April 2021 was identified by Token Sniffer as a honeypot. The available incident record states that the contract owner could disable transfers, a control that can prevent buyers from selling their tokens.
Technical Root Cause
Privileged contract controls could disable token transfers. If those controls are not transparently constrained, they can make a market one-way for holders and create a honeypot risk.
Classified under:
Access Control Attacks
·
Compare similar hacks →
Case & protocol details
Classification
Token / Honeypot
Protocol Type
Exit Scam/Honeypot
Affected asset / contract
ECLIPSE
Attack Timeline
The evidence preserved for this older record is limited: there is no independently verified loss amount, contract address, or technical postmortem in the source set. The reported risk is an owner-controlled transfer restriction. In a honeypot pattern, a token may appear tradeable when users buy it, while privileged logic can later block the transfers needed to sell or exit. This page deliberately does not infer a dollar loss or a more detailed exploit sequence without stronger primary evidence.
Audit assessment
Review priorities based on the documented failure pattern in Lunar Eclipse (April 2021).
Critical checks
- Verify every sensitive logic path is guarded by appropriate access controls and input validation - see the Access Control Attacks attack class for patterns
Evidence & learning
Attack pattern
Compare incidents →Sources and on-chain records
- report Report twitter.com
Practice this exploit pattern safely
Work through hands-on labs covering real exploit mechanics, review techniques, and defensive patterns.