Early-stage security check — honeypot & rug-pull analysis
This report is based on an audit request for the contract at 0xa1af1beabd885181a4927f91d66dfe2140cb077c on the Base network.
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 14, 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.
0xdc2e…1fd80x9bd2…168c0.0% of the pool's LP is burned or time-locked. 100.0% is held, unlocked, by 1 address(es) other than the owner/deployer. One of them — a contract, 0xdc2e…1fd8 — holds 100.0% and can remove that share at once; who controls it is not visible on-chain, so it is not treated as an independent provider.
Check the lock's end date and beneficiary on the locker's own page before relying on it.
Acknowledged
The audit was requested for the contract at address on the Base network. However, no Solidity source code was supplied for analysis. Without the source code, a detailed security audit, including vulnerability identification, architectural review, and economic analysis, cannot be performed.
Provide the complete and verified Solidity source code for the contract. This includes all dependent libraries and imported contracts, along with the correct compiler version and optimization settings used during deployment. This will enable a full and accurate security assessment.
Unresolved
The ten largest holders own 48.8% of supply. What remains: 21.9% in wallets, 26.8% in other contracts. 1,053 holders in total.
Watch the largest wallets that are not exchanges, pools or locks — those are the ones that can move the price.
Acknowledged
1,053 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 $114K (DexScreener, all pools). 24h trading volume $129K (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: $114K of DEX liquidity across 1 pools. Launch: 1 days 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 1 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
This report is based on an audit request for the contract at 0xa1af1beabd885181a4927f91d66dfe2140cb077c on the Base network. No Solidity source code was provided for analysis. Therefore, a comprehensive security audit could not be performed, and no specific vulnerabilities or strengths can be identified. The findings are limited to an informational note regarding the absence of source code.
Due to the absence of Solidity source code, a technical analysis of the contract's architecture (7.1), code security (7.2), and access control mechanisms (7.3) could not be performed. Without the code, it is impossible to identify common vulnerabilities such as reentrancy, integer overflows, or improper authorization checks. Therefore, no strengths or issues can be reported in this section.
Without access to the contract's source code, an assessment of its economic model (7.4), governance structure (7.5), and interactions with external protocols (7.6) is not possible. This prevents the identification of potential economic exploits, governance attack vectors, or risks arising from external dependencies. No specific strengths or issues can be reported.
The upgradeability aspects (7.7) and operational procedures (7.8) of the contract cannot be determined without the source code. It is unknown if the contract employs a proxy pattern (e.g., UUPS, Transparent) or if it is immutable. Consequently, potential upgrade risks or operational security considerations cannot be assessed.
To enable a comprehensive security assessment, it is crucial to provide the full Solidity source code for the contract at .
This will allow for a thorough analysis of its architecture, security mechanisms, economic model, and upgradeability, leading to actionable security recommendations.
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? Publish your own audit on this page
