Early-stage security check — honeypot & rug-pull analysis
The target contract is not verified on the Base block explorer, rendering the source code inaccessible for security analysis.
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
Share held by contracts — treasury, vesting, bridge or staking — is discounted against share held by wallets when the score is computed: a contract cannot decide to sell the way an anonymous holder can, though it can still be drained or voted to sell. Effective concentration is the figure the risk score is actually calculated from.
Holder balances as recorded by the audit of Oct 26, 2026
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.
0x5ca3…ffc1A privileged address — the deployer, the owner, or the token contract itself — is among these holders, so that party can withdraw liquidity.
The contract source code is not verified on the block explorer, making it impossible to audit the logic for vulnerabilities or malicious backdoors.
Verify the contract source code on the block explorer to provide transparency to users.
Unresolved
The absence of public code prevents users from understanding the tokenomics, ownership privileges, and potential risks associated with the contract.
Publish the source code and provide documentation regarding the contract's functionality and ownership structure.
Unresolved
0.0% of the pool's LP is burned or time-locked. 100.0% is held, unlocked, by the token's owner/deployer (0x5ca3…ffc1) — 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 ten largest holders own 43.2% of supply. What remains: 22.8% in wallets, 20.5% in other contracts. 757 holders in total.
Watch the largest wallets that are not exchanges, pools or locks — those are the ones that can move the price.
Acknowledged
757 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 $100K (DexScreener, all pools). 24h trading volume $3.1M (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: mint capability could not be read. Control: an owner that could not be resolved. Code: not upgradeable (no proxy). Fees: no buy or sell tax. Market: $100K 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 target contract is not verified on the Base block explorer, rendering the source code inaccessible for security analysis. Consequently, it is impossible to verify the presence of backdoors, minting functions, or tax mechanisms. Investors should exercise extreme caution as the lack of transparency is a significant indicator of potential risk.
7.1 Architecture, 7.2 Code Security, 7.3 Access Control, 7.6 External: All technical aspects are opaque due to the lack of verified source code. Without bytecode analysis, it is impossible to determine if the contract adheres to standard ERC-20 patterns or contains malicious logic. The inability to inspect the implementation prevents any assessment of security controls or external dependencies.
7.4 Economic, 7.5 Governance: The economic model and governance structure are entirely hidden from the user. There is no way to verify if the owner has the ability to pause trading, blacklist addresses, or modify supply parameters. Investors must assume the highest level of risk regarding potential rug-pulls or arbitrary economic manipulation.
7.7 Upgrades, 7.8 Operations: It is unknown if the contract utilizes a proxy pattern or is immutable. If the contract is a proxy, the implementation could be swapped at any time by an owner, leading to total loss of funds. Operational security cannot be verified without access to the deployment configuration.
Do not interact with this contract. The lack of verified source code is a critical red flag that prevents any meaningful security assurance.
Without transparency, there is no way to distinguish this contract from a malicious actor or a honeypot. If you are considering an investment, wait for the developers to verify the contract on the block explorer. Perform thorough due diligence on the project's social presence and liquidity locks before considering any interaction.
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
