# Bitget urges THORChain to block attacker addresses after hack

<https://kriptometa.com/en/bitget-thorchain-attacker-address-dispute>

Author: Abdullah Özkurt
Language: English

Published: 2026-09-27T17:07:05+03:00

Updated: 2026-10-08T22:33:33+03:00

![A magnifying glass highlights an address in a network between Bitget and THORChain nameplates.](https://kriptometa.com/uploads/bitget-ten-thorchain-e-adres-engelleme-cagrisi-agdan-merkeziyetsizlik-yaniti-0554_article.webp)

## Key takeaways

- Gracy Chen asked THORChain on September 26 to refuse service to addresses linked to the attackers.
- THORChain emphasized its decentralized, permissionless design the same day without announcing a specific blocking measure.
- MistTrack reported cross-chain movements of funds; tracking addresses does not establish that assets have been recovered.

Bitget’s request to stop serving attacker addresses has met THORChain’s defense of permissionless access. The network has not announced an address-blocking measure or a fund recovery plan.

Bitget CEO Gracy Chen has called on [THORChain](https://kriptometa.com/en/markets/thorchain) to stop serving addresses linked to the attack on the exchange. In a September 26 statement, THORChain emphasized that it is a decentralized, permissionless network, comparing its design with Bitcoin and Ethereum. The dispute concerns where swap infrastructure should intervene once stolen funds have been identified.

## What Bitget is asking for

In her [September 26 post](https://x.com/GracyBitget/status/2103812967066439817), Chen said the attackers’ [wallet addresses](https://kriptometa.com/en/glossary/wallet-address) were publicly listed and actively tracked. Her request goes beyond labeling the addresses: she wants THORChain to stop providing them with swap services.

> “We are formally asking @THORChain to refuse service to these addresses.”

Gracy Chen, September 26 post on X

The request follows cross-chain movements of funds. In a [September 25 statement](https://x.com/MistTrack_io/status/2103403250183815294), MistTrack said assets it linked to the Bitget attack were being sent into THORChain for swaps and transfers between networks. The tracking firm criticized the continued processing of transactions after the addresses had been identified. Both Chen and THORChain referenced that same MistTrack post.

## The protocol and its interfaces have different roles

THORChain expressed sympathy for those affected and compared its architecture with Bitcoin, Ethereum and BNB Chain. It asked what responsibility those networks should bear when handling known stolen funds. The statement did not announce an address-blocking measure or a plan to return funds.

[THORChain’s September 26 statement on its permissionless design](https://x.com/THORChain/status/2103911825490203083)



The project’s [official FAQ](https://thorchain.org/faq) describes swaps between native assets on different blockchains without requiring wrapped tokens. Node operators run the network, and the protocol does not require users to open an account or complete identity verification. Third-party applications providing access to THORChain can set their own conditions.

**An application restricting access and a network rejecting a transaction are separate actions.** A restriction at one interface does not, by itself, establish that an address has been blocked across the protocol.



The operator of a [centralized exchange](https://kriptometa.com/en/glossary/centralized-exchange-cex) controls customer accounts within a different structure from a swap network run by multiple operators. Bitget is asking the network to stop serving the identified attacker addresses.

## Tracking funds is not the same as recovering them

[Tracking transactions on-chain](https://kriptometa.com/en/track-crypto-transaction) helps establish which addresses sent and received assets. Identifying an address does not provide the key needed to move its funds, nor does it establish that victims have received their money back.

The statements on the [Bitget attack](https://kriptometa.com/en/news/security) provide no record of an address restriction taking effect or of recovered funds.
