On-chain security analysis — is it a scam or legit?
This report is based on an audit request for a contract at the specified address.
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 Sep 4, 2026
The 7 remaining pairs hold $53 between them and are not listed. 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.
0x68d5…bc200x3b0c…3fcd0xcad1…f7bf0x84ac…f1850xbf3a…19c90xc115…97ce0x70b6…38b60xee57…3d240x189d…1e630xef28…7342No privileged address appears among these holders: the unlocked liquidity sits with independent providers, not with the deployer.
The source code for the contract at was not provided for analysis. This prevents any form of static or dynamic code analysis.
Provide the full and verified Solidity source code for the contract. It is best practice to verify contract source code on block explorers.
Unresolved
Without the contract's source code, it is impossible to identify common technical vulnerabilities such as reentrancy, integer overflows/underflows, access control flaws, or logic errors (7.2 Code Security, 7.3 Access Control).
Ensure that the contract's source code is made available for a thorough security review to identify and mitigate potential technical risks.
Unresolved
The absence of source code prevents an assessment of the contract's economic model, governance mechanisms, or upgradeability patterns (7.4 Economic, 7.5 Governance, 7.7 Upgrades). This leaves potential risks related to economic manipulation, centralized control, or upgrade safety unaddressed.
Provide the source code to allow for a comprehensive review of the contract's economic design, governance structure, and upgrade path, if any.
Unresolved
This report is based on an audit request for a contract at the specified address. However, no source code was provided for analysis, preventing a comprehensive security assessment. Therefore, no vulnerabilities could be identified or confirmed.
A technical security assessment could not be performed as the contract's source code was not provided. Without access to the Solidity code, it is impossible to analyze for common vulnerabilities such as reentrancy, integer overflows, or access control flaws (7.2 Code Security, 7.3 Access Control). Therefore, no specific strengths or weaknesses in the contract's implementation can be reported.
Without the contract's source code, it is impossible to analyze its economic model, tokenomics, or governance mechanisms (7.4 Economic, 7.5 Governance). Potential risks related to economic manipulation, flash loan attacks, or centralized control cannot be identified. Any assessment of economic stability or governance decentralization is precluded.
The upgradeability status of the contract could not be determined without its source code (7.7 Upgrades). It is unknown if the contract implements a proxy pattern (e.g., UUPS, Transparent) or if it is immutable. Therefore, risks associated with upgrade safety, such as storage collisions or logic errors during upgrades, cannot be assessed.
To enable a comprehensive security audit, it is crucial to provide the full and verified source code for the contract.
Without the source code, no security guarantees can be made, and any potential vulnerabilities remain unknown. It is strongly recommended to publish the source code on block explorers and ensure it matches the deployed bytecode.
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.
Our AI-powered scanner gives you a deeper, real-time smart contract analysis — free, with every scoring factor shown.
Get Detailed Audit Is this your token? Publish your own audit on this page
