Baby Bonk contract 0xbb28…8775 on BNB Chain

0xbb2826ab03b6321e170f0558804f2b6488c98775

As of 21 Nov 2026, Trustblock’s record holds 0xbb2826ab03b6321e170f0558804f2b6488c98775 on BNB Chain as a contract of Baby Bonk. 1 audit report on Trustblock lists this address: CertiK, 9 Jan 2024. 6 findings in it are recorded as open or acknowledged.

Audit reports that list this address1

Each report’s scope as stored on Trustblock names this address on BNB Chain.

AuditSecurity firmDateCommit named in the reportReport
BabybonkCertiKNot recorded (see the report)Open

Open and acknowledged findings in these reports6

1 High, 5 Low. In the firm’s own words; statuses are the firm’s, from each report.

HighInitial Token DistributionBabybonk · CertiKAcknowledged

All of the BabyBonk 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.

The audit on Trustblock · Open the report
LowMaximum wallet limit could be bypassedBabybonk · CertiKOpen

If `maxWalletLimitEnabled` is true and the wallet (`from`) in the `_isExcludedFromMaxWalletLimit` array transfers `maxWalletAmount + 1` tokens to a normal `to` wallet, the following check will pass. Consequently, the `to` wallet ends up holding a token amount that exceeds the maximum wallet limit. ```solidity=710 if (!_isExcludedFromMaxWalletLimit[from] && !_isExcludedFromMaxWalletLimit[to] && to != uniswapV2Pair ) { ```

The audit on Trustblock · Open the report
LowNo Slippage CheckBabybonk · CertiKOpen

A sandwich attack may happen when an attacker observes a transaction swapping tokens or adding liquidity without setting restrictions on slippage or minimum output amount. The attacker can manipulate the exchange rate by frontrunning (executing before the target) a transaction to purchase one of the assets and make profits by backrunning (executing after the target) a transaction to sell the asset.

The audit on Trustblock · Open the report
LowThird Party DependenciesBabybonk · CertiKOpen

The contract is serving as the underlying entity to interact with third-party `UniswapV2` protocols. The scope of the audit treats 3rd party entities as black boxes and assumes their functional correctness. However, in the real world, 3rd parties can be compromised and this may lead to lost or stolen assets. In addition, upgrades of 3rd parties can possibly create severe impacts, such as increasing fees of 3rd parties, migrating to new LP pools, etc.

The audit on Trustblock · Open the report
LowTrading is enabled for wallets in the `_isExcludeBabybonk · CertiKOpen

```solidity=635 require(tradingEnabled || _isExcludedFromFees[from] || _isExcludedFromFees[to], "Trading not yet enabled!"); ``` Addresses in the `_isExcludedFromFees` array can engage in trading even when `tradingEnabled` is disabled. This is confusing, considering that the array name implies it is meant to be excluded from all fees.

The audit on Trustblock · Open the report
LowVariables That Could Be Declared as ImmutableBabybonk · CertiKOpen

The linked variables assigned in the constructor can be declared as `immutable`. Immutable state variables can be assigned during contract creation but will remain constant throughout the lifetime of a deployed contract. A big advantage of immutable variables is that reading them is significantly cheaper than reading from regular state variables since they will not be stored in storage.

The audit on Trustblock · Open the report

The Baby Bonk security record · Every Baby Bonk address · This address on the explorer