As of 3 Nov 2026, Sanji Inu has 2 audit reports by 2 security firms on Trustblock; the latest is by CertiK, dated 22 Sep 2022. Those reports list no open critical findings. It also holds 1 deployed contract on 1 chain.
Record last updated . It holds audits, findings and contracts up to Nov 2026, and incidents up to Oct 2026. Trustblock does not review code.
Newest first
Statuses are the security firm’s own, from each report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 0 | 3 | 0 |
| Medium | 0 | 1 | 0 |
| Low | 13 | 0 | 0 |
`public` functions that are never called by the contract could be declared as `external`. `external` functions are more efficient than `public` functions.
Open the reportThe SANJI token is a fork of the famous Safemoon token. However, the addLiquidity() function has been removed. Without it, the trading pair may suffer poor liquidity.
Open the reportAddresses should be checked before assignment or external call to make sure they are not zero addresses. ```solidity=135 _owner = newOwner; ``` - `newOwner` is not zero-checked before being used. --- ```solidity=325 _developmentAddress = dev; ``` - `dev` is not zero-checked before being used. --- ```solidity=332 _marketingAddress = markt; ``` - `markt` is not zero-checked before being used.
Open the reportA sandwich attack may happen when an attacker observes a transaction swapping tokens or adding liquidity without setting restrictions on slippage or minimum output amount. The attacker can manipulate the exchange rate by front running (before the transaction being attacked) a transaction to purchase one of the assets and make profits by back running (after the transaction being attacked) a transaction to sell the asset. The following functions are called without setting restrictions on slippage or minimum output amount, so transactions triggering these functions are vulnerable to sandwich attacks, especially when the input amount is large: - `swapExactTokensForETHSupportingFeeOnTransferTokens()`
Open the reportThe 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=169 IUniswapV2Router02 public uniswapV2Router; ``` - The contract `Sanji_Inu` interacts with third-party contract with `IUniswapV2Router02` interface via `uniswapV2Router`. --- ```solidity=317 function rescueForeignTokens(address _tokenAddr, address _to, uint _amount) public onlyDev() { ``` - The function `Sanji_Inu.rescueForeignTokens` interacts with third party contract with `Token` interface via `_tokenAddr`.
Open the reportThe return value of the transfer()/transferFrom() call is not checked. ```solidity=319 Token(_tokenAddr).transfer(_to, _amount); ```
Open the reportThe `SafeMath` library is used unnecessarily. With Solidity compiler versions 0.8.0 or newer, arithmetic operations will automatically revert in case of integer overflow or underflow. ```solidity=70 library SafeMath { ``` - An implementation of `SafeMath` library is found. --- ```solidity=142 using SafeMath for uint256; ``` - `SafeMath` library is used for `uint256` type in `Sanji_Inu` contract. ```solidity=237 _approve(sender, _msgSender(), _allowances[sender][_msgSender()].sub(amount, "ERC20: transfer amount exceeds allowance")); ``` - `SafeMath.sub` is called in `transferFrom` function of `Sanji_Inu` contract. *Note: Only a sample of 2 `SafeMath` library usage in this contract (out of 24) are shown above.*
Open the reportOne or more state variables are never used in the codebase. Variable `_previousOwner` in `Ownable` is never used in `Sanji_Inu`. ```solidity=110 address private _previousOwner; ``` ```solidity=140 contract Sanji_Inu is Context, IERC20, Ownable { ``` --- Variable `_tOwned` in `Sanji_Inu` is never used in `Sanji_Inu`. ```solidity=144 mapping (address => uint256) private _tOwned; ``` ```solidity=140 contract Sanji_Inu is Context, IERC20, Ownable { ```
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=308 _developmentAddress.transfer(amount.div(2)); ``` - `Sanji_Inu.sendETHToFee` uses `transfer()`.
Open the reportThe report gives no description here.
Open the reportThe report gives no description here.
Open the reportThe report gives no description here.
Open the reportThe report gives no description here.
Open the report| Address | Chain | Source code |
|---|---|---|
| 0xa9f0…070c0xa9f059f63cd432b65a723eeeff69304fd780070c | Chain: BNB Chain | Source code: Verified source |
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="sanji-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