Bitget hacker transfer failed! After stolen funds were rejected, they were returned
The Bitget hacker has made another move, but this time it didn’t go through.
According to SlowMist’s MistTrack tracking, the hacker attempted to transfer some stolen assets related to the Bitget attack via the cross-chain liquidity protocol Chainflip.
Result:
Deposit rejected → Cross-chain failed → Funds returned to the original address.
Chainflip didn’t directly “freeze” the money; instead, the deposit was refused at the broker interface, so the funds ultimately went back to the sender.
This actually highlights a very real issue:
🔹 Hackers can continuously switch chains, wallets, and cross-chain protocols
🔹 But exchanges, cross-chain protocols, and stablecoin issuers can also intercept suspicious funds through risk-control systems
🔹 So even though on-chain assets can flow freely, it doesn’t mean stolen assets will necessarily be successfully laundered out
At present, Bitget’s official confirmation says the incident involves assets of about $387.5 million. The funds controlled by the attacker are still being actively tracked, and some assets have already been frozen through industry cooperation. Bitget has also launched a reward program for fund recovery, offering a 5% reward for qualifying freezing or recovery actions.
Even more noteworthy is that the hacker previously moved about $83 million worth of stolen XRP, and XRP itself cannot be directly frozen by Ripple.
So what’s really worth关注 this time isn’t just “how much the hacker stole.”
Instead, it’s this:
On-chain tracking + cross-chain risk control + exchange freezing + stablecoin blacklist are forming a new system for tracking and recovering crypto assets.
The hacker is racing against time, and the industry’s risk-control systems are racing against the hacker.
#Bitget #xrp #bitget黑客盗资转移被拒退回
The Bitget hacker has made another move, but this time it didn’t go through.
According to SlowMist’s MistTrack tracking, the hacker attempted to transfer some stolen assets related to the Bitget attack via the cross-chain liquidity protocol Chainflip.
Result:
Deposit rejected → Cross-chain failed → Funds returned to the original address.
Chainflip didn’t directly “freeze” the money; instead, the deposit was refused at the broker interface, so the funds ultimately went back to the sender.
This actually highlights a very real issue:
🔹 Hackers can continuously switch chains, wallets, and cross-chain protocols
🔹 But exchanges, cross-chain protocols, and stablecoin issuers can also intercept suspicious funds through risk-control systems
🔹 So even though on-chain assets can flow freely, it doesn’t mean stolen assets will necessarily be successfully laundered out
At present, Bitget’s official confirmation says the incident involves assets of about $387.5 million. The funds controlled by the attacker are still being actively tracked, and some assets have already been frozen through industry cooperation. Bitget has also launched a reward program for fund recovery, offering a 5% reward for qualifying freezing or recovery actions.
Even more noteworthy is that the hacker previously moved about $83 million worth of stolen XRP, and XRP itself cannot be directly frozen by Ripple.
So what’s really worth关注 this time isn’t just “how much the hacker stole.”
Instead, it’s this:
On-chain tracking + cross-chain risk control + exchange freezing + stablecoin blacklist are forming a new system for tracking and recovering crypto assets.
The hacker is racing against time, and the industry’s risk-control systems are racing against the hacker.
#Bitget #xrp #bitget黑客盗资转移被拒退回