Thorswap partner frozen 10 BTC?

[Mark00101]

Hii

One user sent exactly 10 BTC through THORSwap. The route got routed through NEAR Intents (their "solver" provider). Funds hit an MPC deposit address controlled by NEAR → instantly flagged as "compliance review" → frozen for days. The guy went nuclear on X, but ZachXBT dropped the receipts: the "victim" was the admin of Chinese darknet market FreeCity (drugs, weapons, stolen data, DPRK laundering). Still, the freeze happened.

So what actually still works these days when it comes to AML? How should you swap now? Is ThorSwap no longer safe at all, or was it just one random case?

https://x.com/zachxbt/status/2022500720143216758

[OmegaStarScream]

It can't be one random case. They either have a built-in feature to block suspicious transaction (after screening them) or they don't.

Now looking at this[1]. It's possible that the issue might be related to this new NEAR INTENT integration, as opposed to Thorchain (the protocol itself)?

Cause if I remember correctly, when Bybit got hacked, funds did go through Thorchain and I don't believe there were ever blocked. Sure, you can do things on the frontend side (like Chainflip did if I'm not mistaken), but not on the protocol level. I could be wrong though, cause I'm not following the developement upclose.
 
[1] https://www.binance.com/fr-AF/square/post/26933087279161

[NotATether]

I list appropriate methods for KYC-free swaps.

Don't use it for anything illegal, of course. It goes without saying.

[b1ack]

Let me clarify the protocols involved:

THORChain: A protocol that does NOT have screening or AML checks.

NEAR Protocol (NEAR Intents): A different protocol that DOES perform screening and AML checks, and requests KYC when transactions are flagged.

The problem with SwapKit.dev:

Both protocols are promoted through SwapKit.dev. Most developers and swap/API providers don't realize that integrating SwapKit.dev for their exchange services is like tying a noose around their own neck.

Why? Because SwapKit routes through multiple protocols with different policies. You might think you're using a no-KYC service, but your transaction gets routed through NEAR Intents, which has AML screening.

What the user can do: • Request a refund (if the service cooperates) • Say goodbye to his funds forever (if they don't)

Bottom line: This is why using third-party APIs and aggregators is dangerous. You don't control the routing, and you don't know which protocol will actually process your swap.

Thorswap is just one of the exchange site based on swapkit.dev.