HTX has pushed back against claims that it orchestrated a wave of small USDT transfers that some users say triggered compliance freezes at Kraken and other exchanges. What happened - On Aug. 20, some users began reporting unsolicited microtransfers of USDT from addresses labeled as linked to HTX. Community observers suggested the transfers could be a form of “address poisoning” — or, more precisely in this case, “compliance poisoning” — intended to make recipients look like they’d interacted with a sanctioned or compliance-sensitive address and thus trip automated screening systems. - A community review flagged a batch of 7.5 USDT transfers from an HTX-labeled hot wallet to addresses attributed to Kraken. Available on-chain data, however, has not proven who controlled every sending address. HTX’s response - An HTX representative using the @HTX_Molly Twitter account said the exchange’s internal review found no activity from official company accounts that would indicate a coordinated campaign. The rep suggested some affected users may have initiated transfers themselves while trying to test or protest Kraken’s restrictions. - HTX said it had identified frozen funds at Kraken with a reported top amount of $4.2 million, but the exchange did not publish account records, transaction hashes, or Kraken communications to substantiate that figure. - HTX has opened a voluntary group to collect cases from Kraken customers who can’t access funds and to pursue releases, while it continues investigating the source of the transfers. Kraken and the regulatory backdrop - Kraken has confirmed a policy of restricting transfers associated with Huobi/HTX addresses. Those restrictions are grounded in U.K. sanctions: on May 26 the U.K. designated Huobi Global S.A. under its Russia sanctions regime, and the U.K. Office of Financial Sanctions Implementation (OFSI) has said that designation applies to HTX under U.K. sanctions rules. - Kraken has told affected customers to cooperate with document requests and contact support. The exchange says it may impose restrictions for sanctions compliance, security reviews, payment reversals or other checks — and has not stated that every incoming transfer from an HTX-labeled address automatically causes a full account freeze. - Whether a specific freeze is legally required depends on ownership, source, timing and the sanctions exposure in each case. Open questions and evidence gaps - Wallet labels alone don’t prove HTX authorized transfers. Exchange deposit addresses, payment processors, intermediaries and user-controlled withdrawal activity can all complicate attribution. Public transaction hashes and verified sending addresses are needed to independently test claims about origin and intent. - HTX’s initial review did not find a verified connection between the disputed transfers and subsequent account freezes, and the exchange has not released a complete address list or a final investigation report. - Kraken has not publicly confirmed the $4.2 million figure or that the microtransfers were the specific cause of the freezes. Terminology: “address poisoning” vs “compliance poisoning” - Classic address poisoning involves tricking users into later copying a fraudulent address and losing funds. The transfers reported here — if intentional — appear aimed at making recipients look like they’d received funds from a sanctioned source, thereby prompting compliance systems to act. If malicious intent is proven, “compliance poisoning” is a more precise label. - Current public evidence does not establish intent, and receiving an unsolicited transfer is not, by itself, proof that a recipient knowingly transacted with a sanctioned entity. What happens next - HTX says it will publish a final review including verified sending addresses and transaction hashes; Kraken may clarify how it evaluates unsolicited transfers and what documentation affected users need to restore access. - For now, the verified takeaways are narrow: the U.K. sanctions apply to HTX as interpreted by OFSI; Kraken restricts transfers tied to Huobi/HTX for regulatory reasons; and HTX denies authorizing the disputed microtransactions. The reported $4.2 million freeze and any coordinated poisoning campaign remain unverified. Practical advice for users - If your Kraken account is restricted, respond promptly to support and documentation requests. - Keep on-chain evidence (transaction hashes) and correspondence handy if you need to escalate or seek remediation. - Watch for HTX’s promised final report; it will be central to resolving attribution questions. This story is developing. We’ll update when HTX publishes its detailed review or when Kraken clarifies the link between the microtransfers and specific account restrictions. Read more AI-generated news on: undefined/news