CertiK reviewed Baby Bonk (Babybonk) on 9 Jan 2024: 9 findings, 0 critical; 3 marked fixed, 1 acknowledged, 5 open.
Report hosted on skynet.certik.com.
Trustblock does not review code.
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 | 5 | 0 | 2 |
In the contract `BabyBonk` the role `_owner` has authority over the functions shown in the diagram below. Any compromise to the `_owner` account may allow the hacker to take advantage of this authority and - steal fees and marketing funds, - update the sensitive settings of the project, and therefore disturb the normal functions of the contract.  In the contract `Ownable` the role `_owner` has authority over the functions shown in the diagram below. Any compromise to the `_owner` account may allow the hacker to take advantage of this authority. 
The `setPair()` function is designed to update the `uniswapV2Pair` only when the `pairSet` is false. In contrast, the `enableTrading()` function sets `uniswapV2Pair` without checking the `pairSet` flag.
If `walletToWalletTransferFee` is nonzero, a transfer fee will be applied when transferring BabyBonk between wallets. If both `_totalFeesOnBuy` and `_totalFeesOnSell` are set to zero, the `swapAndLiquify()` and `swapAndSendMarketing()` processes will not be triggered. Consequently, the charged `walletToWalletTransferFee` will be locked in the contract.
| Address | Chain | Source code |
|---|---|---|
| 0xbb28…87750xbb2826ab03b6321e170f0558804f2b6488c98775 | Chain: BNB Chain | Source code: Verified source |
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