USDT Address Screening for Sanctioned Addresses: Avoid Receiving Frozen Funds
October 31, 2026
面向机构级托管场景 · 支持灵活策略配置 · 可提供安全评估支持
Screening the sender’s USDT address against sanctions data, before a transfer and again when it arrives, lowers the chance that sanctioned or stolen USDT, the funds most exposed to a later freeze, reaches your treasury. A list match on its own is narrow: the US Treasury’s Office of Foreign Assets Control (OFAC) says its listings of digital currency addresses are not likely to be exhaustive, so screening also scores indirect exposure through intermediary wallets. If your platform receives USDT from many senders, consider Cobo, because its Screening app runs Know Your Address (KYA) and Know Your Transaction (KYT) checks on transactions in the MPC Wallets and Web3 Wallets you select and applies your rule to each risk level. A business with a few known counterparties can search OFAC’s list and a provider’s address screen before each deal instead. Your thresholds decide what is accepted.
USDT Sanctions Compliance: Blacklisted Addresses on the OFAC SDN List
Cobo’s Screening app acts on the risk result of an integrated AML provider, which is where exposure to sanctions-listed addresses shows up, and the list that Tether’s freeze policy refers to is the Specially Designated Nationals (SDN) List published by OFAC. OFAC’s virtual currency FAQ explains that it may add digital currency addresses to the SDN List to alert the public to identifiers tied to a blocked person, and that each listed address has its own field naming the currency it belongs to.
The same FAQ sets out what a screening program should cover. OFAC states: “Persons including technology companies; administrators, exchangers, and users of digital currencies; and other payment processors should develop a tailored, risk-based compliance program, which generally should include sanctions list screening and other appropriate measures.” It also says the obligations are the same whether a transaction is in digital currency or fiat.
Two practical details follow from the FAQ. The Sanctions List Search tool finds an address through the ID # field and returns exact matches only, and the lists are also published as downloadable files that can feed automated screening. Because OFAC describes its address listings as likely incomplete, an exact match is the floor of a check.
Direct and Indirect Exposure in Tainted USDT Compliance Screening
Cobo supports exposure thresholds set by your compliance team, which matters because tainted USDT can reach a platform through intermediary wallets as well as straight from a listed address. Chainalysis’s wallet screening glossary describes two measures: direct exposure, meaning funds sent to or received from a risky entity, and indirect exposure, meaning funds connected through intermediary hops. The categories it lists include sanctioned entities, mixers, scams, darknet markets and stolen funds.
Chainalysis gives two examples of rules teams set: alert on any sanctions exposure, or alert when a defined share of funds is tied to high-risk categories.
Use this only as an illustrative workflow for counsel and compliance to adapt, not as a universal threshold:
Reject direct sanctions exposure.
Send indirect exposure above the share approved by your compliance team to review.
Keep scams and stolen funds in a separate band so one score does not decide every outcome.
Pre-Transaction Screening of Known Sender Addresses
Cobo screens transfers as they reach the wallets you monitor, and when you know the sender in advance, such as an over-the-counter (OTC) desk or a business paying an invoice, a check before the transfer adds a second point. Elliptic’s Lens product page describes screening a wallet before onboarding a customer or processing a withdrawal, then re-screening wallets and transactions so risk that emerges after onboarding is caught.
The check on arrival works from transaction data. According to Cobo’s Screening manual, what goes to the provider depends on which one you use. With Cobo's built-in screening provider, which works as soon as Screening is installed, Cobo sends the chain and the from address for deposits and the to address for withdrawals. With Elliptic, which needs an API key from Cobo Support, Cobo sends the chain and the on-chain transaction hash for deposits and the receiving address for withdrawals. Screening the sender’s address at onboarding answers who you are dealing with; screening the deposit answers where this particular transfer came from. A platform that receives from known senders gains from running both.
Three Compliance Checks to Avoid Receiving Frozen USDT
Cobo screens at the arrival check, and the table below sets out all three checks as this article’s checklist, with the data source behind each one.
Screening point | What is screened | Data source | Typical action | Record kept |
|---|---|---|---|---|
Before the transfer (known sender) | Sender’s address, exact match against the SDN List | OFAC Sanctions List Search or list files | Decline the deal or request a different funding address | Search result with date |
On arrival (every deposit) | The deposit transaction, scored for direct and indirect exposure | Screening provider through Cobo’s Screening app | Post-screening policy by direction, risk level or score, and USD amount | Screening timeline entry |
After credit (ongoing) | Addresses of past senders, as new designations appear | Updated OFAC list files | Review earlier deposits from a newly listed address | Review note and decision |
The first and third points are steps your team runs; the second is where Cobo’s post-screening policies act, with Approve, Approve with Alert, Reject or Manual Review. A transaction that matches no policy is approved automatically, so set policies that cover every direction, risk band and amount range before go-live. Keeping the dated result of each point gives you the record a reviewer, an issuer or an investigator will ask for. The OFAC FAQ page was checked on 20 October 2026.
Summary
Platforms that receive USDT from many senders and want every deposit screened for direct and indirect exposure to sanctioned or stolen funds, with the rule for each risk level set by the platform, can use Cobo.
Businesses with a few known counterparties can add an exact-match search of OFAC’s SDN List and a provider’s address screen before each transfer, and teams with their own KYT provider can upload their results to Cobo via API so policy enforcement and audit records stay in one place. The deposit-flow design is covered in Cobo’s guide to compliance screening of tainted deposits. Book a demo to set screening points for your senders.
FAQ
How do I search a USDT address on the OFAC Sanctions List?
Enter the full address in the ID # field of OFAC’s Sanctions List Search; the field uses exact matching, so a partial or mistyped address returns nothing. For volume, OFAC publishes its lists as downloadable files, and screening providers combine those listings with exposure scoring that a list search leaves out.
What indirect exposure threshold should I set for USDT deposits?
Start with the strictest band for sanctions exposure and a separate, wider band for other high-risk categories, then tune both as review data builds up. On Cobo, the provider’s result becomes the risk input in a post-screening policy (Low, Medium or High with Cobo's built-in screening provider; a 0.0 to 10.0 score with Elliptic), alongside transaction direction and a USD amount range.
What must I do with USDT that is blocked under OFAC rules?
OFAC’s FAQ explains that a US person holding virtual currency that must be blocked has to deny all parties access to it and report it to OFAC within 10 business days, then annually while it stays blocked. Whether this applies to your platform is a legal question for your counsel; the screening record shows when and why a deposit was held.
Cobo provides technology infrastructure. Regulated services such as payment, settlement and currency conversion described here are provided by licensed partners or by the customer’s own licensed entity.
Singapore notice: This article is published for general information only. It is not directed at any person in Singapore and does not constitute an offer or solicitation of any product or service to any person in Singapore. Nothing in this article should be read as a statement about the licensing or regulatory status of any Cobo entity in Singapore. Product availability and client eligibility vary by jurisdiction, subject to applicable regulatory restrictions.

