The BNBOrochiNetworkToken contract is an ERC-20 token built upon OpenZeppelin's battle-tested implementations for ERC20 and Ownable. The core token functionalities are robust. Key findings include a design limitation regarding the single-shot minting mechanism and the inherent centralization risk associated with the Ownable pattern. No critical technical vulnerabilities were identified.

On-chain security analysis — is it a scam or legit?
Is Orochi Network Token Safe?
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 →The BNBOrochiNetworkToken contract is an ERC-20 token built upon OpenZeppelin's battle-tested implementations for ERC20 and Ownable.
Read the full analysis- Mintable supply — no cap found, dilution unbounded
- Top-10 concentration > 30%
- Liquidity not locked, but no owner/deployer address holds LP — market-depth risk, not rug risk
- LP top1 unlocked holder = 100.0%
- LP top3 unlocked holders = 100.0%
- 1 Medium finding(s) from audit
- 1 Low finding(s) from audit
Exact factors
- Mintable supply — no cap found, dilution unbounded
- Top-10 concentration > 30% (55.6% total → 44.2% effective; 36.6% in EOAs, 19.1% in contracts — moderate)
- Liquidity not locked, but no owner/deployer address holds LP — market-depth risk, not rug risk
- LP top1 unlocked holder = 100.0% (independent LP — depth risk, pool = 100% of DEX liquidity)
- LP top3 unlocked holders = 100.0% (independent LP — depth risk, pool = 100% of DEX liquidity)
- 1 Medium finding(s) from audit
- 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 4Holders
as of audit · Sep 4, 2026- Contractstreasury, vesting, bridge, staking19.1%
- Walletsanonymous holders, free to sell36.6%
- Everyone elsethe rest of the supply44.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 4The 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.
0x166a…0b050xf663…a2b00x9faa…6cd4No privileged address appears among these holders: the unlocked liquidity sits with independent providers, not with the deployer.
Security Findings
MediumSingle-Shot Minting Design Limitation
The mint() function includes a check if (totalSupply() > 0) { revert AlreadyMinted(totalSupply()); }, which prevents subsequent minting calls if any tokens have already been minted (i.e., totalSupply is non-zero). If the owner initially mints 0 tokens, they can still mint a non-zero amount later. However, if they mint any non-zero amount, they cannot mint additional tokens in the future. This design choice creates an immutable total supply after the first non-zero mint, which might be a desired feature but limits flexibility for future token supply management.M-01
Issue
The mint() function includes a check if (totalSupply() > 0) { revert AlreadyMinted(totalSupply()); }, which prevents subsequent minting calls if any tokens have already been minted (i.e., totalSupply is non-zero). If the owner initially mints 0 tokens, they can still mint a non-zero amount later. However, if they mint any non-zero amount, they cannot mint additional tokens in the future. This design choice creates an immutable total supply after the first non-zero mint, which might be a desired feature but limits flexibility for future token supply management.
Fix
Confirm that a fixed, non-expandable token supply after the initial mint is the intended tokenomic model. If future flexibility for supply adjustments (e.g., for ecosystem growth, liquidity incentives) is ever desired, this design would require a new contract deployment. Ensure the initial mint quantity is carefully planned to meet all long-term requirements.
Status
Unresolved
LowCentralized Ownership Risk
The contract utilizes the Ownable pattern, granting a single external address (the owner) exclusive control over critical administrative functions, specifically the mint() function and the ability to transferOwnership(). This introduces a single point of failure (7.3 Access Control). If the owner's private key is compromised, a malicious actor could potentially perform an unauthorized initial mint or transfer ownership to themselves, leading to a loss of control or unexpected token distribution.L-01
Issue
The contract utilizes the Ownable pattern, granting a single external address (the owner) exclusive control over critical administrative functions, specifically the mint() function and the ability to transferOwnership(). This introduces a single point of failure (7.3 Access Control). If the owner's private key is compromised, a malicious actor could potentially perform an unauthorized initial mint or transfer ownership to themselves, leading to a loss of control or unexpected token distribution.
Fix
To mitigate the risk associated with a single point of failure, consider transferring ownership to a multi-signature wallet (e.g., Gnosis Safe) after deployment. This distributes control among multiple trusted parties, requiring multiple approvals for critical operations. Alternatively, if the token supply is fixed and no further administrative actions are anticipated, the owner could renounce ownership to fully decentralize control.
Status
Unresolved
InfoImmutability of Token Decimals
The decimals() function is hardcoded to return 18. While 18 is the most common and widely accepted standard for ERC-20 token decimals, this value is immutable once the contract is deployed. Any future requirement to change the token's decimal precision would necessitate deploying an entirely new token contract.I-01
Issue
The decimals() function is hardcoded to return 18. While 18 is the most common and widely accepted standard for ERC-20 token decimals, this value is immutable once the contract is deployed. Any future requirement to change the token's decimal precision would necessitate deploying an entirely new token contract.
Fix
Confirm that 18 decimals is the permanent and desired configuration for the token. This is generally a safe and standard practice, but it's important to acknowledge its immutability in the context of long-term project planning.
Status
Unresolved
Analysis
AI Copilotas of audit · Sep 4The contract leverages battle-tested OpenZeppelin ERC20 and Ownable implementations, ensuring robust core token functionalities and secure access control (7.2 Code Security). Standard ERC20 operations like transfer and approve are correctly implemented with appropriate checks and custom error handling. No reentrancy or integer overflow vulnerabilities were identified due to the careful use of unchecked blocks after validation checks. The architecture (7.1 Architecture) is straightforward and adheres to common ERC-20 standards.
The token's economic model features a single-shot minting mechanism controlled by the owner (7.4 Economic). Once a non-zero supply is minted, no further tokens can be created, which defines a fixed supply. However, this introduces a dependency on a single owner for the initial mint (7.5 Governance), posing a centralization risk if the owner's key is compromised. Transferring ownership to a multi-sig or renouncing it post-deployment can mitigate this. External dependencies (7.6 External) are limited to standard ERC interfaces.
The contract is not designed to be upgradeable (7.7 Upgrades), meaning its logic is immutable once deployed. This eliminates risks associated with proxy patterns, such as storage collisions or incorrect upgrade paths. Any future changes to the token's functionality would require a new contract deployment and migration, which is a common approach for simple token contracts.
It is recommended to carefully plan the initial token supply due to the single-shot minting mechanism.
Consider transferring ownership to a multi-signature wallet for enhanced security and shared control over the initial mint and other administrative functions. After all necessary administrative tasks are completed, evaluate the option of renouncing ownership to further decentralize control and reduce the single point of failure risk.
Contract & Record
Free for any token on the record. It links to this page and always shows the current score and the date it was checked.
- Sep 4, 202641Medium
- Aug 11, 202613Low
Score changes are recorded as dated snapshots — history is append-only and cannot be edited.
Frequently Asked Questions
What is the ON contract address?
The Orochi Network Token (ON) contract on BNB Chain is 0x0e4f6209ed984b21edea43ace6e09559ed051d48. Compare it with the address the project itself publishes before trading: other contracts can carry the same name and ticker.
Is Orochi Network Token a scam?
Quantum Audit's risk score for Orochi Network Token is 41/100 (Medium risk) as of Sep 4, 2026, computed by a deterministic function from on-chain facts — Contract verified: Verified; Ownership: Renounced; Mint: Mintable; Liquidity lock: Not locked; Upgradeability: Fixed code. A score is a dated snapshot of those facts, not a guarantee; each one is listed on this page.
Is ON liquidity locked?
Liquidity lock: Not locked (as of Sep 4, 2026). Total DEX liquidity: $1.17M.
Who holds ON?
As of Sep 4, 2026, the 10 largest holders own 55.6% of the supply. The Holders section on this page shows who they are by holder type.
Would You Like a More Detailed Audit of Orochi Network Token?
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