| Risk factor | Finding | Evidence | Date |
|---|---|---|---|
| Sellable | Yes | Transfer simulation | 27 Oct 2026 |
| Buy tax | No data | Contract | 27 Oct 2026 |
| Sell tax | No data | Contract | 27 Oct 2026 |
| Admin mint | Not present | Contract | 27 Oct 2026 |
| Transfers pausable | Not present | Contract | 27 Oct 2026 |
| Address blacklist | Not present | Contract | 27 Oct 2026 |
| Upgradeable proxy | No | Contract | 27 Oct 2026 |
| Source verified | Yes | Block explorer | 27 Oct 2026 |
| Top-10 holders | 0.5% | Holder distribution | 27 Oct 2026 |
| Liquidity locked | No | LP holders | 27 Oct 2026 |
| Holders | 11223471 | Token contract | 27 Oct 2026 |
| Deployed by | 0x074a2b…d4c25d |
| Current owner | None — ownership renounced |
| Holders | 11,223,471 |
| Rank | Address | Share |
|---|---|---|
| #1 | 0x55906a…741cef | 0.52% |
| #2 | 0x93f16f…a75e54 | 0.00% |
| #3 | 0x81d789…17433a | 0.00% |
| #4 | 0xc7029e…570171 | 0.00% |
| #5 | 0x460e55…44f5a2 | 0.00% |
This automated check looked at the contract code for MNEB on BSC and found no honeypot behaviour: a simulated transfer went through, meaning holders are currently able to sell. No admin minting function was detected, so the owner does not appear able to create new tokens and dilute holders. Transfers cannot be paused by the contract owner, and there is no address blacklist function, meaning no on-chain mechanism was found that would let the owner freeze a specific wallet's tokens. The contract is also not an upgradeable proxy, which means its logic cannot be swapped out for different code after the fact without deploying a new contract entirely. The source code is verified on the block explorer, so what's published matches what's running, and it can be read by anyone. One point worth flagging: liquidity is not locked, meaning whoever controls the liquidity pool tokens could, in principle, withdraw that liquidity at any time, which would affect the ability to trade the token at a stable price. Top-10 wallets hold a small 0.5% of supply, which on its own does not indicate concentrated control by a small number of addresses.
It's important to be clear about what this check does not cover. This is an automated read of contract mechanics only — it does not assess who the team behind MNEB is, whether their stated plans or roadmap are credible, how the token's supply and incentives are structured, whether any legal or regulatory obligations apply, or the intent behind the project. A clean mechanical result tells you the code doesn't contain certain common traps; it says nothing about the people running it or the broader risks of the project.
Before putting any money in, it's worth looking at where the liquidity pool tokens actually sit and who controls them, since unlocked liquidity means that party has latitude to remove it. Check whether buy and sell taxes apply in practice, since this report has no data on either. Look into who the team is, whether they're identifiable, and what independent sources (not just the project's own channels) say about the project's history and conduct. Consider the token's distribution and release schedule, and treat any findings here as one input among several, not a conclusion on their own.
Contracts change after they are checked. Tell us where to reach you and we will say when this one does. Free for three contracts, no account.
We checked 18 points out of 100.
The other 82 are where money is usually lost: who the team is, where the tokens sit, what the documents actually say, and what the project chose not to put on its front page.