{"id":92710,"date":"2025-12-28T13:56:11","date_gmt":"2025-12-28T10:56:11","guid":{"rendered":"https:\/\/forklog.com\/en\/?p=92710"},"modified":"2025-12-28T14:00:17","modified_gmt":"2025-12-28T11:00:17","slug":"flow-token-plummets-40-following-3-9-million-hack","status":"publish","type":"post","link":"https:\/\/forklog.com\/en\/flow-token-plummets-40-following-3-9-million-hack\/","title":{"rendered":"FLOW Token Plummets 40% Following $3.9 Million Hack"},"content":{"rendered":"

On December 27, the value of the L1 blockchain token Flow<\/a> (FLOW) dropped by 40% \u2014 from $0.17 to $0.1. This decline followed an attack causing $3.9 million in damages.<\/p>\n

\"image\"
Hourly chart of FLOW\/USDT on Binance. Source: TradingView<\/a>.<\/figcaption><\/figure>\n

At the time of writing, the asset had recovered to $0.12.<\/p>\n

The incident was first highlighted<\/a> by a user named Wazz. According to him, the attacker issued 5 million FLOW and sold them, draining liquidity pools. It is likely that the perpetrator compromised private keys.\u00a0<\/p>\n

\"image\"
Transactions of FLOW tokens issued by the hacker. Source: X.<\/figcaption><\/figure>\n

Later, the Flow team reported the attack. Initially, developers announced<\/a> an investigation into a “potential security incident,” but subsequently confirmed Wazz’s suspicions.\u00a0<\/p>\n

\n

This is the verified update from the Flow Foundation.<\/p>\n

INCIDENT CONFIRMED<\/p>\n

On December 27, 2025, an attacker exploited a vulnerability in Flow’s execution layer and moved approximately $3.9M in assets off-network before validators executed a coordinated halt.<\/p>\n

Critically, this\u2026 https:\/\/t.co\/KEXzo0w8as<\/a><\/p>\n

\u2014 Flow.com (@flow_blockchain) December 27, 2025<\/a><\/p><\/blockquote>\n