This is the report from a security audit performed on Maximine Coin (MXM) by gorbunovperm.
Audit Top 200 CoinMarketCap tokens.
Maximine Coin (MXM)
In total, 5 issues were reported including:
-
0 high severity issue.
-
0 medium severity issues.
-
4 low severity issues.
-
1 owner privileges.
-
0 note.
-
It is possible to double withdrawal attack. More details here
-
Lack of transaction handling mechanism issue. WARNING! This is a very common issue and it already caused millions of dollars losses for lots of token users! More details here
Add into a function transfer(address _to, ... )
following code:
require( _to != address(this) );
According to ERC20 standard when coins are minted(or burned) a Transfer
event should be emitted.
- Line 41, 163, 181.
According EIP20 Standard the transfer
function should returns boolean value function transfer(address _to, uint256 _value) public returns (bool success)
. But here it is not implemented.
- Line 76.
EIP20 says that:
Transfers of 0 values MUST be treated as normal transfers and fire the Transfer event. But in this contract, function
transfer
has a condition:
require(balanceOf[_to] + _value > balanceOf[_to]);
- Line 56.
The contract owner allowed to pause transfer functions for certain user.
- Line 86, 77, 111, 128.
There are no serious vulnerabilities were discovered here.