Coinsult

Request your audit at coinsult.net

Advanced Manual
Smart Contract Audit

July 8, 2022

Audit requested by

Strike Crypto BSC

0x47B196a23B230f28e0495EF1693b4efdFB70E451

Strike Crypto BSC / Security Audit

Table of Contents

1. Audit Summary

1.1 Audit scope

1.2 Tokenomics

1.3 Source Code

2. Disclaimer

3. Global Overview

3.1 Informational issues

3.2 Low-risk issues

3.3 Medium-risk issues

3.4 High-risk issues

4. Vulnerabilities Findings

5. Contract Privileges

5.1 Maximum Fee Limit Check

5.2 Contract Pausability Check

5.3 Max Transaction Amount Check

5.4 Exclude From Fees Check

5.5 Ability to Mint Check

5.6 Ability to Blacklist Check

5.7 Owner Privileges Check

6. Notes

6.1 Notes by Coinsult

6.2 Notes by Strike Crypto BSC

7. Contract Snapshot

8. Website Review

9. Certificate of Proof

Strike Crypto BSC / Security Audit

Audit Summary

Audit Scope

Project Name

Strike Crypto BSC

Blockchain

Binance Smart Chain

Smart Contract Language

Solidity

Contract Address

0x47B196a23B230f28e0495EF1693b4efdFB70E451

Audit Method

Static Analysis, Manual Review

Date of Audit

8 July 2022

This audit report has been prepared by Coinsult’s experts at the request of the client. In this audit, the results of the static analysis and the manual code review will be presented. The purpose of the audit is to see if the functions work as intended, and to identify potential security issues within the smart contract.

The information in this report should be used to understand the risks associated with the smart contract. This report can be used as a guide for the development team on how the contract could possibly be improved by remediating the issues that were identified.

Strike Crypto BSC / Security Audit

Tokenomics

Rank Address Quantity (Token) Percentage
1 0x455f3ee7fb28addd87eeff757fbc3f7b8cf317fd 100,000,000 100.0000%

Source Code

Coinsult was comissioned by Strike Crypto BSC to perform an audit based on the following code:
https://bscscan.com/address/0x47B196a23B230f28e0495EF1693b4efdFB70E451#code

Strike Crypto BSC / Security Audit

Disclaimer

This audit report has been prepared by Coinsult’s experts at the request of the client. In this audit, the results of the static analysis and the manual code review will be presented. The purpose of the audit is to see if the functions work as intended, and to identify potential security issues within the smart contract.

The information in this report should be used to understand the risks associated with the smart contract. This report can be used as a guide for the development team on how the contract could possibly be improved by remediating the issues that were identified.

Coinsult is not responsible if a project turns out to be a scam, rug-pull or honeypot. We only provide a detailed analysis for your own research.

Coinsult is not responsible for any financial losses. Nothing in this contract audit is financial advice, please do your own research.

The information provided in this audit is for informational purposes only and should not be considered investment advice. Coinsult does not endorse, recommend, support or suggest to invest in any project. 

Coinsult can not be held responsible for when a project turns out to be a rug-pull, honeypot or scam.

Strike Crypto BSC / Security Audit

Global Overview

Manual Code Review

In this audit report we will highlight the following issues:

Vulnerability Level

Total

Pending

Acknowledged

Resolved

0

0

0

0

5

0

0

0

0

0

0

0

0

0

0

0

Privilege Overview

Coinsult checked the following privileges:

Contract Privilege

Description

Owner can mint?

Owner can blacklist?

Owner can set fees > 25%?

Owner can exclude from fees?

Owner can pause trading?

Owner can set Max TX amount?

More owner priviliges are listed later in the report.

Strike Crypto BSC / Security Audit

Contract contains Reentrancy vulnerabilities

Additional information: This combination increases risk of malicious intent. While it may be justified by some complex mechanics (e.g. rebase, reflections, buyback). 

More information: Slither

				
					State variables written after the call(s):
- administrationWallet = 0x2Bf7105Cd8aCf6F5b64548DE2A2eA8acF0983b86 (Strike_Crypto_Metaverse.sol#88)
- developingWallet = 0x2Bf7105Cd8aCf6F5b64548DE2A2eA8acF0983b86 (Strike_Crypto_Metaverse.sol#89)
- exemptFee[address(this)] = true (Strike_Crypto_Metaverse.sol#78)
- exemptFee[DEAD] = true (Strike_Crypto_Metaverse.sol#82)
- exemptFee[ownerWallet] = true (Strike_Crypto_Metaverse.sol#86)
- exemptFee[administrationWallet] = true (Strike_Crypto_Metaverse.sol#91)
- exemptFee[developingWallet] = true (Strike_Crypto_Metaverse.sol#93)
- liquidityPool = WBNB_TOKEN_PAIR (Strike_Crypto_Metaverse.sol#74)
- swapHelper = new SwapHelper() (Strike_Crypto_Metaverse.sol#95)
				
			

Recommendation

Apply the check-effects-interactions pattern.

Exploit scenario

				
					    function withdrawBalance(){
        // send userBalance[msg.sender] Ether to msg.sender
        // if mgs.sender is a contract, it will call its fallback function
        if( ! (msg.sender.call.value(userBalance[msg.sender])() ) ){
            throw;
        }
        userBalance[msg.sender] = 0;
    }
				
			
Bob uses the re-entrancy bug to call withdrawBalance two times, and withdraw more than its initial deposit to the contract.

Strike Crypto BSC / Security Audit

No zero address validation for some functions

Detect missing zero address validation.

				
					function setAdministrationWallet(address account) public isAuthorized(0) { administrationWallet = account; }
				
			

Recommendation

Check that the new address is not zero.

Exploit scenario

				
					contract C {

  modifier onlyAdmin {
    if (msg.sender != owner) throw;
    _;
  }

  function updateOwner(address newOwner) onlyAdmin external {
    owner = newOwner;
  }
}
				
			

Bob calls updateOwner without specifying the newOwner, soBob loses ownership of the contract.

Strike Crypto BSC / Security Audit

Functions that send Ether to arbitrary destinations

Unprotected call to a function sending Ether to an arbitrary address.

				
					function safeWithdraw() external isAuthorized(0) {
    uint256 contractBalance = address(this).balance;
    payable(_msgSender()).transfer(contractBalance);
  }
				
			

Recommendation

Ensure that an arbitrary user cannot withdraw unauthorized funds.

Exploit scenario

				
					contract ArbitrarySend{
    address destination;
    function setDestination(){
        destination = msg.sender;
    }

    function withdraw() public{
        destination.transfer(this.balance);
    }
}
				
			

Bob calls setDestination and withdraw. As a result he withdraws the contract’s balance.

Strike Crypto BSC / Security Audit

Missing events arithmetic

Detect missing events for critical arithmetic parameters.

				
					  // Excempt Controllers
  function setExemptFee(address account, bool operation) public isAuthorized(2) { exemptFee[account] = operation; }
  function setExemptFeeReceiver(address account, bool operation) public isAuthorized(2) { exemptFeeReceiver[account] = operation; }

  // Special Wallets
  function setAdministrationWallet(address account) public isAuthorized(0) { administrationWallet = account; }
  function setDevelopingWallet(address account) public isAuthorized(0) { developingWallet = account; }
				
			

Recommendation

Emit an event for critical parameter changes.

Exploit scenario

				
					contract C {

  modifier onlyAdmin {
    if (msg.sender != owner) throw;
    _;
  }

  function updateOwner(address newOwner) onlyAdmin external {
    owner = newOwner;
  }
}
				
			

updateOwner() has no event, so it is difficult to track off-chain changes in the buy price.

Strike Crypto BSC / Security Audit

Conformance to Solidity naming conventions

Allow _ at the beginning of the mixed_case match for private variables and unused parameters.

				
					Variable ERC20._balances (ERC20.sol#35) is not in mixedCase
Contract Strike_Crypto_Metaverse (Strike_Crypto_Metaverse.sol#11-322) is not in CapWords
Function Strike_Crypto_Metaverse.setWBNB_TOKEN_PAIR(address) (Strike_Crypto_Metaverse.sol#316) is not in mixedCase
Function Strike_Crypto_Metaverse.setWBNB_BUSD_Pair(address) (Strike_Crypto_Metaverse.sol#317) is not in mixedCase
Function Strike_Crypto_Metaverse.getWBNB_TOKEN_PAIR() (Strike_Crypto_Metaverse.sol#318) is not in mixedCase
Function Strike_Crypto_Metaverse.getWBNB_BUSD_Pair() (Strike_Crypto_Metaverse.sol#319) is not in mixedCase
Constant Strike_Crypto_Metaverse._name (Strike_Crypto_Metaverse.sol#17) is not in UPPER_CASE_WITH_UNDERSCORES
Constant Strike_Crypto_Metaverse._symbol (Strike_Crypto_Metaverse.sol#18) is not in UPPER_CASE_WITH_UNDERSCORES
Constant Strike_Crypto_Metaverse.decimal (Strike_Crypto_Metaverse.sol#21) is not in UPPER_CASE_WITH_UNDERSCORES
Constant Strike_Crypto_Metaverse.decimalBUSD (Strike_Crypto_Metaverse.sol#22) is not in UPPER_CASE_WITH_UNDERSCORES
Constant Strike_Crypto_Metaverse.maxSupply (Strike_Crypto_Metaverse.sol#23) is not in UPPER_CASE_WITH_UNDERSCORES
Variable Strike_Crypto_Metaverse._maxTxAmount (Strike_Crypto_Metaverse.sol#25) is not in mixedCase
Variable Strike_Crypto_Metaverse._maxAccountAmount (Strike_Crypto_Metaverse.sol#26) is not in mixedCase
Variable Strike_Crypto_Metaverse.WBNB_BUSD_PAIR (Strike_Crypto_Metaverse.sol#48) is not in mixedCase
Variable Strike_Crypto_Metaverse.WBNB_TOKEN_PAIR (Strike_Crypto_Metaverse.sol#49) is not in mixedCase
				
			

Recommendation

Follow the Solidity naming convention.

Rule exceptions

  • Allow constant variable name/symbol/decimals to be lowercase (ERC20).
  • Allow _ at the beginning of the mixed_case match for private variables and unused parameters.

Strike Crypto BSC / Security Audit

Contract Privileges

Maximum Fee Limit Check

Coinsult tests if the owner of the smart contract can set the transfer, buy or sell fee to 25% or more. It is bad practice to set the fees to 25% or more, because owners can prevent healthy trading or even stop trading when the fees are set too high. 

Type of fee

Description

Transfer fee

Buy fee

Sell fee

Type of fee

Description

Max transfer fee

Max buy fee

Max sell fee

Strike Crypto BSC / Security Audit

Contract Pausability Check

Coinsult tests if the owner of the smart contract has the ability to pause the contract. If this is the case, users can no longer interact with the smart contract; users can no longer trade the token.

Privilege Check

Description

Can owner pause the contract?

Strike Crypto BSC / Security Audit

Max Transaction Amount Check

Coinsult tests if the owner of the smart contract can set the maximum amount of a transaction. If the transaction exceeds this limit, the transaction will revert. Owners could prevent normal transactions to take place if they abuse this function.

Privilege Check

Description

Can owner set max tx amount?

Strike Crypto BSC / Security Audit

Exclude From Fees Check

Coinsult tests if the owner of the smart contract can exclude addresses from paying tax fees. If the owner of the smart contract can exclude from fees, they could set high tax fees and exclude themselves from fees and benefit from 0% trading fees. However, some smart contracts require this function to exclude routers, dex, cex or other contracts / wallets from fees.

Privilege Check

Description

Can owner exclude from fees?

Strike Crypto BSC / Security Audit

Ability To Mint Check

Coinsult tests if the owner of the smart contract can mint new tokens. If the contract contains a mint function, we refer to the token’s total supply as non-fixed, allowing the token owner to “mint” more tokens whenever they want.

A mint function in the smart contract allows minting tokens at a later stage. A method to disable minting can also be added to stop the minting process irreversibly.

Minting tokens is done by sending a transaction that creates new tokens inside of the token smart contract. With the help of the smart contract function, an unlimited number of tokens can be created without spending additional energy or money.

Privilege Check

Description

Can owner mint?

Strike Crypto BSC / Security Audit

Ability To Blacklist Check

Coinsult tests if the owner of the smart contract can blacklist accounts from interacting with the smart contract. Blacklisting methods allow the contract owner to enter wallet addresses which are not allowed to interact with the smart contract. 

This method can be abused by token owners to prevent certain / all holders from trading the token. However, blacklists might be good for tokens that want to rule out certain addresses from interacting with a smart contract.

Privilege Check

Description

Can owner blacklist?

Strike Crypto BSC / Security Audit

Other Owner Privileges Check

Coinsult lists all important contract methods which the owner can interact with.

⚠ Owner is able to burn tokens

⚠ Owner is able to revoke certain permissions

⚠ Owner is able to give addresses certain permissions

Strike Crypto BSC / Security Audit

Notes

Notes by Strike Crypto BSC

No notes provided by the team.

Notes by Coinsult

✅ No notes provided by Coinsult

Strike Crypto BSC / Security Audit

Contract Snapshot

This is how the constructor of the contract looked at the time of auditing the smart contract.

				
					contract Strike_Crypto_Metaverse is Authorized, ERC20 {
  address constant DEAD = 0x000000000000000000000000000000000000dEaD;
  address constant ZERO = 0x0000000000000000000000000000000000000000;
  address constant BUSD = 0xe9e7CEA3DedcA5984780Bafc599bD69ADd087D56;
  address constant WBNB = 0xbb4CdB9CBd36B01bD1cBaEBF2De08d9173bc095c;

  string constant _name = "Strike Crypto Metaverse";
  string constant _symbol = "STR";
				
			

Strike Crypto BSC / Security Audit

Website Review

Coinsult checks the website completely manually and looks for visual, technical and textual errors. We also look at the security, speed and accessibility of the website. In short, a complete check to see if the website meets the current standard of the web development industry. 

Type of check

Description

Mobile friendly?

Contains jQuery errors?

Is SSL secured?

Contains spelling errors?

Strike Crypto BSC / Security Audit

Certificate of Proof

Strike Crypto BSC

Audited by Coinsult.net

Date: 8 July 2022

Coinsult

coinsult.net

End of report
Smart Contract Audit

Request your smart contract audit / KYC

t.me/coinsult_tg