Skip to content
high Token Standards No SWC entry CWE-682

Fee-on-Transfer / Rebasing Token Accounting Mismatch

SAFE-0052 Token Standards Checked automatically by the scanner
1

What goes wrong

The protocol credits users the nominal transfer amount, but a fee-on-transfer or rebasing token delivers less (or a changing amount), so internal accounting exceeds real holdings and the last users cannot withdraw.

2

How to fix it

the pattern that is safe
uint256 b0 = token.balanceOf(address(this));
token.safeTransferFrom(msg.sender, address(this), amt);
deposits[msg.sender] += token.balanceOf(address(this)) - b0;
◆
Account for real received amounts on elastic tokens.
3

Related vulnerabilities in Token Standards

SAFE-0053Unsafe / Unprotected Minting critical · Token Standards SAFE-0051Missing SafeERC20 / Non-Standard Token Handling 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
← PreviousMissing SafeERC20 / Non-Standard Token Handling
Check your own contract for this

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