Exchange freezes · Field note

Hyperliquid Is Quietly Freezing Accounts and Demanding KYC. Here’s What Actually Happened.

Hyperliquid Is Quietly Freezing Accounts and Demanding KYC. Here’s What Actually Happened.

Hyperliquid, the decentralized perpetuals exchange that built its brand on “no KYC, no email, just connect a wallet,” is now blocking users from its own frontend. Wallets are being flagged as “high risk” by third-party screening tools, and traders are locked out of the official interface with no clear appeals process. If you’re affected, the good news is that your funds aren’t necessarily trapped. But.

What’s Happening on the Hyperliquid Frontend

Since early 2026, Hyperliquid has been deploying third-party wallet screening on its official frontend at app.hyperliquid.xyz. When a flagged wallet tries to connect, the interface displays a red warning banner:

> “Your address has been flagged as high risk by a third-party screening tool. This frontend interface doesn’t support connection to the Hyperliquid blockchain by high-risk addresses.”

The block is enforced at the frontend layer only. It isn’t a protocol-level freeze. The Hyperliquid L1 smart contracts don’t check identity, jurisdiction, or risk status. The screening is applied by code running on the frontend and its associated API endpoint at api-ui.hyperliquid.xyz.

The initial wave of blocks targeted wallets linked to HTX (formerly Huobi) after the UK sanctioned Huobi Global SA on May 26, 2026. But the net has widened. Users with no direct HTX exposure have also been flagged, and the blocking logic appears to trace wallets through multiple intermediate transfers. A wallet that sent funds to a wallet that sent funds to a wallet that once interacted with HTX can end up blocked.

Chainalysis Integration on the Frontend

Multiple sources confirm that Hyperliquid’s frontend screening is powered by blockchain analytics providers. Chainalysis is one of them, alongside Blockaid and TRM Labs. These firms provide risk labels (such as “interacted with sanctioned entity”) that Hyperliquid’s frontend code uses to decide whether to allow a wallet to connect.

The critical detail: Chainalysis and similar providers don’t issue mandatory block lists. They provide factual tags. The decision to block is Hyperliquid’s own. This was confirmed by a compliance researcher known as “as required,” who spoke with several analytics firms and reported that none of them mandate blocking. Other platforms, including OpenSea and Lighter, handled the same risk data differently and didn’t block the same wallets.

The Chainalysis integration lives in the frontend code served from api-ui.hyperliquid.xyz. This means it only affects users who access Hyperliquid through the official web interface. It doesn’t affect direct interaction with the Hyperliquid L1 smart contracts.

The KYC Allowlist

Hyperliquid is also testing a KYC allowlist mechanism. This feature allows deployers to create HIP-3 commodity futures allowlists supporting up to 10,000 addresses. Addresses not on the list can still fund their accounts but can’t execute trades on those specific markets. This move is widely interpreted as preparation for a dedicated US-facing frontend, following discussions between Hyperliquid Labs and US regulators including the SEC and CFTC.

This represents a significant shift for a platform that marketed itself on having zero KYC requirements. No email, no government ID, no selfie verification. Now the infrastructure for identity-gated trading is being built.

How to Withdraw If Your Frontend Is Blocked

This is the part that matters if your wallet has been flagged.

The frontend block doesn’t freeze your funds at the contract level. Your USDC balance on Hyperliquid is still yours at the smart contract layer. Unless Circle (the issuer of USDC) has separately frozen your USDC at the token contract level on the chain where it’s held, and unless Hyperliquid has updated the withdrawal smart contract to block your address specifically, you can still withdraw.

The withdrawal is done by interacting directly with the Hyperliquid L1 smart contracts, bypassing the frontend entirely. here’s how:

1. Use the Hyperliquid API directly. The official API documentation at app.hyperliquid.xyz/API describes how to interact with the protocol programmatically. 2. Use the open-source SDK `@nktkas/hyperliquid` (available on npm). The key method is `withdraw3`, which submits a signed withdrawal request to the Hyperliquid L1. 3. The SDK first checks your clearinghouse state to confirm your withdrawable balance, then submits the signed transaction.

The process requires your private key (the wallet that owns the Hyperliquid account) and a destination EVM address. The SDK signs the request locally and submits it to the Hyperliquid API endpoint. If the protocol itself hasn’t frozen your address, the withdrawal will process.

Using Alternative Frontends

If you prefer a graphical interface over writing code, you can try third-party frontends that connect to the Hyperliquid L1 without the Chainalysis screening layer.

One option reported by the community is app.hyperunit.xyz. This is a third-party interface for the Hyperliquid protocol that doesn’t set up the same wallet screening as the official frontend. If your address is blocked on app.hyperliquid.xyz, you may be able to connect and trade through alternative interfaces. The HyperUnit bridge has had its own issues, including a reported case of $77,000 in ETH locked on their bridge for over two months with revert functions failing. Treat any third-party frontend with appropriate caution and verify you’re interacting with the correct smart contract addresses.

What This Means

Hyperliquid built its user base on the promise of permissionless, no-KYC trading. The reality in 2026 is that the official frontend now screens wallets, blocks flagged addresses, and is building KYC infrastructure. The protocol layer remains permissionless, but the primary access point most users rely on doesn’t.

If your wallet is blocked:

– Your funds are likely still accessible via direct API or SDK interaction
– The block is a frontend decision, not a chain-level freeze
– Circle USDC freezes are separate and independent (check your address on Etherscan/Arbiscan for the USDC blacklist)
– Alternative frontends like app.hyperunit.xyz may work as a fallback

For assistance with frozen or blocked crypto funds, USDT Freeze provides recovery advisory services. We don’t guarantee recovery and this article isn’t legal or financial advice. Every case depends on the specific freeze mechanism involved.

Sources

– Original report: Kekius Foundation on X
– Hyperliquid frontend blocking documentation: Leo Onchain, Medium
– HTX sanctions and wallet blocking analysis: Coinpaper
– KYC allowlist testing: AInvest

Next step

Think a freeze is affecting your position?

Send the tx hashes, exchange references, and rough timeline. We open a jurisdictional pool review under NDA and come back with a candid position.

[email protected] · Telegram @unfreezeusdt · NDA on request