Sonic Inu contract 0x066c…544b on BNB Chain

0x066cda0cca84e9c6ed0a4ecb92aa036a9582544b

As of 21 Nov 2026, Trustblock’s record holds 0x066cda0cca84e9c6ed0a4ecb92aa036a9582544b on BNB Chain as a contract of Sonic Inu. 1 audit report on Trustblock lists this address: CertiK, 18 May 2023. 16 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
Sonic InuCertiKNot recorded (see the report)Open

Open and acknowledged findings in these reports16

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

HighInitial Distribution Centralization RiskSonic Inu · CertiKOpen

All `SonicInu` tokens are sent to the owner when deploying the contract. Therefore the owner completely determines the token distribution.

The audit on Trustblock · Open the report
MediumMissing Input Validation for Fee AddressSonic Inu · CertiKOpen

The functions `updateOpsWallet()`, `updateDevWallet()`, and `updateMarketingWallet()` do not perform any input validation on the `newWallet` parameter. This means that any address can be set as the new wallet, including the contract itself, which can result in the contract gaining tokens through fees.

The audit on Trustblock · Open the report
MediumVariable `_rOwned[account]` Not Updated in FunctiSonic Inu · CertiKOpen

The function `includeInReward` below has a known rate issue. If an excludedFromReward account sends or receives tokens, its tOwned balance is updated. However _rOwned was not updated. This results in an incorrect increase in the return value of `_getRate`. ```solidity function includeInReward(address account) external onlyOwner() { require(_isExcluded[account], "Account is already excluded"); for (uint256 i = 0; i < _excluded.length; i++) { if (_excluded[i] == account) { _excluded[i] = _excluded[_excluded.length - 1]; _tOwned[account] = 0; _isExcluded[account] = false; _excluded.pop(); break; } } } ```

The audit on Trustblock · Open the report
Low`RValues` Calculations Done SeparatelySonic Inu · CertiKOpen

In the codebase, the calculation of the r values for the fees is divided into two separate functions, `_getRValues1()` and `_getRValues2()`. However, neither of the functions is used separately, and they could be merged into a single function to improve the code's readability.

The audit on Trustblock · Open the report
LowCheck Effect Interaction Pattern ViolatedSonic Inu · CertiKOpen

The order of an external call or transfer with respect to a storage manipulation action should follow the check effect interaction pattern. In this case, the function `_transfer()` is called before `_approve()`.

The audit on Trustblock · Open the report
LowFee Exemption not RevokedSonic Inu · CertiKOpen

The owner is exempt from fees by default. Yet when ownership is reset through `transferOwnership()`, the exemptions are not granted to the new owner nor are they revoked from the previous owner.

The audit on Trustblock · Open the report
LowMissing Emit EventsSonic Inu · CertiKOpen

Functions that update state variables should emit relevant events as notifications.

The audit on Trustblock · Open the report
LowPotential Reentrancy AttackSonic Inu · CertiKOpen

The `_transfer()` function is open to an reentrancy attack if `uniswapV2Router` is set maliciously. The function call of `swapAndLiquify()` would eventually send `ethAmount` via `uniswapV2Router.addLiquidityETH()`, and state variable `_rOwned` is changed later in the function call of `_tokenTransfer()`.

The audit on Trustblock · Open the report
LowState Variable Should Be Declared ConstantSonic Inu · CertiKOpen

The following are state variables that are never changed. To save gas they can be declared as constants. ```solidity=143 uint256 private _tTotal = 42e16 * 10**_decimals; ``` - `_tTotal` should be declared `constant`. --- ```solidity=151 address public deadWallet = 0x000000000000000000000000000000000000dEaD; ``` - `deadWallet` should be declared `constant`.

The audit on Trustblock · Open the report
LowTypoSonic Inu · CertiKOpen

There is a typos in the codebase: - "UNLICENSE" should be "UNLICENSED"

The audit on Trustblock · Open the report
LowUnchecked ERC-20 `transfer()`/`transferFrom()` CaSonic Inu · CertiKOpen

The return values of the `transfer()` and `transferFrom()` calls in the smart contract are not checked. Some ERC-20 tokens' transfer functions return no values, while others return a bool value, they should be handled with care. If a function returns `false` instead of reverting upon failure, an unchecked failed transfer could be mistakenly considered successful in the contract. ```solidity=742 IBEP20(_tokenAddr).transfer(_to, _amount); ```

The audit on Trustblock · Open the report
LowUnused FeesChanged EventSonic Inu · CertiKOpen

The event `FeesChanged` was defined in the contract `Sonic Inu` but was not used on the codebase.

The audit on Trustblock · Open the report
LowUnused Return ValueSonic Inu · CertiKOpen

The smart contract does not check or store the return value of an external call in a local or state variable, which may introduce vulnerabilities due to the unhandled outcome. ```solidity=674 router.addLiquidityETH{ value: bnbAmount }( address(this), tokenAmount, 0, // slippage is unavoidable 0, // slippage is unavoidable deadWallet, block.timestamp ); ```

The audit on Trustblock · Open the report
LowUnused State VariableSonic Inu · CertiKOpen

The variable `_lastSell` is not used in the codebase. ```solidity=135 mapping(address => uint256) private _lastSell; ```

The audit on Trustblock · Open the report
LowUsage of `msg.sender` instead of `_msgSender()`Sonic Inu · CertiKOpen

The linked functions use `msg.sender` to retrieve the sender of the transaction instead of using the function `_msgSender()`. Given that the function is inherited from the contract `AccessControl`, which in turns inherits from `Context`, the return value will be the same, but there will be consistency across the contract.

The audit on Trustblock · Open the report
LowUsage of `transfer`/`send` for sending EtherSonic Inu · CertiKOpen

It is not recommended to use Solidity's `transfer()` and `send()` functions for transferring Ether, since some contracts may not be able to receive the funds. Those functions forward only a fixed amount of gas (2300 specifically) and the receiving contracts may run out of gas before finishing the transfer. Also, EVM instructions' gas costs may increase in the future. Thus, some contracts that can receive now may stop working in the future due to the gas limitation. ```solidity=736 payable(msg.sender).transfer(weiAmount); ```

The audit on Trustblock · Open the report

The Sonic Inu security record · Every Sonic Inu address · This address on the explorer