A transfer that didn't ask for anything back
A USDT transfer shows up in your history from an address you don't recognize, or from one close enough to a wallet you've paid before that the difference is easy to miss. That's address poisoning. Someone builds a lookalike address that shares enough characters with a real one and places it in your transaction history, so a later payment goes to their wallet.
Tether issues USDT from exactly one contract per network, so you can compare the contract on any transfer against a fixed reference. A wallet's balance is a single number per address: a received transfer is added to it, and nothing keeps it apart from what was already there. A tiny poisoning transfer therefore sits in the same balance and the same history as your real payments, and your wallet does nothing to mark it as different. You have to check the sender's address and the token contract yourself.
This article shows how to tell a genuine address from a lookalike with a block explorer. The sources we used for it include no wallets we have flagged for address poisoning, so we can't say who sends these transfers or how often. What follows covers only the mechanics you can check yourself.
Why matching first and last characters isn't a match
A poisoning address is built to resemble one you already trust, often sharing the characters at the start and the end while differing in the middle. Those are the characters most people glance at when copying an address out of their history, which is exactly why an address built for this purpose is made to match them.
Reading the full string is the only way to catch the difference. An explorer shows the complete address beside every field you need to judge the transfer, so you don't have to rely on the first and last few characters.
Made-up example: a wallet you've paid before starts with 0x9F2a and ends with 7cE4. An address built to poison your history could open and close with those same characters and swap several in the middle. It would then arrive attached to a transfer worth a tiny amount, so it sits in your records without drawing attention.
The one contract that proves the token is really USDT
A token can call itself USDT and still not be Tether's USDT. Tether's only contracts are TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t on TRON and 0xdAC17F958D2ee523a2206206994597C13D831ec7 on Ethereum. A token minted from any other contract isn't the stablecoin Tether backs, whatever name or symbol it displays in a wallet app.
The contract address on the transfer settles whether the token is genuine. The name your wallet displays proves nothing. A lookalike address attached to a genuine USDT transfer is still a lookalike address, and a lookalike address attached to a token from the wrong contract is a second, separate problem.
What Tronscan and Etherscan put in front of you
On Tronscan, searching an address or a transaction hash shows each TRON transfer's sender, recipient, token contract, amount and time. Etherscan shows the same five fields for Ethereum transfers.
The contract field tells you whether the token is really USDT. The amount and the time show whether the transfer looks like a real payment or a near-empty one sent only to land in your history.
Four checks before you trust a saved address
Run these in order before you pay an address pulled from your history, or one offered to you by someone else:
- Open the address or transaction on Tronscan for TRON or Etherscan for Ethereum. Read the full address character by character, the middle ones included, against a copy the recipient gave you directly (the fourth step covers how to get one).
- Compare the contract address the explorer shows against Tether's published contracts, TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t on TRON or 0xdAC17F958D2ee523a2206206994597C13D831ec7 on Ethereum. Any other contract means the token isn't USDT, whatever it's labelled.
- Check the amount and the time of the transfer. One worth a tiny amount, arriving with no prior contact from the sender, fits a poisoning attempt rather than a genuine payment.
- Don't copy the address you're about to pay out of a past transaction. Get it fresh from the person or platform you're dealing with, then recheck it against what the explorer shows before you send.
- If you're unsure about the wallet behind the address, run it through TrustSniffer's wallet checker. The result is a risk rating for the address itself, based on its on-chain record. It can't tell you whether this particular transfer is poisoning, so do the explorer checks above as well.
When the characters don't match, stop there
If the full address doesn't match what you saved, or the contract isn't one of Tether's two, don't send to it. Don't reuse an address pulled from a transaction you didn't start yourself.
If everything matches and the transfer history looks like an ordinary payment, go ahead with the address you intended to use in the first place. If the result is unclear, for instance the transfer history is too new to judge, treat the address as unverified and ask the counterparty to confirm it through a separate channel before you pay.
If a website asking you to pay gave you the address, check the site too with TrustSniffer's website checker. It covers the website itself, which the explorer checks above can't see. If it flags the site, hold the payment.


