| Risk factor | Finding | Evidence | Date |
|---|---|---|---|
| Sellable | Yes | Transfer simulation | 22 Oct 2026 |
| Buy tax | 0% | Contract | 22 Oct 2026 |
| Sell tax | 0% | Contract | 22 Oct 2026 |
| Admin mint | Not present | Contract | 22 Oct 2026 |
| Transfers pausable | Not present | Contract | 22 Oct 2026 |
| Address blacklist | Not present | Contract | 22 Oct 2026 |
| Upgradeable proxy | No | Contract | 22 Oct 2026 |
| Source verified | Yes | Block explorer | 22 Oct 2026 |
| Top-10 holders | 90.4% | Holder distribution | 22 Oct 2026 |
| Liquidity locked | 25.7% until 11 Mar 2035 | LP holders · GoPlus SafeToken Locker | 22 Oct 2026 |
| Holders | 40929 | Token contract | 22 Oct 2026 |
| Deployed by | 0xeabf22…3f642a |
| Current owner | None — ownership renounced |
| Holders | 40,929 |
| Rank | Address | Share |
|---|---|---|
| #1 | 0xf97781…41acec | 54.45% |
| #2 | 0xda91ce…5ab71f | 7.50% |
| #3 | 0x0d0707…b492fe | 6.02% |
| #4 | 0x5a52e9…70efcb | 5.20% |
| #5 | 0xc882b1…84f071 | 4.72% |
This automated check looked at the mubarak contract's code and on-chain data as they stand today, and scored it 12 out of 18. A transfer simulation found the token can currently be sold, and no buy or sell tax was detected, meaning trades are not being skimmed by the contract at this time. No minting function was found, so there is no detected mechanism for the owner to create new tokens and dilute holders. No pause function and no blacklist function were detected either, which means no evidence was found that the contract owner can currently freeze transfers generally or block specific wallets from trading. The contract is not upgradeable through a proxy, so the logic deployed is what you see, and it was not detected that it could be swapped out later. The source code is verified on the block explorer, which allows anyone, including automated tools like this one, to read what the contract actually does rather than relying on trust alone. On the less favourable side, the top 10 holders control 90.4% of supply, which is a high concentration, and only 25.7% of liquidity is locked, albeit until 2035. A locked portion of liquidity reduces, but does not remove, the risk of that portion being pulled, and the unlocked majority remains a separate consideration.
It's important to be clear about what this check does not cover. It reads contract mechanics only: whether code allows certain actions, not whether the team behind the token is trustworthy, not whether the tokenomics make long-term sense, not any legal or regulatory status, and not the intent of whoever deployed or controls the contract. A clean mechanical reading does not speak to who holds the admin keys, how they plan to use them, or whether information outside the contract is accurate. This is also a point-in-time, automated assessment; contract permissions, liquidity locks, and holder distribution can all change after the check is run.
Before considering any further action, it would be worth looking at who actually holds the admin or owner wallet and whether those permissions have been renounced, checking the liquidity lock directly on the locker contract to confirm the terms and the portion actually locked, reviewing the holder list for wallets that look linked to each other or to the deployer, and searching independently for information about the team, any audits, and community discussion of the project. None of this should be treated as a recommendation to buy, hold, or sell the token.
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.