Honeypot, rug-pull and ownership checks
EthereumThe audit of the PepeToken contract, an ERC20 token, reveals a robust implementation primarily leveraging battle-tested OpenZeppelin libraries.
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 Sep 4, 2026
One more pair holds $3.5K and is not listed. The risk score reads depth across every pair.
The LP tokens of the analysed pool are locked or burned.
0x6982…19330x371d…37390x4c39…cd500xe151…1a310x4dc7…e11f0x0fbf…a4c30xb0e2…d3880xb481…d4ac0x5f8e…0b5fGiven the renounced ownership and non-proxy architecture, there is no mechanism to pause the contract, recover accidentally sent tokens (if applicable), or upgrade the contract to address future vulnerabilities or feature requirements. This lack of administrative flexibility is a direct consequence of the design choice for maximum decentralization.
For future projects where administrative flexibility or upgradeability might be desired, consider implementing a multi-signature wallet for critical administrative functions or utilizing an upgradeable proxy pattern. For this specific contract, ensure users are fully aware of its immutable nature.
Unresolved
owner address is address(0)), rendering all onlyOwner functions inaccessible. This makes the contract highly immutable and decentralized regarding administrative control. While this prevents malicious owner actions, it also means no one can perform administrative tasks, fix potential bugs, or upgrade the contract in the future.I-01The contract's ownership has been renounced (the owner address is address(0)), rendering all onlyOwner functions inaccessible. This makes the contract highly immutable and decentralized regarding administrative control. While this prevents malicious owner actions, it also means no one can perform administrative tasks, fix potential bugs, or upgrade the contract in the future.
This is a design choice that enhances decentralization. Ensure that all stakeholders understand the implications of this immutability, particularly the inability to modify contract logic or parameters post-deployment.
Unresolved
The contract extensively uses battle-tested OpenZeppelin libraries (Context, Ownable, ERC20). This significantly reduces the likelihood of common vulnerabilities like reentrancy, integer overflows, and basic access control flaws, as these libraries are widely audited and considered secure.
Continue to leverage well-audited and maintained libraries for core functionalities. Regularly check for updates and security advisories related to these dependencies.
Unresolved
The audit of the PepeToken contract, an ERC20 token, reveals a robust implementation primarily leveraging battle-tested OpenZeppelin libraries. A key characteristic is the renounced ownership, which enhances decentralization and immutability. This design choice, while beneficial for trust, also means the contract lacks administrative flexibility for future changes or emergency responses.
The technical architecture (7.1) is sound, relying on standard OpenZeppelin ERC20 and Ownable contracts. Code security (7.2) is high due to the use of well-audited libraries and Solidity 0.8.0, which includes SafeMath by default. Access control (7.3) is effectively decentralized as ownership has been renounced, preventing any single entity from controlling critical functions. No complex custom logic was identified that could introduce novel technical vulnerabilities.
The economic model (7.4) is a standard ERC20 token, with no apparent complex tokenomics in the provided code. Governance (7.5) is highly decentralized due to the renounced ownership, meaning no single entity can alter contract parameters or perform administrative actions. While this prevents malicious owner behavior, it also removes the ability to address unforeseen issues or upgrade the contract, representing a trade-off between decentralization and flexibility.
The contract is not designed with upgradeability (7.7) in mind, as indicated by its non-proxy architecture. Furthermore, with ownership renounced, there is no administrative mechanism to implement an upgrade path even if it were technically feasible. This design choice ensures immutability but means the contract cannot be modified or improved post-deployment.
It is recommended to ensure that all initial parameters, especially the total supply and distribution, were correctly configured prior to ownership renouncement, as these cannot be altered.
Users should be fully aware of the contract's immutable nature and the implications of no administrative control or upgrade path. For future projects, consider the trade-offs between full decentralization and the need for emergency administrative functions or upgradeability.
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.
Based on automated analysis, Pepe scores 0/100 (Low Risk) on our risk scale. No honeypot was detected, but always verify independently before investing.
Our scanner flagged a risk score of 0/100. Ownership is renounced which reduces rug-pull risk. DYOR before purchasing any token.
The contract is open-source and verified on-chain. Verification is not the same as a full security audit. Use Quantum Audit's free tool to run a deeper analysis of the contract code.
Paste the contract address into our AI-powered scanner for a deeper real-time report — free, with every scoring factor shown.
Get Detailed Audit Is this your token? Publish your own audit on this page
