Quantum Audit Logo
Launch App

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

Is Zypher Token Safe?

POPBNB 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
High RiskHow is this score calculated?
How the score breaks downratings: 10 is safest
Technical6/10Governance1/10Upgrades5/10Checks passed2 of 5Findings1 High · 1 Medium · 2 Info4
SummaryAI Copilot

The Zypher Network Token contract is an ERC-20 compliant token built upon battle-tested OpenZeppelin libraries, including Ownable2Step, Pausable, and ERC20Burnable.

Read the full analysis
What raised the score
  • Ownership not renounced — Multisig
  • Mintable supply, but capped at 0.0%/year
  • Top-10 concentration > 30%
  • Liquidity not locked
  • LP top1 unlocked holder = 98.9%
  • LP top3 unlocked holders = 99.8%
  • 1 High finding(s) from audit
  • 1 Medium finding(s) from audit
Exact factors
  • Ownership NOT renounced — Multisig (2-of-3)
  • Mintable supply, but capped at 0.0%/year
  • Top-10 concentration > 30% (89.7% total → 37.7% effective; 3.0% in EOAs, 86.7% in contracts — moderate)
  • Liquidity NOT locked (owner can withdraw — rug-pull risk)
  • LP top1 unlocked holder = 98.9% (exit-liquidity risk)
  • LP top3 unlocked holders = 99.8% (exit-liquidity risk)
  • 1 High finding(s) from audit
  • 1 Medium 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 42 of 5 checks passed
Contract verifiedVerified
OwnershipRetained
MintMintable
Liquidity lockNot locked
UpgradeabilityFixed code

Holders

as of audit · Sep 4, 2026
86.7%Contracts3.0%10.3%Everyone else
86.7%Contracts3.0%10.3%
ContractsWalletsEveryone elseBubble area = share of supply
89.7%of supply sits with the top 10 holders
  • Contractstreasury, vesting, bridge, staking86.7%
  • Walletsanonymous holders, free to sell3.0%
  • Everyone elsethe rest of the supply10.3%
Effective concentrationwhat the score reads37.7%
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$463.7K across 4 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$463.7KShare of depth100.0%
Top-1 Unlocked Holder98.9%
Top-3 Unlocked99.8%
Unlocked LP held by
0x1663…441c0x7820…8ef30x894a…40130xe679…75d40xccfd…00bf

A privileged address — the deployer, the owner, or the token contract itself — is among these holders, so that party can withdraw liquidity.

Security Findings

1 High1 Medium2 Info
High

Centralized Control Over Critical Functions and Initial Supply

The contract owner has significant centralized control. The entire initial token supply is minted to the owner's address during deployment. Furthermore, the owner possesses the exclusive ability to pause and unpause all token transfers, effectively halting the token's utility. This level of control, while common in initial token deployments, presents a single point of authority that could be misused or compromised, impacting all token holders (7.3 Access Control, 7.4 Economic, 7.8 Operations).H-01

Issue

The contract owner has significant centralized control. The entire initial token supply is minted to the owner's address during deployment. Furthermore, the owner possesses the exclusive ability to pause and unpause all token transfers, effectively halting the token's utility. This level of control, while common in initial token deployments, presents a single point of authority that could be misused or compromised, impacting all token holders (7.3 Access Control, 7.4 Economic, 7.8 Operations).

Fix

Implement a multi-signature wallet for the owner address to distribute control over critical functions like pausing and ownership transfers. Consider a timelock mechanism for sensitive operations to provide a delay for community review. For future iterations, explore mechanisms to progressively decentralize control over the token supply or critical functions.

Status

Unresolved

Medium

Single Point of Failure for Owner Key

The contract relies on a single external account (the owner) for all administrative actions, including pausing transfers and transferring ownership. If the private key for this owner account is compromised, lost, or becomes inaccessible, all owner-restricted functionalities could be exploited or become permanently unavailable. While Ownable2Step mitigates accidental transfers, it does not address the fundamental risk of a single point of failure (7.3 Access Control, 7.8 Operations).M-01

Issue

The contract relies on a single external account (the owner) for all administrative actions, including pausing transfers and transferring ownership. If the private key for this owner account is compromised, lost, or becomes inaccessible, all owner-restricted functionalities could be exploited or become permanently unavailable. While Ownable2Step mitigates accidental transfers, it does not address the fundamental risk of a single point of failure (7.3 Access Control, 7.8 Operations).

Fix

Secure the owner's private key with industry best practices, such as a hardware wallet. For enhanced security and resilience, transition ownership to a multi-signature wallet (e.g., Gnosis Safe) requiring multiple approvals for sensitive transactions.

Status

Unresolved

Info

Non-Upgradeability of Contract Logic

The Zypher Network Token contract is deployed directly and does not utilize a proxy pattern, meaning its logic is immutable once deployed. This design choice implies that no future bug fixes, feature enhancements, or protocol adjustments can be made to the existing contract. Any necessary changes would require deploying an entirely new contract and migrating users, which can be a complex and disruptive process (7.7 Upgrades).I-01

Issue

The Zypher Network Token contract is deployed directly and does not utilize a proxy pattern, meaning its logic is immutable once deployed. This design choice implies that no future bug fixes, feature enhancements, or protocol adjustments can be made to the existing contract. Any necessary changes would require deploying an entirely new contract and migrating users, which can be a complex and disruptive process (7.7 Upgrades).

Fix

This is a design decision. If future upgradeability is desired, consider implementing a proxy pattern (e.g., UUPS or Transparent) in future contract deployments. For this contract, ensure thorough testing and auditing to minimize the need for future changes.

Status

Unresolved

Info

Reliance on OpenZeppelin Libraries

The contract heavily relies on OpenZeppelin's standard libraries (ERC20, Ownable2Step, Pausable, ERC20Burnable). While these libraries are widely used and thoroughly audited, any undiscovered vulnerability within these external dependencies could potentially affect the Zypher Network Token contract. This is an inherent aspect of building on established frameworks (7.6 External).I-02

Issue

The contract heavily relies on OpenZeppelin's standard libraries (ERC20, Ownable2Step, Pausable, ERC20Burnable). While these libraries are widely used and thoroughly audited, any undiscovered vulnerability within these external dependencies could potentially affect the Zypher Network Token contract. This is an inherent aspect of building on established frameworks (7.6 External).

Fix

Regularly monitor OpenZeppelin's security advisories and updates. While direct action on this contract is limited, staying informed about potential vulnerabilities in dependencies is crucial for overall protocol security.

Status

Unresolved

Analysis

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

The Zypher Network Token contract is an ERC-20 compliant token built upon battle-tested OpenZeppelin libraries, including Ownable2Step, Pausable, and ERC20Burnable. The contract initializes with a fixed total supply minted to the deployer, who also assumes ownership. While the technical implementation is robust, the centralized control over critical functions and the initial token supply introduces operational and economic risks. External data regarding TVL, balance, deployment, and transaction count was not provided for this analysis.

Technical6/10Medium risk

The technical implementation of the Zypher Network Token contract is strong, leveraging well-audited OpenZeppelin libraries (7.2 Code Security). It inherits from ERC20, ERC20Burnable, Ownable2Step, and Pausable, ensuring standard and secure token functionalities. The use of Ownable2Step for ownership transfers (7.3 Access Control) enhances security by requiring a two-step process, mitigating accidental transfers. The contract includes a pausing mechanism (7.8 Operations) controlled by the owner, allowing for emergency halts of transfers. No reentrancy, integer overflow/underflow, or other common technical vulnerabilities were identified.

Governance1/10High risk

The contract exhibits a high degree of centralized control (7.4 Economic, 7.5 Governance). The initial owner receives the entire token supply upon deployment and retains the power to pause all token transfers via the pause() function. While Ownable2Step provides a safer mechanism for transferring ownership, the owner's single point of control over critical operations like pausing introduces a significant operational risk. The economic model is a standard fixed-supply token with burning capabilities, but the initial distribution is fully centralized to the owner.

Upgrades5/10Medium risk

The Zypher Network Token contract is not designed to be upgradeable (7.7 Upgrades). It is deployed as a standard, non-proxy contract, meaning its logic cannot be modified post-deployment. Any future changes or bug fixes would necessitate deploying an entirely new contract and migrating users, which is a common design choice for simple token contracts.

Final RecommendationWhat to do about this score

To mitigate the identified risks, it is strongly recommended that the contract owner's private key be secured using a robust multi-signature wallet solution.

This would distribute control and reduce the single point of failure risk. Additionally, consider establishing clear, public guidelines for the use of the pause() function to enhance transparency and trust within the community. For future projects, explore options for progressive decentralization of control over time.

Contract & Record

1 audit on record
TypeZypherNetworkToken
NetworkBNB Chain
Token age10mo
Contract0xa3cf…8fe6
Deployer0x8beb…1987
Badge for your website
Zypher Token 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, 202676High
  2. Jul 23, 202674High
  3. Jul 22, 202656Medium

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

Related Audits

6 more on the recordAll audits
STBL_Token - STBL Governance TokenSTBL · BNB Chain76HighTartSwapTART · BNB Chain76HighDisney (Ondo Tokenized)DISON · BNB Chain76HighSpaceXSPCXB · BNB Chain77HighLorenzo Governance TokenBANK · BNB Chain77HighVenusCoinBNB Chain77High

Would You Like a More Detailed Audit of Zypher 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