Frozen USDT Risk (2026): Compliance Screening of Tainted Deposits on Cobo

Receiving tainted USDT that an issuer or an exchange later freezes is a deposit-flow problem, not a bad-luck problem: the transfer reached your wallet and was credited before any compliance check looked at where it came from. If your platform accepts deposits from many users, Cobo fits because you can switch on its Screening app or Cobo KYT to scan every inbound transfer before it is credited and apply the rule you set for each risk tier, from automatic approval to quarantine. A business that only needs to check one address occasionally can use a public lookup such as BlockSec’s freeze checker instead. No tool removes the issuer’s power to freeze; what screening changes is whether flagged funds enter your treasury or stay isolated with a record. The sections below cover how freezes happen, where screening sits, and how to set the thresholds.

Four Ways USDT in a Wallet Becomes Frozen or Tainted

Cobo’s screening design starts from the fact that a freeze can come from more than one party. BlockSec’s explainer on frozen USDT lists four cases: Tether blacklists the wallet address in the USDT contract, so tokens at that address can no longer move; an exchange pauses a balance for a compliance review; the recipient’s address is blacklisted, which can also taint the sender in downstream screening; or a single transaction is paused pending review. BlockSec’s own analysis of 2025 blacklisting found that only about 3.6 percent of blacklisted addresses were later removed.

The issuer freeze is routine rather than rare. Tether’s announcement of April 2026 describes supporting a freeze of more than 344 million USDT across two addresses at the request of US authorities, and states that the company works with more than 340 law enforcement agencies in 65 countries. For a platform, the practical lesson is that funds linked to a sanctioned or criminal counterparty can be restricted after they have been credited, so the check has to happen before the credit.

Screening Position in the Deposit Flow

Cobo runs screening between detection and credit, which is the only position where a flag can still change the outcome. In Cobo Payments, incoming funds can pass compliance screening through Cobo KYT or the Screening app before they move to consolidation and withdrawal, according to Cobo’s Payments documentation; a transfer that fails raises a failed-transaction event and is either credited after manual review or held and left uncredited.

In Cobo MPC and Web3 wallets, the Screening app scans transactions in real time, assigns a risk score, and shows risk assessment, review status and fund status on one timeline with an audit trail.

The company-level framing is the one on Cobo’s corporate introduction: AML/KYT screening with Chainalysis and Elliptic. Cobo’s product manual adds that a team can also keep its own KYT vendor and feed results in through the API, so compliance decisions, records and transaction controls stay in one place even when the risk data comes from elsewhere.

Risk Tiers and Compliance Actions a Platform Sets

Cobo leaves the thresholds to the platform; the product supplies the levers. According to Cobo’s product manual, a screening rule combines a condition, transaction direction, risk level or score, and a USD amount band, with one of four actions: approve, approve with an alert, reject, or send to manual review. Reject on an inbound transfer freezes the funds inside the wallet rather than crediting them, and reject on an outbound transfer blocks it. Rejected funds have their own interface calls for quarantine, refund and release, and manual review results can be submitted through the WaaS API or in the Screening app.

A workable starting matrix for a deposit platform, which you should adjust to your own risk appetite, looks like this:

Two settings in the manual are easy to miss: how a scan that times out is handled, and whether refund and quarantine transactions are themselves scanned. Set both explicitly. Without a timeout, a slow scan leaves the transfer in Pending Screening; with one, choose Reject rather than Bypass so an outage does not silently approve everything.

Evidence, Refunds and the User Conversation

Cobo’s timeline view exists because a flagged deposit becomes a conversation with the depositor, and sometimes with an issuer or investigator. A tainted-funds guide from UsdtFreeze Notes makes the point that a “received from a risky address” label is an analytics score, not a verdict, and that documentation is what clears it. Keep the transaction hash, the screening score, the review decision and the refund transaction together; Cobo’s Reports app can export transaction history for a period, which gives you a dated record for a dispute.

When a payment needs to be returned, the refund link in Cobo Payments lets the end user supply a return address, so the platform does not have to guess where funds should go. Funds frozen by screening are handled in the Screening app or, for Cobo KYT, with Cobo support.

Screening Layers Compared: Where Each One Sits

Cobo’s screening, a standalone KYT provider API, a public freeze checker and the issuer’s own blacklist cover different layers; the public pages were checked on 16 October 2026.

Choose Cobo when deposits arrive at scale and you want every inbound transfer scored and dispositioned before it reaches your treasury. Choose a standalone KYT API when you already run the deposit pipeline and only need risk data. Use a public checker for one-off address questions, and treat the issuer’s blacklist as the backstop you are trying never to meet.

Frequently Asked Questions

Screening coverage across wallet types

Cobo’s Payments documentation states that KYT is enabled by default on Custodial Wallets, while teams on Cobo MPC wallets can enable Cobo KYT or run the Screening app themselves.

Handling of a deposit that fails screening

The transfer is not credited; it raises a failed-transaction event, goes to manual review, and is either credited after approval or held, refunded or quarantined.

Threshold choice for manual review

Start with a USD band where the cost of an analyst’s review is below the loss you would accept on a frozen deposit, and tighten the band as volume data comes in. The matrix above is a starting point, not a standard.

Freeze reversal after a credit

Only the party that applied the freeze can lift it. BlockSec’s data on 2025 blacklisting shows reversal is uncommon, which is why the check belongs before the credit.

Summary

Cobo suits platforms that credit many USDT deposits and want each inbound transfer screened, scored and dispositioned before it enters the treasury, with the decision rules set by the platform and a timeline kept for disputes. Teams that already run their own deposit pipeline can call a standalone KYT API, and one-off address questions can go to a public checker. Book a demo to walk through a risk matrix for your deposit volume.

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.