Kraken Users Got Locked Out After a Dust Attack From a Sanctioned HTX Wallet - Startup Fortune

Kraken customers were locked out after about 12,000 tiny crypto transfers hit deposit addresses from wallets tied to sanctioned HTX. The transfers were small. The compliance problem wasn't.

Between August 17 and August 24, wallets that blockchain analytics firm Arkham Intelligence linked to HTX, the exchange formerly known as Huobi, sent roughly 12,000 tiny transfers to Kraken-related addresses, according to Bloomberg. Most were worth only a few cents to a few dollars. That was enough to trip Kraken's sanctions checks and temporarily restrict some customer accounts.

That distinction matters. The story isn't that 12,000 customers were frozen. Kraken hasn't said how many users were affected. The sharper point is that a large batch of unwanted deposits, each too small to matter financially, was enough to turn ordinary customers into compliance cases they didn't create.

"We don't know who is behind these attacks, but they likely expect that if sanctioned funds land in a client account, it triggers a full account lock, causing operational disruption for a large number of users," a Kraken spokesperson told Bloomberg. Kraken also said the transfers appeared to be an attempt to spread UK and EU sanctioned funds across other platforms and undermine trust in the industry.

That's a remarkable admission. Kraken is describing its own compliance system as the attack surface.

The EU just put HTX on a crypto blacklist and gave itself the power to cut off entire countries

The EU's 21st Russia sanctions package, adopted July 23, 2026, bans 14 crypto exchanges including HTX from transacting with EU entities starting August 23. More significantly, Brussels introduced a first-ever country-level blacklist tool for crypto, allowing it to cut off entire national crypto sectors that facilitate Russian sanctions evasion... - EU crypto blacklist HTX sanctions - how Russia uses crypto exchanges

Dusting attacks are old news in crypto. Normally someone sends tiny amounts of a token to many wallets to track spending patterns and try to connect addresses to real users. This case was different. Nobody needed to trace anything. The sender only needed a public blockchain, wallets associated with a sanctioned entity, and Kraken-linked deposit addresses. Anyone can send crypto to an address without permission. Send tainted dust to enough places and the exchange's own controls do the disruptive work.

HTX has denied initiating the transfers. Bloomberg reported that an HTX spokesperson said the exchange's review had found no evidence it sent them, and raised possible explanations including faulty attribution or third-party activity. Kraken hasn't accused HTX's leadership directly. It has restored account access while continuing to hold the flagged funds separately, which is exactly the kind of dry compliance detail that tells you how little room exchanges have once sanctioned funds touch an account.

The timing is hard to ignore. The UK sanctioned Huobi Global S.A. on May 26 as part of a Russia sanctions package, with CoinDesk reporting that the action targeted crypto firms accused of helping Russia evade restrictions. The EU then added "HTX (HUOBI GLOBAL SA)" to its Russia sanctions regime in July, with a transaction ban taking effect on August 23, according to The Block. That date fell right inside the eight-day window when the dust was landing at Kraken.

The trigger worked too well

Here's the uncomfortable part. Kraken doesn't appear to have been running a broken system. It was running the kind of system regulators expect licensed exchanges to run: screen incoming funds, flag sanctioned exposure, freeze or restrict activity while the review happens. If you're a customer, that feels absurd when the deposit is unsolicited and worth pennies. If you're the exchange, ignoring it can create a sanctions problem.

Frankly, this looks a lot like swatting for crypto accounts. You don't need to steal a password. You don't need to crack a wallet. You just need enough sanctioned dust and enough addresses, and you can make a platform lock people out by forcing it to follow its own rules.

That should bother every exchange, not only Kraken. Coinbase, Binance, OKX, Bybit, you name it, any large venue with sanctions exposure has to decide what happens when a user receives funds they didn't ask for from a flagged address. Treating every contact as user activity punishes the wrong person. Treating it too lightly risks letting sanctioned funds move through the system.

Kraken says it moved quickly to restore access once reviews cleared. Good. But speed after the freeze doesn't solve the design problem before it. The industry now has a public example of sanctions screening being turned into a denial-of-service tool, and the fix can't just be telling customers not to touch strange deposits. In this case, they didn't have to touch anything.

Crypto traders got refunds when SpaceX tokens ran out

xStocks saw more than $1 billion in demand for tokenized SpaceX shares, but partner exchanges including Bybit and Bitget Wallet received no allocations and refunded users. The episode shows that tokenized IPO access still depends on securing the scarce shares underneath the token. - crypto traders got refunds for SpaceX tokens - why SpaceX tokenized IPO access failed immediately

The next test is whether exchanges and screening vendors can separate unwanted dust from customer-directed transfers without opening a loophole sanctions evaders can walk through. That won't be clean. Public blockchains don't ask permission, and compliance systems were built to spot contact, not intent. Until that changes, a few cents of toxic crypto can still do more damage than its price suggests.

Also read: Circle and Coinbase Shares Slide as Banks Move to Kill Stablecoin Yield * BitMart Stops Trading While Its Founder Dismisses Withdrawal Demands * The SEC Just Sent Its Crypto Custody Rule Rewrite to the White House