Kraken Freezes Accounts After HTX Dust Attack Claim

Points of Focus

• HTX-linked wallets sent 12,000 tiny transfers to Kraken addresses over eight days.
• Kraken calls it a dust attack aimed at triggering sanctions-driven account freezes.
• Kraken’s own sanctions policy would freeze the funds regardless of intent.

Kraken said wallets linked to sanctioned exchange HTX sent roughly 12,000 small transfers, most worth a few cents to several dollars, to Kraken-related addresses between Aug. 17 and Aug. 24, temporarily locking some customer accounts in the process, Bloomberg reported on Aug. 25.

Digital-assets exchange Kraken said some customers were temporarily locked out of their accounts after tiny amounts of cryptocurrency were sent to them from a wallet linked to sanctioned rival HTX https://t.co/WYxhxfJPRs

— Bloomberg (@business) August 25, 2026

What Kraken says the HTX dust attack was designed to do

A Kraken spokesperson described the transfers as a dust attack aimed at spreading UK- and EU-sanctioned funds across other platforms and undermining trust across the industry.

NEW: Kraken users face temporary account lockouts following a coordinated dusting attack from sanctioned wallets.

Arkham Intelligence identified 12,000 transfers sent to Kraken-linked addresses from an HTX wallet this month.

The European Union sanctioned Chinese exchange HTX in… pic.twitter.com/nU3cdDYwnP

— Zubiqo (@zubiqo) August 26, 2026

The apparent goal, Kraken said, was that once sanctioned funds landed inside a customer account, the account itself would get locked entirely, not just the tainted funds. Kraken said it has since restored access for affected users while continuing to freeze the specific sanctioned funds and is working with authorities to limit further harm.

HTX denies direct involvement and said it’s investigating, with a spokesperson suggesting the source of the transfers may have been misidentified or carried out by a third party.

Arkham Intelligence’s classification of the wallet as HTX-linked rests on an address HTX itself disclosed during its own proof-of-reserves process, a meaningfully different standard of evidence than a direct admission, worth stating precisely rather than treating the attribution as settled fact.

Why Kraken’s own sanctions policy complicates the attack claim

The detail that complicates Kraken’s framing is Kraken’s own compliance obligations. The UK sanctioned HTX operator Huobi Global SA in May over its alleged role in helping Russia evade sanctions, with the EU following in July.

Under those sanctions, Kraken’s policy requires it to freeze any funds traceable to HTX, regardless of who sent them or why. That means the account freezes Kraken cites as evidence of a targeted attack could equally be its own compliance system functioning exactly as designed, whether the transfers were a deliberate campaign, an accident, or a third party spoofing HTX’s wallet to cause this kind of disruption.

How dust attacks fit a wider pattern of crypto compliance risk

A blockchain security executive who’s quoted in coverage of the incident described it as functioning like poisoning a user’s transaction history since anyone can send assets to any wallet on a public blockchain without permission, letting attackers manipulate a target’s transaction flows at very low cost.

This specific attribution needs independent verification against a source on AlphaWire’s permitted list before it can be run as a named quote.

The pattern extends beyond this one dispute. Since the UK and EU sanctions took effect, Bybit, OKX, and Binance have all separately restricted or reviewed transactions linked to HTX, with the EU’s transaction ban reaching full effect on Aug. 23, in the middle of the disputed transfer window.

Regulators have leaned toward strict enforcement in comparable cases before. Historical precedent involving the Office of Foreign Assets Control’s sanctions on Tornado Cash and subsequent guidance on unsolicited sanctioned transfers reaching unwitting recipients would strengthen this point.