Quantum Audit Logo
Launch App

On-chain security analysis — is it a scam or legit?

Is OKZOO Safe?

AIOTBNB Chain
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 record
Chart
Low RiskHow is this score calculated?
How the score breaks downratings: 10 is safest
Technical10/10Governance4/10Upgrades6/10Checks passed3 of 5Findings1 Low · 2 Info3
SummaryAI Copilot

The OkzooToken contract is a standard ERC-20 token implementation, inheriting directly from OpenZeppelin's battle-tested ERC20 contract.

Read the full analysis
What raised the score
  • Ownership status UNKNOWN
  • Top-10 concentration > 30%
  • Liquidity not locked, but no owner/deployer address holds LP — market-depth risk, not rug risk
  • 1 Low finding(s) from audit
Exact factors
  • Ownership status UNKNOWN (owner could not be resolved)
  • Top-10 concentration > 30% (81.9% total → 41.4% effective; 14.5% in EOAs, 67.4% in contracts — moderate)
  • Liquidity not locked, but no owner/deployer address holds LP — market-depth risk, not rug risk
  • 1 Low finding(s) from audit

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

Security Checklist

as of audit · Sep 43 of 5 checks passed
Contract verifiedVerified
OwnershipUnknown
MintNo mint
Liquidity lockNot locked
UpgradeabilityFixed code

Holders

as of audit · Sep 4, 2026
67.4%Contracts14.5%Wallets18.1%Everyone else
67.4%Contracts14.5%Wallets18.1%Everyone else
ContractsWalletsEveryone elseBubble area = share of supply
81.9%of supply sits with the top 10 holders
  • Contractstreasury, vesting, bridge, staking67.4%
  • Walletsanonymous holders, free to sell14.5%
  • Everyone elsethe rest of the supply18.1%
Effective concentrationwhat the score reads41.4%
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$1.17M across 9 pairs
Show 3 more pairs

The risk score reads depth across every pair.

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$1.14MShare of depth97.2%
Top-1 Unlocked Holder27.3%
Top-3 Unlocked61.1%
Unlocked LP held by
0x2fbe…da9a0x9571…bf640xbc7a…3e710x5c71…39c90x2799…64c30x0360…692a0x1262…3df00x1498…d27e0x5fbe…94c40x4cc4…2ee2

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

Security Findings

1 Low2 Info
Low

Lack of Administrative Control Functions

The OkzooToken contract does not include any administrative control functions such as pause, blacklist, or owner-restricted minting/burning capabilities beyond the initial constructor mint. While this design choice minimizes centralization risk and potential attack vectors associated with privileged roles, it also means there is no mechanism to halt transfers in an emergency (e.g., a critical bug in a DeFi protocol interacting with the token) or to recover tokens sent to incorrect addresses.L-01

Issue

The OkzooToken contract does not include any administrative control functions such as pause, blacklist, or owner-restricted minting/burning capabilities beyond the initial constructor mint. While this design choice minimizes centralization risk and potential attack vectors associated with privileged roles, it also means there is no mechanism to halt transfers in an emergency (e.g., a critical bug in a DeFi protocol interacting with the token) or to recover tokens sent to incorrect addresses.

Fix

Assess whether the absence of administrative controls aligns with the project's long-term strategy and risk tolerance. If emergency response capabilities are deemed necessary, consider implementing a separate governance or multi-sig controlled contract that can interact with the token, or deploying a token with such features from the outset. For this specific contract, no changes are recommended if the current design is intentional.

Status

Unresolved

Info

Reliance on OpenZeppelin Standard Implementation

The OkzooToken contract inherits directly from OpenZeppelin's ERC20 contract, which is a widely used and thoroughly audited library. This significantly reduces the likelihood of common ERC-20 vulnerabilities such as reentrancy, integer overflows/underflows, and incorrect token accounting. The custom logic is limited to the constructor, which performs an initial mint.I-01

Issue

The OkzooToken contract inherits directly from OpenZeppelin's ERC20 contract, which is a widely used and thoroughly audited library. This significantly reduces the likelihood of common ERC-20 vulnerabilities such as reentrancy, integer overflows/underflows, and incorrect token accounting. The custom logic is limited to the constructor, which performs an initial mint.

Fix

No specific recommendation is required as this is a strength. Continue to monitor OpenZeppelin's security advisories for any potential issues in the base contracts, although this is generally handled by the OpenZeppelin team.

Status

Unresolved

Info

Fixed Token Supply After Initial Mint

The total supply of OkzooToken is determined solely by the mintAmount parameter provided during the contract's deployment in the constructor. There are no functions available to mint additional tokens or burn tokens (beyond the internal _burn function which is not exposed externally) after the initial deployment. This results in a fixed supply token.I-02

Issue

The total supply of OkzooToken is determined solely by the mintAmount parameter provided during the contract's deployment in the constructor. There are no functions available to mint additional tokens or burn tokens (beyond the internal _burn function which is not exposed externally) after the initial deployment. This results in a fixed supply token.

Fix

Ensure that the initial mintAmount is carefully chosen and verified, as it cannot be altered post-deployment. This fixed supply characteristic is generally a security strength, preventing arbitrary inflation, but it also means the token's supply cannot be adjusted to respond to future economic or protocol needs.

Status

Unresolved

Analysis

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

The OkzooToken contract is a standard ERC-20 token implementation, inheriting directly from OpenZeppelin's battle-tested ERC20 contract. It features a single constructor that initializes the token's name, symbol, and mints an initial supply to a specified recipient. The contract exhibits a high degree of security due to its reliance on well-audited OpenZeppelin libraries and its minimal custom logic. No critical or high-severity vulnerabilities were identified.

Technical10/10Low risk

The technical architecture (7.1) is straightforward, implementing a standard ERC-20 token. Code security (7.2) is robust, primarily due to the use of OpenZeppelin's ERC20 library, which incorporates best practices for integer arithmetic and common attack vectors. For instance, unchecked blocks are safely guarded by require statements to prevent underflow in functions like _transfer and _burn. Access control (7.3) is minimal, limited to standard ERC-20 permissions, which reduces the attack surface.

Governance4/10Medium risk

The economic model (7.4) is simple: a fixed supply token minted once at deployment. There are no complex DeFi primitives or external dependencies (7.6) that could introduce economic exploits or oracle manipulation risks. Governance (7.5) is not present within this contract, as there are no administrative roles or upgrade mechanisms. This design choice simplifies the contract and reduces centralization risks associated with privileged roles.

Upgrades6/10Medium risk

The contract is not designed to be upgradeable (7.7), meaning its logic is immutable once deployed. This eliminates upgrade-related risks such as proxy implementation bugs or administrative key compromise for upgrades. However, it also means that any discovered vulnerabilities or desired feature changes would necessitate a new contract deployment and migration.

Final RecommendationWhat to do about this score

The OkzooToken contract is a secure and straightforward ERC-20 implementation.

It is recommended to ensure that the deployment parameters, specifically the mintAmount and recipient in the constructor, are thoroughly verified before deployment, as these are immutable. Given the lack of administrative controls, consider the implications for emergency response in case of unforeseen issues in external protocols interacting with this token.

Contract & Record

1 audit on record
TypeOkzooToken
NetworkBNB Chain
Token age1y
Contract0x55ad…b4a5
Deployer0x781a…1098
Badge for your website
OKZOO 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. Aug 11, 202613Low

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

Related Audits

6 more on the recordAll audits
FrippyBNB Chain13LowGiggle MascotMAX · BNB Chain13LowBinance CatBNBCAT · BNB Chain13LowNianNianBNB Chain13LowARIA.AIARIA · BNB Chain12LowBreak And ReclaimBAN · BNB Chain14Low

Would You Like a More Detailed Audit of OKZOO?

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