Early-stage security check — honeypot & rug-pull analysis
BNB ChainThe AgentPadTokenV3 contract implements a custom token with integrated buy/sell functionality and minting capabilities.
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 23, 2026
The 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.
0xa3b2…4bfcA privileged address — the deployer, the owner, or the token contract itself — is among these holders, so that party can withdraw liquidity.
The functions _finishV3 and _graduateV2 do not verify the return values of ERC-20 transfers, which may lead to silent failures if a transfer fails.
Use OpenZeppelin's SafeERC20 library to perform transfers and ensure return values are validated.
Unresolved
The factory address has the authority to mint new tokens via buyWithBNB, sell, and related functions, which can dilute existing token holders.
Implement a hard cap on total supply or require a governance vote for significant minting events.
Unresolved
The factory controls a switch that can halt or enable transfers, giving it the power to freeze user assets or restrict trading at any time.
Document the specific conditions under which transfers are gated and provide transparency to users regarding these rules.
Unresolved
0.0% of the pool's LP is burned or time-locked. 100.0% of the LP tokens sit in the token contract itself — only a function in the token's own code could move them, so whether this is a lock depends on that code and on who controls it. 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
The ten largest holders own 44.4% of supply. Of that, 24.8% in DEX pools — not holders that can sell, so excluded from the concentration score. What remains: 17.5% in wallets, 2.0% in other contracts. The deployer/owner wallet itself holds 1.9%. 445 holders in total.
Watch the largest wallets that are not exchanges, pools or locks — those are the ones that can move the price.
Acknowledged
445 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
Liquidity $19K (DexScreener, all pools). 24h trading volume $123K (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: mintable with no on-chain cap found. Control: an owner that could not be resolved. Code: not upgradeable (no proxy). Fees: no buy or sell tax. Market: $19K of DEX liquidity across 1 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 AgentPadTokenV3 contract implements a custom token with integrated buy/sell functionality and minting capabilities. The architecture relies heavily on a factory-controlled state machine to manage token lifecycle and liquidity. While the core logic is functional, the contract exhibits significant centralization risks and potential failure points in external token interactions.
The contract utilizes ReentrancyGuard to protect sensitive buy/sell operations. 7.1 Architecture: The design tightly couples token logic with liquidity management. 7.2 Code Security: The failure to check ERC-20 return values in _finishV3 and _graduateV2 is a significant oversight. 7.3 Access Control: The factory contract holds absolute authority over minting and transfer gating.
7.4 Economic: The minting mechanism allows the factory to dilute holders at will. 7.5 Governance: There is no decentralized governance; the factory address acts as a single point of failure. 7.6 External: The protocol depends on the factory's integrity for all lifecycle transitions.
7.7 Upgrades: The contract is not upgradeable. 7.8 Operations: Operational risk is high due to the reliance on the factory address for critical state changes.
Implement strict return value checking for all external ERC-20 transfers to ensure transactions do not fail silently.
Consider introducing a multi-sig or timelock for the factory-controlled functions to mitigate the impact of a compromised or malicious factory address.
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.
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
