Skip to content
critical Token Standards No SWC entry CWE-284

Unsafe / Unprotected Minting

SAFE-0053 Token Standards Checked automatically by the scanner
1

What goes wrong

A mint function lacks access control, supply caps, or proper accounting, letting an attacker mint unlimited tokens and dump or drain liquidity (infinite mint).

2

How to fix it

the pattern that is safe
function mint(address to, uint256 amt) external onlyRole(MINTER_ROLE) {
    require(totalSupply() + amt <= MAX_SUPPLY, "cap");
    _mint(to, amt);
}
◆
Gate and cap all minting.
3

Related vulnerabilities in Token Standards

SAFE-0051Missing SafeERC20 / Non-Standard Token Handling high · Token Standards SAFE-0052Fee-on-Transfer / Rebasing Token Accounting Mismatch high · Token Standards SAFE-0055Burn Authorization / Burn-From Missing Checks high · Token Standards SAFE-0107Fee-on-Transfer / Rebasing Token Mis-Accounting high · Token Standards SAFE-0208Non-Standard ERC20 Return Value Not Handled high · Token Standards SAFE-0050ERC-20 Approval Race Condition medium · Token Standards SAFE-0054ERC-721/1155 Missing Receiver Validation (Safe Transfer) medium · Token Standards SAFE-0056EIP-2612 Permit Misuse / Front-Running medium · Token Standards
← PreviousFee-on-Transfer / Rebasing Token Accounting Mismatch
Check your own contract for this

The SaferICO scanner runs 201 detectors over your Solidity source, SAFE-0053 among them. Paste an address or the source itself — a small per-scan fee, shown before you sign, or unlimited on any plan.

Run the scanner See how it is attacked Read the docs