BabyCate contract 0x76b5…be79 on BNB Chain

0x76b560b628f74bf192be09f0449abef8e456be79

As of 21 Nov 2026, Trustblock’s record holds 0x76b560b628f74bf192be09f0449abef8e456be79 on BNB Chain as a contract of BabyCate. 1 audit report on Trustblock lists this address: CertiK, 8 Oct 2024. 5 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
BabyCate - AuditCertiKNot recorded (see the report)Open

Open and acknowledged findings in these reports5

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

HighInitial Token DistributionBabyCate - Audit · CertiKAcknowledged

All of the `BABYCATE` tokens are sent to the contract owner. This is a centralization risk because the owner 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
MediumRouter should not be in the fee exempt whitelistBabyCate - Audit · CertiKAcknowledged

Some restrictions can be bypassed by swapping tokens to the router and then getting tokens from the router. When the tokens are transferred to the router, the attacker uses the feature of the router function ***`removeLiquidityETHSupportingFeeOnTransferTokens`***, which will send all the specified tokens in the router to a specified address. Because the router is not supposed to receive tokens for any user other than remove liquidity..

The audit on Trustblock · Open the report
LowPotential Sandwich AttacksBabyCate - Audit · CertiKAcknowledged

A sandwich attack can occur when an attacker notices a transaction involving token swaps or liquidity additions that lacks slippage restrictions or minimum output amount settings. The attacker can exploit this by frontrunning the transaction to purchase one of the assets, thereby manipulating the exchange rate, and then backrunning the transaction to sell the asset for a profit. The referenced functions are invoked without setting slippage restrictions or minimum output amounts, making transactions that trigger these functions particularly vulnerable to sandwich attacks, especially when large input amounts are involved.

The audit on Trustblock · Open the report
LowRedundant And Unreasonable ApprovalBabyCate - Audit · CertiKAcknowledged

The allowance is approved to the router based on the token swapping amount in the `swapBack` function. Therefore, approving the maximum allowance to the router is redundant and unnecessary.

The audit on Trustblock · Open the report
LowThird-Party Dependency UsageBabyCate - Audit · CertiKAcknowledged

The contract is serving as the underlying entity to interact with one or more third party protocols. The scope of the audit treats third party entities as black boxes and assumes their functional correctness. However, in the real world, third parties can be compromised and this may lead to lost or stolen assets. In addition, upgrades of third parties can possibly create severe impacts, such as increasing fees of third parties, migrating to new LP pools, etc. ```solidity=1011 IUniswapV2Router02 public immutable uniswapV2Router; ``` - The contract `BabyCate` interacts with third party contract with `IUniswapV2Router02` interface via `uniswapV2Router`.

The audit on Trustblock · Open the report

The BabyCate security record · Every BabyCate address · This address on the explorer