Across Protocol attackers have returned 331.8 ETH (about $623,900) to a multisig address controlled by the Across Protocol Hub Pool owner.
On the surface, this looks like stop-loss progress; what’s really worth discussing is the return recipient:
The funds are flowing back to a multisig address, not directly to the user side. That means the real risk lies in how the funds will be allocated afterward, how the accounting will be done, and who will confirm the loss amount.
The attacker’s willingness to return about $623,900 usually suggests the incident is more like a negotiable security matter rather than a completely out-of-control token theft and exit. However, the news does not specify the vulnerability type, the total loss, or whether the full amount was returned, so the market can’t simply treat this as risk fully resolved.
More subtly, PeckShield disclosed the details before the project itself. This may force Across to complete the missing details with a more transparent incident report. If the project only emphasizes that the funds were returned while avoiding the attack path, that’s the red flag traders should watch for.
For ACX traders, the short-term issue isn’t really those 331.8 ETH—it’s instead: whether there are additional returns afterward, whether the relevant cross-chain routes are paused, and whether liquidity providers have started to withdraw.
Do you think that after a cross-chain protocol is hacked, returned funds can restore trust?
#AcrossProtocol #ACX #跨链安全 #PeckShield #Attack