BabyPepe
CertiK reviewed BabyPepe on 6 May 2024: 8 findings, 0 critical; 3 marked fixed, 1 acknowledged, 4 open.
No open critical findings
Open the reportOpen BabyPepe’s security record
Report hosted on skynet.certik.com.
Trustblock does not review code.
Findings8
Statuses are the security firm’s own, from its report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 0 | 1 | 1 |
| Medium | 0 | 0 | 0 |
| Low | 4 | 0 | 2 |
HighInitial Token DistributionAcknowledged
All the BabyPepe tokens are sent to the contract deployer. This is a centralization risk because the deployer can distribute tokens without obtaining the consensus of the community. Any compromise to these addresses may allow a hacker to steal and sell tokens on the market, resulting in severe damage to the project.
Contracts in scope1
| Address | Chain | Source code |
|---|---|---|
| 0x9d6db6382444b70a51307a4291188f60d4eef205 | Chain: BNB Chain | Source code: Verified source |
Part of BabyPepe’s security record
BabyPepeAudits1 audit by 1 firmLast audit May 2024, by CertiK.
Critical findingsNo open critical findingsIn 1 report.
Open BabyPepe’s security recordSecurity firm
CertiK1,044 projects reviewed · 1,375 reports · latest May 2025
See CertiK’s auditsSomething wrong on this page? A missing report, a wrong date, a finding that was fixed since. Tell us and we check it against its source.
Tell us