Early-stage security check — honeypot & rug-pull analysis
BNB ChainThe 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
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 20, 2026
The risk score reads depth across every pair.
The LP tokens of the analysed pool are locked or burned.
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/owner authority, mint capability, LP lock/burn state, holder concentration) 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 ten largest holders own 28.4% of supply. Of that, 18.0% in DEX pools — not holders that can sell, so excluded from the concentration score. What remains: 10.5% in wallets, 0.0% in other contracts. 961 holders in total.
Watch the largest wallets that are not exchanges, pools or locks — those are the ones that can move the price.
Acknowledged
961 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
100.0% of the pool's LP is burned or time-locked. 100.0% is locked in PinkLock02 until 03 Nov 2026 (13 days). Until then nobody — the project included — can withdraw it unless the locker contract itself is flawed; after that date the lock's owner can. That date is close: treat it as short-term protection. 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
Liquidity $156K (DexScreener, all pools). 24h trading volume $7.7M (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: nobody (ownership renounced). Code: not upgradeable (no proxy). Fees: no buy or sell tax. Market: $156K 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
The contract is a standard ERC-20 token implementation utilizing OpenZeppelin libraries. Ownership has been renounced, meaning no administrative functions can be executed, effectively locking the contract configuration. The code follows established patterns and contains no custom logic that could introduce vulnerabilities.
The architecture follows the standard OpenZeppelin ERC-20 implementation, ensuring high reliability and compatibility. 7.1 Architecture is robust, 7.2 Code Security is high due to library usage, and 7.3 Access Control is effectively disabled via renouncement. 7.6 External dependencies are limited to standard, audited OpenZeppelin contracts.
7.4 Economic and 7.5 Governance factors are not applicable as the contract is a simple token with no minting, burning, or fee mechanisms. The renounced ownership ensures no central entity can alter the economic parameters. 7.8 Operations are straightforward as the token functions as a standard store of value.
7.7 Upgrades are not supported as the contract is not a proxy. The code is immutable, providing security against unauthorized logic changes. This design choice eliminates risks associated with upgradeable patterns.
The contract is secure and follows best practices for a non-upgradeable ERC-20 token.
No further action is required as ownership is renounced and the code is standard.
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? Publish your own audit on this page
