Trade with care. Read the warnings first.
Top 10 holders hold 100% of the tokens in circulation.
Scanned 3d ago. Scan again before you trade.
- FAILHolder concentration
- FAILDangerous functions
- WARNHoneypot
DexProof recorded EXPLOITBNKR as CAUTION on Robinhood Chain under formula v2.0.1, in verdict #1283 published 27 Oct 2026 (UTC). Of 28 checks, 13 passed, 4 warned, 2 failed and 9 could not be run.
Trade with care. Read the warnings first.
Top 10 holders hold 100% of the tokens in circulation.
Scanned 3d ago. Scan again before you trade.
Price
—
Liquidity
—
Volume 24h
—
FDV
—
Buys 24h
—
Age
—
Top 10 holders hold 100% of the tokens in circulation.
The largest holder is , a contract, holding 89.1% of the tokens in circulation on its own. Against total supply, the top 10 hold 15.0%. Liquidity pools hold 85.0% of total supply, and we leave them out of the tokens in circulation. The top 10 share also moves when pool liquidity moves, even if no holder trades.
The token contract has privileged powers: limit change, a switch that can block transfers or selling, privileged low-level code we couldn't read.
Someone can still use them, or we couldn't tell who controls them. The code still contains these, but they can no longer be used: supply mint (initialize can only run once and already has), amm route change (initialize can only run once and already has), initialization (initialize can only run once and already has).
We couldn't finish the sell test on the other exchanges we checked.
We couldn't get a clear result from any pool we tested, so we can't say whether this token can be sold.
We couldn't work out who controls this token's liquidity on this scan.
Missing data limits the verdict. A pool we couldn't read is not a pool we cleared. This describes what we could see, not the token.
This contract still has an active owner: .
The same code has been deployed 15 times, which looks like a copycat pattern.
These are gaps in what we could see, not problems found in this token.
We couldn't work out which wallet funded the creator, so there was no funder to check for past rugs.
We could only trace 0.0% of this pool's liquidity to a holder, so we can't say who controls it.
We couldn't find the wallet that first funded this deployer, so we have no funding trail to check.
We could not read this token's market data, so we did not measure its pool depth.
That is a gap in what we could see, not a finding about the token.
We don't have the market data needed to compare this token's value at full supply with its liquidity.
We don't have the volume and liquidity figures needed to check turnover.
We don't have the market data needed to check for wash trading.
A contract created this token, so we can't see the person behind it.
So we can't check whether it changed fees or limits.
We could not find when this token's pool was created.
This token does not share its name and symbol with any real tokenized share.
The explorer has not tagged this contract as a scam.
No liquidity removal by the wallet recorded as this token's creator from its own pool.
The creator's recent history has no removal calls either.
This token is not on our list of confirmed rugs.
This token has no honeypot mark in our records.
This token has no pump-and-dump mark in our records.
This deployer has no earlier launches on record.
This contract's code is fixed.
We found no standard upgrade setup on it.
This contract's source is partially verified on the explorer.
The code matches, but the compiler metadata does not. This is about its implementation at .
No paid promotion found on DexScreener.
This contract was 93 days old at this scan.
Launched on Doppler.
Our launchpad records don't show it graduating, but it has a DEX pool. The raise on record is too old to compare against, so how much of it the creator bought is unknown.
The source is partially verified through a bytecode match, so the code can be read.
We could not match it to a known template.