Gonka suffered an Ethereum bridge security incident on November 18, 2026. The attacker allegedly changed the bridge's epoch BLS group key, affecting its authorization mechanism before extracting part of its stablecoin reserves and minting WGNK tokens without corresponding backing. Initial estimates put the value extracted at approximately $1.05 million. On November 19, the project announced that the funds had been fully returned. While the recovery is positive, the incident highlights continuing risks involving bridge key management, validator authorization and reserve monitoring.
What Happened to Gonka's Cross-Chain Bridge?
According to SlowMist's incident records and related security reporting, Gonka's Ethereum bridge was attacked on November 18. The attacker changed the epoch BLS group key used by the bridge, then withdrew part of its USDT and USDC reserves and minted a large amount of WGNK without sufficient backing. Initial estimates placed the extracted value at approximately $1.05 million.
BLS signatures are commonly used in multi-party verification and signature aggregation. Cross-chain bridges rely on validators or signers to confirm transactions and asset states across networks. Key rotation, signing authorization and validator-set management are therefore critical security components. Following the incident, Gonka said it had identified investigative leads and was coordinating with relevant partners.
Does the Return of Funds Mean the Risk Is Over?
On November 19, Gonka announced that the funds involved in the incident had been fully returned. This is a positive development, but asset recovery and complete remediation are separate matters. The project still needs to explain how the attacker gained the ability to change the key, whether permissions have been reconfigured and whether independent security checks have been completed before the bridge resumes normal operations.
The stablecoin withdrawals and the minting of insufficiently backed tokens may also involve separate weaknesses in asset custody and cross-chain state consistency. Even after funds are returned, the project should assess whether other authorization paths could be abused and verify that all affected contracts and validator components have been reviewed.
How Can Bridges Improve KYT and Security Controls?
Cross-chain bridges should require multi-party approval for validator key rotation, signing threshold changes and administrative operations. Unexpected key updates should trigger immediate alerts. Reserve assets should be continuously reconciled against cross-chain issuance and redemption data, with abnormal discrepancies prompting restrictions on relevant operations.
KYT systems can monitor bridge-related fund flows and identify unusually large withdrawals, rapid transaction splitting, cross-chain conversions and transfers to high-risk addresses. Following an incident, projects should publish a clear timeline, affected components, recovery status and remediation measures. Gonka's experience demonstrates that bridge security cannot rely on cryptographic signatures alone. Key governance, reserve accounting, on-chain monitoring and transparent incident response must work together.