Decats

init function basically acts as an initialise function for the contract. creator, totalSupply, name, decimals, and symbol are set through this function. As well as, the creator address’s balance is set with total supply.Attackers/Searchers can front-run the init call transaction by looking at the mempool. Through this, they can set the values mentioned above and steal tokens. This is happening because the function is public, and there is no check on who the caller is. This is not a high-severity issue because the contract is deployed and live already.

There is no protection for race condition through the approve function. For Example, if Alice approves 10 tokens to Bob, later wants to change the approval to 5 tokens and calls the approve function which will create a transaction. Bob can look into the mempool and notice that approval is changed. Then, Bob will send a transaction (call transferfrom) with a higher gas price than the approval transaction to transfer 10 tokens to himself. Later, 5 tokens approval transaction is executed, and Bob can get 5 more tokens as well. Alice wanted to send 5 tokens but instead gave out 15 tokens. The contract is not inheriting OpenZeppelin’s ERC20 contract.

Each slot in the storage is 32 bytes in size. decimals and initialized only use 1 byte, but both are defined between 32-byte size variables. This creates new slots just for 1-byte variables, and total number of slots is 6.

The contract is using 0.6.9 solidity version, which is old and contains vulnerabilities. Using the latest stable solidity version will prevent vulnerabilities.