Don't trade this token.
This token's creator removed liquidity from this token's pool.
Scanned 2d ago. Scan again before you trade.
- FAILDeployer pulled liquidity
- FAILConfirmed rug
- FAILLP custody
DexProof recorded MuseFi as CRITICAL on Robinhood Chain under formula v2.0.1, in verdict #1436 published 28 Oct 2026 (UTC). Of 28 checks, 15 passed, 4 warned, 4 failed and 5 could not be run.
Don't trade this token.
This token's creator removed liquidity from this token's pool.
Scanned 2d ago. Scan again before you trade.
Price
—
Liquidity
—
Volume 24h
—
FDV
—
Buys 24h
—
Age
—
This token's creator removed liquidity from this token's pool.
It made 1 withdrawal on Uniswap V4, and that withdrawal closed the position completely.
This token is on our list of confirmed rugs.
About $149,082 either left its pool or is stuck inside it.
The largest liquidity provider, (a smart-account wallet), controls 100.0% of this pool's liquidity and can withdraw it at any moment.
It is not the deployer. Renouncing ownership does not protect against this. None of this V4 pool's liquidity is burned or locked. This pool is on Uniswap V4 and holds 58.6% of the liquidity we could read.
Top 10 holders hold 52% of the tokens in circulation.
The largest holder is , a plain wallet, holding 46.6% of the tokens in circulation on its own.
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. Sells on this pool go through a swap hook. Our code check found functions that let its owner set a router list, a whitelist or a blacklist. We can't see whether the owner has used them.
We couldn't read some checks on this scan, so the verdict is limited.
A failed read is not a clean result. This describes what we could see, not the token.
This deployer is a new wallet funded by another new wallet, a common setup before a rug.
This token's code matches an earlier creator liquidity removal on 0x0d5a…5d05.
We haven't verified that the same creator is behind both.
These are gaps in what we could see, not problems found in this token.
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.
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.
Nothing on record ties , the wallet that funded the creator, to a past rug on Robinhood Chain.
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.
Ownership was renounced.
The owner is the zero or dead address.
This contract's code is fixed.
We found no standard upgrade setup on it.
This contract's source is verified on the explorer, but it was matched from another address with identical bytecode, not proven against this one.
We found no privileged powers in the token contract's code.
We looked at its audited source and compiled code.
We saw no fee or limit changes by the deployer in the transactions we searched.
We only looked at the deployer's recent history, so changes by a separate fee owner would not show.
No active paid boosts.
DexScreener has paid listing services on record for this token (a token profile), which is common for a launched token.
This contract was 33 days old at this scan.
No launchpad deployed this token.
It was deployed directly, which counts neither for nor against it. The on-chain checks decide this one.
The source is verified, so anyone can read the code.
We could not match it to a known template.
This token trades in V4 pools that run a hook, a contract that executes on swaps. Here is what Uniswap's public hook list says about each one. It describes the hook, not this token.
Found by reading the hook's code. Whether the owner has used these controls is not something this scan can see.
We could not read Uniswap's hook list just now, so we cannot say whether this hook is described there.