Share
Subscribe to the AlphaWire Newsletter
On August 18, 2026, pseudonymous trader 0xZiye posted on X that their Coinbase account, alongside many others, received 7.5 USDT from a wallet labelled as HTX. According to the trader’s post, Coinbase wanted an explanation for the transaction, or it would close the account.
The claim means that seven dollars from a sanctioned exchange could shut down anyone’s Coinbase funds, a severe threat for anyone utilizing digital assets.
孙哥是不是在报复社会。。
htx疯狂的往外转小额,污染其他地址。。
我的coinbase收到孙哥的7.5u投毒。。
目前coinbase说不解释清楚,就关户。。。 pic.twitter.com/Qz49RxTGOL
— 紫夜 (@0xZiye) August 18, 2026
That said, it’s important to note that Coinbase has not confirmed the situation as of this writing. Now, normally one could check a transaction’s information to learn more, but no sending address, transaction hash, or network was published. This presents a few questions: is the poster lying for some reason? Or if they’re telling the truth, how did this happen, and how can one replicate the scenario for testing purposes?
HTX head of markets @HTX_Molly replied to 0xZiye, stating the exchange had opened an internal investigation and that it would “not engage in such behavior”. The ever-so controversial Justin Sun, TRON founder and current HTX advisor, even calls the entire situation made up.
我们内部快速开会讨论了,我们官方绝对没有这种行为,要么是误会要么是有人故意使坏,我们会快速查清原因,给大家一个交代。
— 火币六爷|火币TradFi负费率 (@HTX_Molly) August 18, 2026
But if HTX did not initiate the transfers, what did? According to analyst 0xMoon, HTX’s review found 166 small USDT outflows from HTX wallet 48, noting that 15 addresses received exactly 7.5 USDT to Kraken-associated addresses instead of Coinbase. He also said HTX found no frozen Coinbase account and found no one else complaining aside from 0xZiye.
Sun’s response does stand against the HTX suspicions, but neither party published the 48 transaction hashes or any relevant wallet addresses. Both versions make accusations that should be testable on a public ledger, yet neither provided the information required to reproduce the test.
中午起床群友发给我这条帖子,因为我在HTX有放一些资产,由于当时有点事情出门,没能第一时间去调查,回家之后我马上去查了这件事情,发现了一些疑点。… https://t.co/83qajCUGv2 pic.twitter.com/7DqsVxGRyL
— 0xMoon (@0xMoon) August 18, 2026
HTX expanded upon its denial on August 20, according to Wu Blockchain. An internal review found no disputed transfers from official HTX accounts, with HTX Molly suggesting users may have sent the funds to test or protest Kraken’s restrictions, though this is not a final report.
HTX-Linked Address-Poisoning Reports Persist as Kraken Freezes User Funds of Up to $4.2 Million
HTX-Linked Address-Poisoning Reports Persist as Kraken Freezes User Funds of Up to $4.2 MillionHTX, one of the longest-running major crypto exchanges since its founding in 2013, said… pic.twitter.com/ICjnJRPjEE
— Wu Blockchain (@WuBlockchain) August 20, 2026
She also claimed the largest Kraken restriction HTX had found involved $4.2 million. HTX created a group to collect cases from affected Kraken users to assist further. However, HTX did not publish account records or hashes, and Kraken has not publicly confirmed these cases either.
So if the trader alleges a Coinbase compliance warning but won’t prove it, and HTX denies any involvement whatsoever, could this be some sort of attack?
It appears that the transaction source may be an address controlled by HTX. But it may have been caused by an HTX customer.
Centralized exchanges hold a portion of user assets in hot wallets, which they use to process withdrawals. When pulling out funds, a user can input any address, really, even one belonging to someone else. This means the record may show a transfer from an HTX-led wallet initiated by someone other than an employee. Such a possibility lends credence to HTX’s denial.
So if the culprit wasn’t HTX, was 0xZiye’s claim the result of a dusting attack?
A dusting attack is defined by Coinbase as:
“When an attacker sends “dust” funds (a tiny amount of crypto) to multiple wallets via an airdrop. If the recipient tries to cash out or move these funds, the attacker will use the activity to try to discover the wallet owner’s identity, which can then be used for phishing scams or other types of attacks.”
Note that Coinbase’s account-dust guidance states that the exchange considers amounts below $0.02 to be dust. The alleged 7.5 USDT is 375 times that. Also, sending funds to, say, 1,000 wallets, typical when it comes to a dusting attack, would have cost 7,500 before fees. This was not an attempt to send small amounts of crypto to a slew of wallets.
Instead, whoever sent the transaction seems to be a form of “compliance grief”: to attach a high-risk party label to an innocent wallet and force legal entities to investigate. To disrupt everyday users and take up an exchange’s resources.
HTX is currently sanctioned by the United Kingdom and will fall under a transaction ban from the European Union on August 23. Council Regulation (EU) 2026/1848 lists the entity as “HTX (HUOBI GLOBAL SA) with August 23rd as the date the restriction starts.
As Crowdfund Insider reporter Omar Faridi noted on July 30, this is a transaction ban rather than a full asset freeze. From August 23, EU persons and entities must stop direct or indirect dealings with HTX, but the ban will not shut down HTX worldwide, so it may continue in markets where no similar restriction applies. The regulation also allows national authorities to approve limited transactions needed to close accounts or withdraw funds, alongside other more specific scenarios.
Of course, this does not prove that Coinbase has a real reason to close 0xZiye’s account. The trader’s post does not say where they live or which Coinbase entity served them, so it is unclear which sanctions rules will apply. Receiving an unwanted payment from HTX is also different from doing business with the exchange. Coinbase’s reaction would depend on this information.

Also, looking at Coinbase’s account-restriction guidance, the exchange only freezes funds in extremely rare cases, instead allowing closed accounts to send their remaining crypto to an external wallet. And even so, Coinbase’s Office of Foreign Assets Control (OFAC) policies state that “Coinbase automatically stops funds, sent from a sanctioned address, from being deposited into your account.” All this to say that 0xZiye should not lose access to their funds in any case, assuming this guidance is followed.
Exchanges use automated systems to check where deposits come from. A transfer from a wallet connected to a sanctioned or high-risk exchange can trigger an alert for the compliance team. A Chainalysis guide published November 21, 2024 explains that exchanges can set these alerts based on the counterparty, amount, risk level, and user behavior.

An alert gives a reason for an exchange to investigate, though it does not inherently imply blame on the recipient. In this case, Coinbase would need to determine whether or not 0xZiye requested the payment. If the trader withdrew funds from HTX, the situation would make a lot more sense. If someone else entered 0xZiye’s Coinbase deposit address and sent the 7.5 USDT without permission, the trader had no control over the transaction.
So, can seven dollars in crypto freeze a Coinbase account? This case, or rather an unproven allegation, does not provide an answer just yet. Sun and HTX’s denial alongside a lack of provable data do not make a solid claim.
Though the validity of such a case does not eliminate potential risk. Permissionless networks allow strangers to create transactions that recipients did not request. Compliance systems need to distinguish between funds a customer deposited and funds a potential bad actor sent. Until exchanges create a system where this is possible, unsolicited deposits will remain a cheap way to cause trouble for innocent traders.
Create a free account to continue reading AlphaClub articles and access exclusive features.
Share