CertiK reviewed BaoBey on 2 May 2023: 11 findings, 0 critical; 10 marked fixed, 1 open.
The original report was removed from its address (seen 17 Oct 2026).
Trustblock does not review code.
Statuses are the security firm’s own, from its report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 1 | 0 | 1 |
| Medium | 0 | 0 | 1 |
| Low | 0 | 0 | 8 |
In the contract `BaoBeyToken` the roles `_owner` and `marketing_wallet` have authority over the following functions: - `removeLimits()` - `disableTransferDelay()` - `setIsExcludedFromTax()` - `setAutomatedMarketMakerPair()` Any compromise to the `_owner` or `marketing_wallet` accounts may allow the hacker to take advantage of this authority and do any of the following: - disable limits which control how transfers behave; - exclude any address from taxes, which could disrupt the deflationary aspect of the token; - set any address as an automated market maker pair, which could potentially disrupt contract functionality ---- In the contract `BaoBeyToken` the role `_owner` has authority over the following functions: - `init()` - `enableTrading()` - `transferOwnership()` - `renounceOwnership()` Any compromise to the `_owner` account may allow the hacker to take advantage of this authority and transfer their privileged role to an address he/she controls or renounce ownership, which cannot be undone and would prevent any privileged function from being called again.
The report names a repository or files. Open the report to see its scope.
Repository and files the report names (1)
1,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