Skip to content
low Token Standards No SWC entry CWE-703

Tokens Transferable to the Contract Itself (Locked)

SAFE-0210 Token Standards Checked automatically by the scanner
1

What goes wrong

transfer/mint allows the destination to be the token/contract's own address with no guard, silently locking tokens that no function can ever recover.

2

The vulnerable pattern

proof of concept — how it is exploited
// user fat-fingers transfer(tokenAddress, 1000)
// tokens now sit at address(this) with no sweep function -> gone.
3

How to fix it

the pattern that is safe
require(to != address(this) && to != address(0), "bad recipient");
◆
Reject transfers to address(this) or add a rescue path.
4

Related vulnerabilities in Token Standards

SAFE-0053Unsafe / Unprotected Minting critical · 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
← Previousapprove() Reverts on Non-Zero Allowance (USDT-style)
Check your own contract for this

The SaferICO scanner runs 201 detectors over your Solidity source, SAFE-0210 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