d57aaf02-0

ConfirmedSecurity675 words3 min decode

Gonka Bridge Exploit Moved $1.05 Million and Minted Unbacked WGNK

Blockaid tied about five transactions to Gonka’s Ethereum bridge exploit, involving $1.05 million in stablecoins and unbacked WGNK. Consensus stayed intact, but compensation awaits a community decision.

Gonka Says Network Services Run Normally; Community to Decide WGNK Compensation
WitnessGonka Says Network Services Run Normally; Community to Decide WGNK Compensationgeralt / pixabay

Outputs

  1. Blockaid tied roughly five transactions to the Gonka Ethereum bridge exploit.

  2. The transactions moved about $1.05 million in stablecoins and minted unbacked WGNK.

  3. Gonka reported no consensus interruption and said network and inference services continued operating normally.

  4. Users were told not to interact with or trade WGNK, use the bridge, or leave tokens in liquidity pools on Uniswap and other decentralized exchanges.

  5. The community will decide whether WGNK holders receive compensation; no payment terms or deadline were stated.

What did the exploit affect?

Blockaid monitoring tied roughly five transactions to an exploit of Gonka’s Ethereum bridge. The transactions moved about $1.05 million in stablecoins and minted unbacked WGNK. Gonka said: “the incident did not affect network consensus” and that its “network and inference services continued operating normally.”

The statements separate the compromised route from the rest of the protocol. Gonka did not report a consensus interruption or a halt to network and inference operations, but its update gave no transaction hashes, affected contracts, exploited code or receiving addresses. Those omissions limit independent review of the attack’s full reach.

Takeaway: The disclosed failure sat at the bridge and asset layer, not in a reported consensus halt.

Why did Gonka keep the network running?

The operating claim is narrow: Gonka said the network and inference services continued normally. That supports continuity of core operations, but the project supplied no uptime data, incident timeline or downstream assessment. It does not establish that every application or integration escaped harm.

Until further notice, Gonka nevertheless restricted the pathways most directly tied to the disclosed risk: bridge use and WGNK activity. Those warnings applied to assets and routing rather than a network shutdown.

Takeaway: Core operations continued, but asset-level exposure did not.

What is the user exposure?

Gonka’s instructions to users were explicit:

  • Do not interact with WGNK.
  • Do not trade WGNK.
  • Do not use the bridge.
  • Withdraw tokens from liquidity pools on Uniswap and other decentralized exchanges.

The pool instruction targeted user exposure rather than an exchange compromise. Gonka did not say that Uniswap or another decentralized exchange had been hacked, disabled or required to freeze WGNK. It also disclosed no pool balances, withdrawal volumes or venue-by-venue trading status.

That distinction matters. The network and inference layers reportedly continued functioning, while the unbacked token and exploited bridge created direct risk for users of those specific routes. The request to withdraw pooled tokens was a risk-control measure, not evidence that liquidity had already been removed.

Takeaway: WGNK trading and pooled liquidity remained exposed even as core operations continued.

What does $1.05 million establish?

Blockaid’s estimate places the disclosed transaction activity at about $1.05 million in stablecoins. Dividing that amount by roughly five transactions yields a simple average near $210,000 each, although the approximate count does not show how the movement was distributed.

The figure does not measure the full economic cost. The attack also minted unbacked WGNK, but the update gave neither the quantity minted nor a price at issuance. Without those inputs, the minting cannot be translated into a defensible dollar loss or dilution estimate.

The update also reported no seized funds, repayment, insurance coverage or reimbursement process. The $1.05 million therefore describes stablecoin movement tied to the exploit, not a settled net loss.

Takeaway: The headline amount measures stablecoin movement, not the full cost of the unbacked minting.

How will compensation work?

Gonka said the community will decide whether WGNK holders receive compensation. That establishes an open policy question, not a promise of payment: the project specified no eligibility test, amount, valuation method, timetable or allocation mechanism.

The missing details determine who among WGNK holders could claim and how any claim would be measured. The disclosure named no vote date or rulebook, and it did not identify the body responsible for implementing a decision. The update therefore offers no basis for estimating payment timing or recovery probability.

Takeaway: Compensation awaits a community decision, but no payment terms or deadline were stated.

What happens next?

The operative deadline remains unspecified. Gonka’s “until further notice” language leaves the WGNK restrictions and bridge-use warning open-ended unless the project issues a replacement.

The next material disclosures are the community’s compensation terms and any change to bridge or token access. Until Gonka provides those details, the disclosed $1.05 million and unbacked minting remain the stated scale of the incident. For users, that open-ended restriction—not a consensus shutdown—remains the operative safety window.

via tokenpost.com (Source)

More from Elena Vasquez

Elena Vasquez

Show full bio

Staff writer covering regulation, policy and their impact on crypto and web3 industry at Mempool Brief.

1,576 articles