Early-stage security check — honeypot & rug-pull analysis
0x171f…6d7c
This report is based on an audit request for the contract at 0x171f70d6f5b843d7656436af1abdfd646bca6d7c on Arbitrum. No source code was provided for analysis, which severely limits the scope and depth of this security assessment. Therefore, no specific vulnerabilities or strengths could be identified within the contract's logic. The risk levels are set to 'Low' by default due to the absence of findings, but this does not imply the contract is secure.
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.
The risk score reads depth across every pair. The volume figure and the volume-to-liquidity ratio elsewhere on this page describe only the pair this audit analysed, so the two are not directly comparable.
0xae36…2e250x59bd…36850x1d2a…158cNo privileged address appears among these holders: the unlocked liquidity sits with independent providers, not with the deployer.
Each 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
This token is brand new. Run a deeper AI-powered analysis of the contract code — free and instant.
Get Detailed Audit