Quantum Audit Logo
Launch App

Early-stage security check — honeypot & rug-pull analysis

Is Lil Finder Guy a Scam?

LFGBase
Not verified This record has not gone through deep verification and is not being monitored. The score is a dated snapshot — the token’s risk can change at any time.Own this token? Put it under verification →
Last checked Sep 4, 2026 · 1 audit on recordNew Launch · 12h old
SummaryAI Copilot

This audit report is based on the analysis of a contract address on the Base network.

Read the full analysis
What raised the score
  • Ownership status UNKNOWN
  • Mint capability UNKNOWN
  • Liquidity not locked, but no owner/deployer address holds LP — market-depth risk, not rug risk
  • Liquidity < $50k
  • LP top1 unlocked holder = 100.0%
  • LP top3 unlocked holders = 100.0%
  • Token age < 24h
Exact factors
  • Ownership status UNKNOWN (owner could not be resolved)
  • Mint capability UNKNOWN (implementation ABI unreadable)
  • Liquidity not locked, but no owner/deployer address holds LP — market-depth risk, not rug risk
  • Liquidity < $50k ($33,384 across 7 pairs — thin market)
  • LP top1 unlocked holder = 100.0% (independent LP — depth risk, pool = 97% of DEX liquidity)
  • LP top3 unlocked holders = 100.0% (independent LP — depth risk, pool = 97% of DEX liquidity)
  • Token age < 24h (brand new — bot activity, unproven)

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

Early-stage analysis. This token has limited on-chain history (12h old). New tokens carry elevated risk — data may change rapidly. Always verify independently before investing.

Security Checklist

as of audit · Sep 44 of 7 checks passed
Contract verifiedVerified
OwnershipUnknown
MintUnknown
Liquidity lockNot locked
UpgradeabilityFixed code
HoneypotNone found
Buy / sell tax0% / 0%

Holders

as of audit · Sep 4, 2026
35.6%Contracts63.2%Everyone else
35.6%Contracts63.2%Everyone else
ContractsWalletsEveryone elseBubble area = share of supply
36.8%of supply sits with the top 10 holders
  • Contractstreasury, vesting, bridge, staking35.6%
  • Walletsanonymous holders, free to sell1.2%
  • Everyone elsethe rest of the supply63.2%
Effective concentrationwhat the score reads15.5%
How holder types affect the score

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

Liquidity

as of audit · Sep 4$33.4K across 7 pairs
LP tokensNot locked

The LP tokens of the analysed pool are not locked or burned, so whoever holds them can withdraw that liquidity.

Analysed pool$32.3KShare of depth96.7%
Top-1 Unlocked Holder100.0%
Top-3 Unlocked100.0%
Unlocked LP held by
0x0683…658c

No privileged address appears among these holders: the unlocked liquidity sits with independent providers, not with the deployer.

Security Findings

1 Info
Info

Lack of Verified Source Code

The source code for the contract at address 0xb200…bd01 on the Base network is not publicly verified. This prevents a thorough security audit and makes it impossible to ascertain the contract's intended functionality, security mechanisms, or potential vulnerabilities (7.1 Architecture, 7.2 Code Security, 7.3 Access Control, 7.4 Economic, 7.5 Governance, 7.7 Upgrades, 7.8 Operations). Users interacting with unverified contracts face significant risks due to the unknown nature of the code.I-01

Issue

The source code for the contract at address on the Base network is not publicly verified. This prevents a thorough security audit and makes it impossible to ascertain the contract's intended functionality, security mechanisms, or potential vulnerabilities (7.1 Architecture, 7.2 Code Security, 7.3 Access Control, 7.4 Economic, 7.5 Governance, 7.7 Upgrades, 7.8 Operations). Users interacting with unverified contracts face significant risks due to the unknown nature of the code.

Fix

The project team should verify the contract's source code on the Base network's block explorer (e.g., Basescan). This will enable transparency, allow for community review, and facilitate independent security audits. Providing the exact Solidity compiler version and optimization settings used during deployment is also crucial for accurate verification.

Status

Unresolved

Analysis

AI Copilotas of audit · Sep 4
Executive SummaryWhat the contract is and what the review found

This audit report is based on the analysis of a contract address on the Base network. Crucially, no source code was provided for review, which severely limits the scope and depth of the security assessment. The findings primarily highlight the risks associated with interacting with unverified contracts. A comprehensive security analysis, including identification of common vulnerabilities, is not possible without the contract's source code.

Technical8/10Low risk

Without access to the contract's source code, a comprehensive technical security analysis (7.1 Architecture, 7.2 Code Security, 7.3 Access Control) cannot be performed. This significantly hinders the ability to identify common vulnerabilities like reentrancy, integer overflows, or logic errors. The lack of verified source code on-chain prevents independent security review and increases operational risk, as the exact functionality and security properties remain unknown.

Governance1/10High risk

The economic and governance aspects (7.4 Economic, 7.5 Governance) of the contract cannot be assessed without source code. It is impossible to determine if the contract implements any governance mechanisms, tokenomics, or economic incentives, or if it is susceptible to oracle manipulation or flash loan attacks. This introduces an unknown level of economic risk for users interacting with the contract, as potential attack vectors or centralized control points cannot be identified.

Upgrades6/10Medium risk

The upgradeability status (7.7 Upgrades) of the contract cannot be determined without its source code. It is unknown whether the contract is part of a proxy pattern (e.g., UUPS, Transparent) or if it has any self-upgrade capabilities. This lack of transparency means users cannot ascertain the immutability or potential for future changes to the contract's logic, posing an operational risk where contract behavior could change unexpectedly.

Final RecommendationWhat to do about this score

It is strongly recommended that the source code for the contract at be verified on a block explorer (e.g., Etherscan, Basescan) to allow for proper security analysis and transparency.

Users should exercise extreme caution when interacting with unverified contracts, as their functionality and security properties are unknown and cannot be independently audited. Always prioritize contracts with publicly available and verified source code.

Contract & Record

1 audit on record
Type-
NetworkBase
Token age12h
Contract0xb200…bd01
Badge for your website
Lil Finder Guy security record badge

Free for any token on the record. It links to this page and always shows the current score and the date it was checked.

Audit History
  1. Sep 4, 202645Medium
  2. Aug 31, 202637Medium

Score changes are recorded as dated snapshots — history is append-only and cannot be edited.

Would You Like a More Detailed Audit of Lil Finder Guy?

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