Tether USD (USDT) Smart Contract Risk
Missing Return Data
⚠ HIGH severityVulnerability
USDT does not return a boolean on transfer/transferFrom/approve, violating the ERC20 standard. Direct calls will revert on Solidity 0.8+ due to ABI decoding failure.
Related: Unchecked Return Values
Safe integration
Use OpenZeppelin SafeERC20 (safeTransfer, safeTransferFrom, safeApprove) instead of calling transfer/transferFrom/approve directly.
Contract addresses
| Chain | Address |
|---|---|
| Ethereum | 0xdac17f958d2ee523a2206206994597c13d831ec7 |
Audit any contract that interacts with USDT: SmartContract.us automatically detects USDT integration risks →
Chain & standard security guides
What this contract permits today
Read live from Ethereum on 2026-10-14. This is a different question from the integration risk above: not how to call the token safely, but what the holders of its keys are able to do to the people holding it.
| Question | Answer |
|---|---|
| Can new tokens be created? | Yes |
| Can transfers be blocked? | Yes |
| Is there a trading tax? | No |
| Can the logic be replaced? | No |
| Can liquidity be withdrawn? | Yes |
The permissions above rest with 0xC6CDE7C39eB2f0F0095F41570af89eFC2C1Ea828, itself a contract, which may be a multisig or a timelock. Whether that is acceptable depends on who holds it.