A growing number of Hyperliquid users are discovering they can no longer access the platform’s web interface — not because they did anything wrong, but because they used a cryptocurrency exch
A growing number of Hyperliquid users are discovering they can no longer access the platform’s web interface — not because they did anything wrong, but because they used a cryptocurrency exchange that the United Kingdom sanctioned in May 2026.
The situation has exposed a fundamental tension at the heart of decentralized finance: a protocol that requires no identity verification and prides itself on permissionless access is blocking users through its frontend based on risk scores assigned by third-party surveillance firms.
The story crystallized publicly through one user’s detailed account on X. On June 2nd, a longtime on-chain participant connected their wallet to Hyperliquid’s official frontend and was immediately met with a red banner:
“Your address has been flagged as high risk by a third-party screening tool. This frontend interface does not support connection to the Hyperliquid blockchain by high risk addresses. If you think this is an error, you can open a support ticket.”
The user checked a second wallet and saw the same message. They had never engaged in any sanctioned activity. The explanation, when it emerged, revealed a problem far broader than one user’s blocked wallet.
The UK Sanctions That Started Everything
On May 26th, 2026, the United Kingdom introduced a new wave of sanctions targeting crypto exchanges and payment networks accused of helping Russia circumvent Western financial restrictions. Among the entities designated was Huobi Global S.A. — the parent entity of HTX, one of the longest-standing cryptocurrency exchanges in the industry.
The UK sanctions went further than simply blacklisting HTX as an organization. British authorities targeted what they described as the financial plumbing behind Russian sanctions evasion — the networks, OTC desks, and cross-border transfer mechanisms that moved money through crypto, rather than just the visible interfaces. Assets associated with these entities are subject to freezing, and UK-regulated businesses are prohibited from processing payments or conducting banking operations with them.
The practical consequence for ordinary crypto users became clear almost immediately: any wallet that had deposited to or withdrawn from HTX after May 26th, 2026 — the date the sanctions took effect — was now classified as having interacted with a sanctioned entity. That classification cascades in multiple directions simultaneously.
The Cascade Effect on Ordinary Users
The affected user on X laid out the implications with uncomfortable clarity. A wallet that interacted with HTX post-sanctions faces four distinct consequences. Depositing those funds into other centralized exchanges risks asset freezing. DeFi protocols using compliance screening tools from Chainalysis, Elliptic, or TRM Labs will deny services to those wallets. Those wallets become ineligible for airdrops from protocols running the same screening infrastructure. And perhaps most troublingly — any wallet that receives funds from a flagged wallet can itself become flagged, extending the contamination to entirely innocent third parties.
The user’s specific situation illustrates why this system produces outcomes that feel deeply unfair to legitimate participants. They had used HTX specifically because the exchange supports generating unique deposit addresses across multiple virtual machines — allowing users to maintain separation between public and private wallets without creating on-chain links between them. This is a standard privacy practice, not evidence of illicit activity. Using the wrong exchange at the wrong time — before learning about sanctions they had no reason to anticipate — resulted in a block from one of DeFi’s most significant trading platforms.
The Decentralization Paradox Hyperliquid Can’t Escape
Hyperliquid presents a genuinely difficult case for anyone thinking seriously about what decentralization means in practice. The underlying DEX protocol remains open — the Hyperliquid blockchain itself does not enforce the sanctions. The blocks are being applied at the frontend layer, through third-party risk scoring tools integrated into the official web interface. Technically sophisticated users can still access the protocol directly. Everyone else — which is to say, almost everyone — is subject to compliance screening every time they connect a wallet to the official site.
This creates a situation that critics have described as the worst of both worlds. Users who choose Hyperliquid for its permissionless, non-custodial properties discover that the main access point to that permissionless system enforces permission-based restrictions. The protocol cannot be censored. The website can be — and is.
The earlier UK sanctions on Garantex and associated Russian payment networks targeted the same infrastructure concept — cutting off the pipes rather than just the visible surfaces. What is now becoming clear is that compliance with those sanctions doesn’t stay contained to the sanctioned entities. It propagates through the compliance tools that DeFi protocols use, reaching wallets that had no knowledge of or connection to the underlying sanctioned activity beyond a single exchange interaction.
Dust Attacks and Indirect Contamination
The situation carries an additional layer of risk that has received less attention than the HTX-specific contamination. Compliance screening tools that flag wallets based on interaction history can be triggered through dust attacks — where a wallet holding sanctioned funds deliberately sends a tiny amount of cryptocurrency to an otherwise clean address. The recipient wallet, having received funds from a flagged source, can itself become flagged through association.
This creates a potential attack surface where malicious actors could deliberately contaminate clean wallets by sending them unsolicited micro-transactions from blacklisted addresses. Users who have never interacted with HTX or any sanctioned entity could find themselves blocked from Hyperliquid and other compliance-screened DeFi protocols through no action of their own.
The Support Ticket That May or May Not Help
Hyperliquid has indicated that users who believe their flagging is in error can open support tickets to dispute the classification. One earlier case — a user flagged at the end of March — was apparently resolved after submitting a Discord ticket. Whether that resolution pathway scales to the potentially large number of users now flagged due to HTX interactions is unclear.
The HTX-flagged user who shared their account on X expressed what many affected users are feeling: they used a legitimate exchange for a legitimate purpose, had no knowledge of upcoming sanctions, and now face consequences across multiple DeFi platforms that treat their wallet as contaminated. The compliance system that is supposed to stop sanctioned actors from accessing DeFi is catching ordinary users in its net — and the mechanisms for resolving those false positives remain opaque, slow, and uncertain.
