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.
Last updated . It holds audits and findings, contracts and incidents up to Nov 2026. Trustblock does not review code.
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).
Initial Distribution Centralization Risk
Sonic Inu · CertiK · 18 May 2023 · Report ↗
Missing Input Validation for Fee Address
Sonic Inu · CertiK · 18 May 2023 · Report ↗
Variable `_rOwned[account]` Not Updated in Functi
Sonic Inu · CertiK · 18 May 2023 · Report ↗
`RValues` Calculations Done Separately
Sonic Inu · CertiK · 18 May 2023 · Report ↗
Check Effect Interaction Pattern Violated
Sonic Inu · CertiK · 18 May 2023 · Report ↗
Fee Exemption not Revoked
Sonic Inu · CertiK · 18 May 2023 · Report ↗
Missing Emit Events
Sonic Inu · CertiK · 18 May 2023 · Report ↗
Potential Reentrancy Attack
Sonic Inu · CertiK · 18 May 2023 · Report ↗
State Variable Should Be Declared Constant
Sonic Inu · CertiK · 18 May 2023 · Report ↗
Typo
Sonic Inu · CertiK · 18 May 2023 · Report ↗
Newest first
| Report | Security firm | Date | Scope | Critical findings | Findings | Source |
|---|---|---|---|---|---|---|
| Sonic Inu | Security firm: CertiK | Date: | Scope: 1 address on BNB Chain | None open | Findings: 2 high · 3 medium · 13 low 2 fixed · 16 open | skynet.certik.com ↗ |
Statuses are the security firm’s own, from each report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 1 | 0 | 1 |
| Medium | 2 | 0 | 1 |
| Low | 13 | 0 | 0 |
All `SonicInu` tokens are sent to the owner when deploying the contract. Therefore the owner completely determines the token distribution.
Open the reportThe 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 reportThe 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 reportIn 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 reportThe 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 reportThe 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 reportFunctions that update state variables should emit relevant events as notifications.
Open the reportThe `_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 reportThe 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 reportThere is a typos in the codebase: - "UNLICENSE" should be "UNLICENSED"
Open the reportThe 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 reportThe event `FeesChanged` was defined in the contract `Sonic Inu` but was not used on the codebase.
Open the reportThe 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 reportThe variable `_lastSell` is not used in the codebase. ```solidity=135 mapping(address => uint256) private _lastSell; ```
Open the reportThe 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 reportIt 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| Address | Chain | Source code |
|---|---|---|
| 0x066c…544b0x066cda0cca84e9c6ed0a4ecb92aa036a9582544b | Chain: BNB Chain | Source code: Verified source |
Trustblock holds 1 public audit report for Sonic Inu, dated 18 May 2023. The latest is by CertiK (“Sonic Inu”).
CertiK wrote the report Trustblock holds for Sonic Inu.
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.
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.
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.
<head><script src="https://widget.trustblock.run/project-widget.min.js" defer></script></head><body><divdata-tb-project-widgetdata-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