BABY

CertiK30 Mar 2024Code version: not recorded (see the report)

Audit

CertiK reviewed Baby on 30 Mar 2024: 2 findings, 0 critical; none marked fixed.

No open critical findings

Open Baby’s security record

The original report was removed from its address (seen 14 Oct 2026).

Trustblock does not review code.

Findings2

Statuses are the security firm’s own, from its report.

Severity	Open	Acknowledged	Fixed
Critical	0	0	0
High	1	0	0
Medium	1	0	0
Low	0	0	0

HighInitial Token DistributionOpen

Based on the on-chain analysis, the initially minted 1000000000000000000 Baby token has been transferred to the token account 8sAsYYNon2EUrKypvZhETR73QeNgxY7zyDfBYHx7uC3y in the transaction [4MZzyXACEe8wKBgpNXVbRLxEWYRfkNC1VuP5jdEVgKJErpM2rnzZ9xm92jNdkmqNDfDnJde1vvvTEF36WFT1SZZR](https://explorer.solana.com/tx/4MZzyXACEe8wKBgpNXVbRLxEWYRfkNC1VuP5jdEVgKJErpM2rnzZ9xm92jNdkmqNDfDnJde1vvvTEF36WFT1SZZR). The tokens are later distributed to multiple addresses and the detailed token distribution can be found [on-chain](https://solscan.io/account/8sAsYYNon2EUrKypvZhETR73QeNgxY7zyDfBYHx7uC3y#splTransfer). This could be a centralization risk as those accounts can distribute tokens without obtaining the consensus of the community. Any compromise to those accounts that hold undistributed tokens may allow the attacker to steal and sell tokens on the market, resulting in severe damage to the project.

MediumCentralization Related RisksOpen

According to the on-chain data, the metadata and update authority for the Baby Token are centralized to a single account (2uTnBkavD1teQTdyyERxxh6r2C3mC5g6RryA5LnnqkCQ). This centralization poses a risk as the authority to update token metadata is held by a singular entity, potentially leading to unilateral decisions without community consensus.