Early-stage security check — honeypot & rug-pull analysis
BNB ChainThe protocol utilizes an EIP-1167 minimal clone architecture, ensuring the implementation logic is immutable post-deployment.
Read the full analysisEach 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
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 Oct 25, 2026
The risk score reads depth across every pair.
The LP tokens of the analysed pool are locked or burned.
The postInitialize function allows a privileged module to change the addresses of contracts that the token relies on for every transfer. This means the controller can redirect token logic to arbitrary contracts at any time.
Restrict the ability to change core dependencies to a multi-signature governance contract and implement a time-lock for such updates.
Unresolved
Multiple privileged modules can modify the transfer fees and tax collection logic. This allows for arbitrary changes to the economic cost of trading the token.
Set hard caps on the maximum allowable fees to protect users from sudden, excessive tax increases.
Unresolved
The _doDispatchFee function performs division before multiplication, which can lead to precision loss and minor discrepancies in fee calculations.
Reorder operations to perform multiplication before division to maintain higher precision.
Unresolved
Privileged functions can toggle the 'swapping' state, which directly impacts whether transfers or sales are permitted. This gives the controller the ability to pause or restrict trading at will. Ownership is renounced, so no one can call these functions now.
Document the intended use of these switches and ensure they are governed by a transparent process to prevent abuse.
Unresolved
The ten largest holders own 22.7% of supply. Of that, 10.3% in DEX pools — not holders that can sell, so excluded from the concentration score. What remains: 9.6% in wallets, 2.8% in other contracts. 1,387 holders in total.
Watch the largest wallets that are not exchanges, pools or locks — those are the ones that can move the price.
Acknowledged
1,387 holders. Not listed by CoinGecko or any exchange GoPlus tracks. Nothing independent confirms who is behind this token, so every power its contract grants is scored at face value.
Match the contract address against the project's official channels before trading.
Acknowledged
100.0% of the pool's LP is burned or time-locked. 100.0% of the LP tokens were sent to a burn address — that liquidity can never be withdrawn by anyone. Some pools are concentrated-liquidity (V3/V4) positions; shares above are by position as GoPlus reports them.
Check the lock's end date and beneficiary on the locker's own page before relying on it.
Acknowledged
Liquidity $39K (DexScreener, all pools). 24h trading volume $1.5M (DexScreener, all pools).
Size any position to the liquidity and daily volume shown — they set how much you can sell and at what price.
Acknowledged
A token issued by a project for use, governance or fundraising. Scored on its contract and market facts. The class itself adds no points; the contract and market facts decide the score. Basis: no class-specific evidence. Tokenomics — Supply: fixed — the contract has no mint function. Control: nobody (ownership renounced). Code: not upgradeable (no proxy). Fees: 1% on buy, 1% on sell. Market: $39K of DEX liquidity across 2 pools. Launch: under a day of market history.
Check the project's own documentation for what the token is used for; this report covers what the contract allows.
Acknowledged
The token's oldest DEX pool is less than a day old. Age is not part of the risk score — a new token is not a risky one by default — but a short history means fewer trades and holder changes behind the facts in this report.
Re-check ownership, liquidity and holder distribution as the token matures; those are the facts that move early.
Acknowledged
The protocol utilizes an EIP-1167 minimal clone architecture, ensuring the implementation logic is immutable post-deployment. The token features complex tax and bonding mechanisms controlled by multiple external modules. While the core logic is fixed, the system relies heavily on privileged roles that can alter transfer rules, fee structures, and external contract dependencies, introducing significant centralization risks.
The architecture leverages EIP-1167 clones for gas-efficient deployment, ensuring the implementation contract remains immutable. The codebase is modular, separating tax logic, bonding, and migration into distinct modules. However, the reliance on external contract addresses for core transfer logic (e.g., quote, wrappedNative) creates a dependency risk where the token's behavior can be fundamentally altered by the tokenModule.
Economic parameters such as fees and liquidity pool settings are entirely managed by privileged modules. The system allows for dynamic fee adjustments via onMigrate and onBondingTrade, which directly impacts user balances. This centralization means that token holders are subject to the decisions of the module controllers regarding tax rates and liquidity management.
The contract uses EIP-1167 minimal clones, which are inherently immutable. There is no upgradeability pattern implemented for the logic contract itself. While the token's behavior can be modified through state changes in privileged functions, the underlying bytecode cannot be replaced.
To mitigate centralization risks, consider implementing a multi-signature wallet or a time-lock mechanism for all privileged functions that modify transfer rules or fee structures.
This would provide transparency and prevent immediate, unilateral changes to the token's economic model. Additionally, perform rigorous testing on the interaction between the token and external modules. Ensure that any address updates in postInitialize are validated against a whitelist or registry to prevent the redirection of token logic to malicious contracts.
Free for any token on the record. It links to this page and always shows the current score and the date it was checked.
Score changes are recorded as dated snapshots — history is append-only and cannot be edited.
The Binance Agent (4AGENT) contract on BNB Chain is 0x5f6a1ce1733fc4834a526798c0e8cf85137effff. Compare it with the address the project itself publishes before trading: other contracts can carry the same name and ticker.
Quantum Audit's risk score for Binance Agent is 51/100 (Medium risk) as of Oct 25, 2026, computed by a deterministic function from on-chain facts — Contract verified: Verified; Ownership: Renounced; Mint: No mint; Liquidity lock: Locked; Upgradeability: Fixed code; Honeypot: None found; Buy / sell tax: 1% / 1%. A score is a dated snapshot of those facts, not a guarantee; each one is listed on this page.
Liquidity lock: Locked (as of Oct 25, 2026). Total DEX liquidity: $39.1K.
As of Oct 25, 2026, the 10 largest holders own 22.7% of the supply across 1,387 holders. The Holders section on this page shows who they are by holder type.
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
