2025-12-28 04:24:47

The Flow network execution layer was recently attacked, resulting in approximately $3.9 million worth of assets being transferred out through multiple cross-chain bridges. Fortunately, user funds remain unaffected.

The attacker exploited system vulnerabilities to transfer funds. The Flow Foundation has promptly submitted asset freeze requests to relevant trading platforms and institutions, and has decided to suspend network operations for emergency repairs. According to official reports, it is expected to take 4 to 6 hours to complete technical repairs and restore normal network operation.

This incident once again highlights the importance for ecosystem participants to pay attention to network security and smart contract risk management.

FLOW-9,78%

View Original

This page may contain third-party content, which is provided for information purposes only (not representations/warranties) and should not be considered as an endorsement of its views by Gate, nor as financial or professional advice. See Disclaimer for details.

7 Likes

Reward
7
7
Repost
Share

Comment

0/400

ShibaSunglasses

· 14h ago

$3.9 million just lost like that, luckily it's not users' money, or it would have exploded --- Flow has another issue? These bridges really need to be thoroughly reviewed --- 4 to 6 hours for a fix, this speed is acceptable, unlike some projects that take several days --- Always say they've learned their lesson, but next time it's the same vulnerability, it's a bit tiring --- Freezing assets is a good move, at least the chances of recovery are higher --- Web3 security issues have been discussed for so many years, yet mistakes are still being repeated --- $3.9 million was hacked, how embarrassing... By the way, how did the attacker find this vulnerability?

View OriginalReply0

Layer2Observer

· 18h ago

$3.9M leaked from the execution layer. An interesting discovery is that the funds flowed through multiple bridges, indicating that the attacker has a good understanding of cross-chain routing. The network was paused for 4-6 hours to fix the issue. From an engineering perspective, this decision is quite decisive. However, the real question is—why do these system vulnerabilities only get fixed after being exploited? It needs to be clarified whether this is an inherent design flaw of the execution layer or something introduced by recent updates.

View OriginalReply0

rekt_but_vibing

· 18h ago

$3.9 million just like that? Flow really deserves it—the bridge is probably just a sieve. --- Another smart contract vulnerability. Brothers, do you still dare to put your money on these L1s? --- Pause for 4 to 6 hours to fix... Well, this time the response was pretty quick, better than some projects. --- It’s always like this. The official says no problem and users haven't lost anything. I just wonder if anyone really suffered a huge loss. --- This is what Web3 security management looks like haha. Cross-chain bridges are truly an eternal bug. --- $3.9 million gone in the blink of an eye. Is system vulnerability really that simple? Where are the audits?

View OriginalReply0

MidnightTrader

· 18h ago

$3.9 million is gone just like that. Why is this bridge so fragile? --- Network repair paused, another 4 hours to wait. How many people are trembling during this time? --- Flow has encountered issues again. Cross-chain is really a high-risk area. --- Fortunately, it didn't affect users, or the public opinion would have exploded. --- System vulnerability + cross-chain bridging, this combo skill is indeed incredible. --- $3.9 million outflow. Can the freeze request be recovered? Feels like a gamble. --- Once again reminding me why I should still be cautious about holding coins. --- The Flow team responded fairly quickly, but there are indeed vulnerabilities in their defense.

View OriginalReply0

GamefiHarvester

· 18h ago

$3.9 million is gone, and it's gone. Anyway, it's not my money haha --- Flow's reaction speed this time is pretty good, fixed in 4 hours, much more reliable than some chains --- Why is it another cross-chain bridge? This thing is truly a city of vulnerabilities --- As long as user funds are safe, it's fine. Anyway, the project team had already transferred the assets --- Pausing the network is quite a harsh move, it seems they are really panicking --- Smart contract risk management... sounds good, but it’s just another case of being exploited for yield farming --- $3.9 million outflow? Feels like this number needs to be increased by zeros

View OriginalReply0

BoredRiceBall

· 18h ago

Flow has been exploited again, this time for $3.9 million... Why can't these bridges just prevent this? --- 4 to 6 hours for a fix? Listen to this timeline, it feels like another knee-jerk reaction. --- Tsk, every time they say "user funds are not affected," but it seems like Flow chain keeps having issues. --- Still the same story, cross-chain is always the biggest attack surface. How come people still dare to go full in? --- Pausing the network for repairs, just for fun, another "emergency adjustment." --- Is this TM a smart contract? Feels like it's not as smart as 😅. --- $3.9 million just gone like that. If I were a dev, I'd be socially anxious. --- How many times can this freeze assets trick be used? Eventually, you'll freeze yourself out. --- Another system vulnerability and emergency fix, same old routine. --- Why does Flow chain love to join the chaos?

View OriginalReply0

ProbablyNothing

· 19h ago

$3.9 million is gone just like that, Flow's performance this time is a bit disappointing. --- It's another cross-chain bridge, this thing really is a hacker's ATM. --- Fortunately, it didn't affect users, or else there would be another round of public criticism. --- 4 to 6 hours for repair? How serious is that? It feels like Flow acted pretty quickly this time. --- Every time they say lessons are learned, but the same vulnerabilities appear next time. When will they truly learn and be smart? --- Pausing network operations, will the recovery speed be another issue altogether? --- Smart contract risk management sounds very complicated. It seems that not many projects truly care.

View OriginalReply0