Flow network token minting vulnerability sparks controversy: a leading exchange has frozen the hacker's funds, and the project team is stuck in a communication deadlock

【Blockchain Rhythm】The Flow network security vulnerability incident that erupted on December 27 has caused quite a stir across the entire ecosystem. Hackers exploited a system flaw to mint a large amount of FLOW tokens. After learning of the news, a major exchange intervened immediately, and the team successfully tracked and froze the remaining funds of the hackers on the platform. While this move helped contain the spread of losses, subsequent handling has appeared somewhat complicated.

According to the official statement, this incident exposed several real-world issues:

Project team’s silence is concerning. A major exchange repeatedly reached out with offers of support and cooperation, but the Flow project team has not provided any substantive response. This raises questions about whether the project team is assessing the situation or has fallen into some kind of dilemma.

The logic behind CEX compensation needs clarification. If Flow decides to implement on-chain recovery solutions, addresses of major centralized exchanges—including the aforementioned major exchange—must be excluded. This is because affected users from different CEXs have already received corresponding compensation. In other words, users should not receive double compensation.

Transparency and accountability cannot be absent. The industry widely expects the Flow project team to release a detailed post-incident analysis report, clearly explaining the root cause of the security vulnerability and outlining future protective measures. The major exchange also expressed willingness to provide professional support in security to help strengthen ecosystem defenses.

This incident serves as both a risk warning for the entire Web3 ecosystem and a test of project governance and communication capabilities.