Sonic Inu audit reports

BNB Chainsonic-inu.com

Sonic Inu has 1 public audit report from CertiK; dated 18 May 2023; no critical findings reported. It also holds 1 deployed contract on 1 chain.

Critical findings
No open critical findings
In 1 report.
Open the latest report
Your label, live
Get the label for your site

Last updated . It holds audits and findings, contracts and incidents up to Nov 2026. Trustblock does not review code.

Open findings across every firm16

Statuses are the security firms’ own

16 findings are still open or acknowledged in the firms’ reports: 1 high, 2 medium, 13 low (all open).

High
1
Medium
2
Low
13
  • High Open

    Initial Distribution Centralization Risk

    Sonic Inu · CertiK · 18 May 2023 · Report ↗

  • Medium Open

    Missing Input Validation for Fee Address

    Sonic Inu · CertiK · 18 May 2023 · Report ↗

  • Medium Open

    Variable `_rOwned[account]` Not Updated in Functi

    Sonic Inu · CertiK · 18 May 2023 · Report ↗

  • Low Open

    `RValues` Calculations Done Separately

    Sonic Inu · CertiK · 18 May 2023 · Report ↗

  • Low Open

    Check Effect Interaction Pattern Violated

    Sonic Inu · CertiK · 18 May 2023 · Report ↗

  • Low Open

    Fee Exemption not Revoked

    Sonic Inu · CertiK · 18 May 2023 · Report ↗

  • Low Open

    Missing Emit Events

    Sonic Inu · CertiK · 18 May 2023 · Report ↗

  • Low Open

    Potential Reentrancy Attack

    Sonic Inu · CertiK · 18 May 2023 · Report ↗

  • Low Open

    State Variable Should Be Declared Constant

    Sonic Inu · CertiK · 18 May 2023 · Report ↗

  • Low Open

    Typo

    Sonic Inu · CertiK · 18 May 2023 · Report ↗

All 16 open and acknowledged findings

Audits1

Newest first

ReportSecurity firmDateScopeCritical findingsFindingsSource
Sonic InuSecurity firm: CertiKDate: Scope: 1 address on BNB ChainNone openFindings: 2 high · 3 medium · 13 low
2 fixed · 16 open
skynet.certik.com ↗

Findings18

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

SeverityOpenAcknowledgedFixed
Critical000
High101
Medium201
Low1300
HighInitial Distribution Centralization RiskSonic Inu · CertiK · 18 May 2023Open

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

Open the report
MediumMissing Input Validation for Fee AddressSonic Inu · CertiK · 18 May 2023Open

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.

Open the report
MediumVariable `_rOwned[account]` Not Updated in FunctiSonic Inu · CertiK · 18 May 2023Open

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; } } } ```

Open the report
Low`RValues` Calculations Done SeparatelySonic Inu · CertiK · 18 May 2023Open

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.

Open the report
LowCheck Effect Interaction Pattern ViolatedSonic Inu · CertiK · 18 May 2023Open

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()`.

Open the report
LowFee Exemption not RevokedSonic Inu · CertiK · 18 May 2023Open

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.

Open the report
LowMissing Emit EventsSonic Inu · CertiK · 18 May 2023Open

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

Open the report
LowPotential Reentrancy AttackSonic Inu · CertiK · 18 May 2023Open

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()`.

Open the report
LowState Variable Should Be Declared ConstantSonic Inu · CertiK · 18 May 2023Open

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`.

Open the report
LowTypoSonic Inu · CertiK · 18 May 2023Open

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

Open the report
Show 6 more
LowUnchecked ERC-20 `transfer()`/`transferFrom()` CaSonic Inu · CertiK · 18 May 2023Open

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); ```

Open the report
LowUnused FeesChanged EventSonic Inu · CertiK · 18 May 2023Open

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

Open the report
LowUnused Return ValueSonic Inu · CertiK · 18 May 2023Open

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 ); ```

Open the report
LowUnused State VariableSonic Inu · CertiK · 18 May 2023Open

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

Open the report
LowUsage of `msg.sender` instead of `_msgSender()`Sonic Inu · CertiK · 18 May 2023Open

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.

Open the report
LowUsage of `transfer`/`send` for sending EtherSonic Inu · CertiK · 18 May 2023Open

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); ```

Open the report

Contracts1

AddressChainSource code
0x066cda0cca84e9c6ed0a4ecb92aa036a9582544bChain: BNB ChainSource code: Verified source

Sonic Inu: questions

Is Sonic Inu audited?

Trustblock holds 1 public audit report for Sonic Inu, dated 18 May 2023. The latest is by CertiK (“Sonic Inu”).

Who audited Sonic Inu?

CertiK wrote the report Trustblock holds for Sonic Inu.

Are there open findings in Sonic Inu’s audits?

16 findings are still open or acknowledged in the firms’ reports: 1 high, 2 medium, 13 low (all open). No critical finding is reported. Statuses are the security firms’ own.

Show this on your site

Is this your project? Show this record on your own website. The label states what the record holds, links to this page and updates by itself. It is free and needs no sign-in.

Content

Facts

Automatic: the three strongest facts of this project’s own record (its last audit and two more), highlighted. They update with the record. Picking a fact turns Automatic off.

Fixed as
Language

Style

Layout
Theme
Accent
Corners

Format

Size
Date
Embed as
HTML
<head>
<script src="https://widget.trustblock.run/project-widget.min.js" defer></script>
</head>
<body>
<div
data-tb-project-widget
data-tb-project-slug="sonic-inu"
></div>
</body>

Paste the code where the label should appear. It uses no API credit and updates by itself.

Something 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