Early-stage security check — honeypot & rug-pull analysis
EthereumThe audited contract is a standard ERC-20 token implementation utilizing OpenZeppelin libraries.
Read the full analysisEach factor is an on-chain fact recorded at the time of this analysis. The score is computed from them by a deterministic function, so the same contract returns the same score for anyone who runs the audit. How scores are computed
How the supply is spread across holders could not be read — the indexer's holder list does not add up to the supply. The indexer lists 128.8% of the supply in its top 10, which cannot be right. Check the largest holders on a block explorer, which reads current balances.
The risk score reads depth across every pair.
The LP tokens of the analysed pool are not locked or burned, so whoever holds them can withdraw that liquidity.
0x4c1c…d74aA privileged address — the deployer, the owner, or the token contract itself — is among these holders, so that party can withdraw liquidity.
0.0% of the pool's LP is burned or time-locked. 100.0% is held, unlocked, by the token's owner/deployer (0x4c1c…d74a) — they can pull that liquidity at any moment. This is the rug-pull path. Some pools are concentrated-liquidity (V3/V4) positions; shares above are by position as GoPlus reports them.
Check the lock's end date and beneficiary on the locker's own page before relying on it.
Acknowledged
The verified source code was reviewed and no issue rising to Informational severity or above was identified. This is a statement about the code that was read, not a guarantee: the review covers the published source only. Fact-layer checks (mint capability) were applied separately and feed the risk score.
Re-check after any contract upgrade or ownership change, both of which can alter behaviour without changing this page.
Acknowledged
The holder list from the security indexer adds up to 128.8% of supply, so it does not describe real balances. That happens with rebasing and reflection tokens, whose balances change without transfers, and with contracts that report balances they do not hold. Concentration is unknown and priced as an unknown — neither a whale nor safe.
Check the largest holders on the block explorer, which reads current balances.
Acknowledged
252 holders. Not listed by CoinGecko or any exchange GoPlus tracks. Nothing independent confirms who is behind this token, so every power its contract grants is scored at face value.
Match the contract address against the project's official channels before trading.
Acknowledged
Liquidity $104K (DexScreener, all pools). 24h trading volume $395K (DexScreener, all pools).
Size any position to the liquidity and daily volume shown — they set how much you can sell and at what price.
Acknowledged
A token issued by a project for use, governance or fundraising. Scored on its contract and market facts. The class itself adds no points; the contract and market facts decide the score. Basis: no class-specific evidence. Tokenomics — Supply: fixed — the contract has no mint function. Control: an owner that could not be resolved. Code: not upgradeable (no proxy). Fees: no buy or sell tax. Market: $104K of DEX liquidity across 1 pools. Launch: under a day of market history.
Check the project's own documentation for what the token is used for; this report covers what the contract allows.
Acknowledged
The token's oldest DEX pool is less than a day old. Age is not part of the risk score — a new token is not a risky one by default — but a short history means fewer trades and holder changes behind the facts in this report.
Re-check ownership, liquidity and holder distribution as the token matures; those are the facts that move early.
Acknowledged
The audited contract is a standard ERC-20 token implementation utilizing OpenZeppelin libraries. It contains no privileged roles, administrative backdoors, or complex logic, making it highly predictable and secure by design. The code adheres to standard interface specifications.
The architecture follows the standard ERC-20 pattern (7.1 Architecture) with robust implementation via OpenZeppelin (7.2 Code Security). There are no access control mechanisms (7.3 Access Control) as the contract is immutable and permissionless. The code is clean, readable, and lacks external dependencies that could introduce risk (7.6 External).
The contract lacks governance (7.5 Governance) and economic parameters (7.4 Economic) as it is a simple token. There are no minting or burning functions that could impact supply dynamics. Operations (7.8 Operations) are limited to standard token transfers.
The contract is not upgradeable (7.7 Upgrades). It is a static implementation, ensuring that the logic cannot be altered post-deployment. This eliminates risks associated with proxy patterns or administrative logic changes.
The contract is secure and follows best practices for a standard ERC-20 token.
No further action is required for the current implementation. Ensure that any future integrations or extensions to this token maintain the same level of simplicity and avoid adding unnecessary administrative functions.
Free for any token on the record. It links to this page and always shows the current score and the date it was checked.
Score changes are recorded as dated snapshots — history is append-only and cannot be edited.
This token is brand new. Run a deeper AI-powered analysis of the contract code — free and instant.
Get Detailed Audit Is this your token? Add your links and get it Verified
