HTX Hot Wallet Batch Small Transfers Spark Address Pollution Controversy
On-chain browser screenshots show that an address labeled "HTX 48" transferred small amounts ranging from 3 to 10 USDT to multiple external addresses in a short period, including a transfer of 7.5 USDT; the screenshots cannot independently prove that the address is actually controlled by HTX.
Netizens claim that their Coinbase address received a suspected 7.5 USDT from this address and were asked by Coinbase to explain the source of the funds, or face account closure risks; this claim currently comes only from personal social media statements, and Coinbase and HTX have not publicly confirmed it.
Another netizen showed multiple records of 0.00 USDT credited to their platform account on August 17, claiming that the platform stated it would assist in intercepting the funds; the screenshot did not display the sender's address, on-chain transaction hash, or the original response from platform customer service.
Zero or very small token transfers are often referred to as "address pollution" or "address poisoning": attackers exploit user transaction records to create records that resemble commonly used receiving addresses or can be mistakenly copied, misleading victims into sending assets to incorrect addresses in subsequent transfers.
However, the existing screenshots show multiple real USDT transfers of different amounts, rather than typical zero transfers or counterfeit token incidents; whether this constitutes address poisoning, the purpose of the transactions, and whether they were initiated by HTX or entities related to Sun Yuchen cannot be verified solely based on the screenshots.
From a market mechanism perspective, small transfers do not change the private key control of the receiving address and cannot directly steal wallet assets; risks occur when users rely on transaction history to copy addresses and neglect complete verification. If centralized exchanges trigger anti-money laundering reviews due to unfamiliar deposits, affected users may also face account explanations, proof of fund sources, or temporary risk control restrictions. The real pressure is on ordinary users who rely on address books and transaction history, as well as compliance teams that need to handle abnormal deposits.
Source: Public Information
ABAB AI Insight
Address pollution does not exploit vulnerabilities in blockchain protocols but rather takes advantage of user operational habits. Public chain addresses typically exceed 40 characters in length, making it difficult for users to verify manually; thus, they often rely on the first and last few characters displayed in the wallet interface, historical records, or auto-fill results to confirm the recipient. As long as attackers make their addresses frequently appear in the victim's transaction history, they may increase the probability of being mistakenly selected; however, this requires that the attacker's address is sufficiently similar to the target's commonly used address, which the screenshots do not demonstrate.
The key issue in this controversy is not whether the "HTX address transferred funds out," but whether the three layers of evidence can close: first, whether the on-chain label can be reliably attributed to HTX by the block explorer; second, whether the transfer is for platform business, user withdrawals, address aggregation, or abnormal operations; third, whether Coinbase issued a genuine risk control notification due to the 7.5 USDT deposit. Any missing layer prevents small transfers from being directly classified as address poisoning or targeted fund pollution led by the platform.
If the related small funds indeed come from sanctioned, high-risk, or exchange-marked addresses, the centralized exchange's risk control logic would prioritize "on-chain traceability" over the amount. Blockchain transfers are permissionless: anyone can transfer assets to a target address, but the recipient may not be able to prevent the deposit. If compliance systems trigger account reviews solely based on the flow of funds, malicious third parties can use low-cost transfers to spill risk labels onto unrelated addresses; mature risk control should combine amount, behavioral patterns, evidence of control, and subsequent fund flows, rather than equating passive receipts with active transactions.
Essentially, this reflects a regulatory change: on-chain transparency makes fund paths more traceable, but also exposes addresses that "passively receive risky funds" to label transmission. The mechanism is that addresses are not natural person identities, and on-chain transactions do not automatically equate to ownership or intent; when exchanges directly map automated on-chain risk scores to account restrictions, attackers can exploit very low costs to create compliance noise. Future competitive points will not only involve intercepting suspicious assets but also who can distinguish between active money laundering, platform hot wallet operations, and passive address pollution.
ABAB News · Cognitive Laws
On-chain address transparency does not equal fund intent transparency
If risk control only looks at paths, attackers can create noise
Small transfers do not steal assets but can hijack compliance costs