9792879f-c

ConfirmedSecurity599 words3 min decode

Gonka Bridge Exploit Withdraws $884,000, Mints 22M WGNK

Ethereum records show 884,151 USDT and 648 USDC withdrawn in the Gonka bridge exploit, which also created 22 million WGNK that Blockaid called unbacked.

Gonka Bridge Exploit Drains $884,000 in Stablecoins, Mints 22M WGNK
WitnessGonka Bridge Exploit Drains $884,000 in Stablecoins, Mints 22M WGNKjamesmarkosborne / pixabay

Outputs

  1. Ethereum records list withdrawals of 884,151 USDT and 648 USDC tied to the Gonka bridge exploit.

  2. The stablecoin movements match an approximately $884,000 outflow.

  3. The exploit created 22 million WGNK on Ethereum.

  4. Blockaid described the newly minted WGNK as unbacked.

By Elena Vasquez

Ethereum records list withdrawals of 884,151 Tether (USDT) and 648 USD Coin (USDC) tied to the Gonka bridge exploit, together matching an approximately $884,000 stablecoin outflow. The incident also created 22 million WGNK on Ethereum, which Blockaid described as “unbacked.”

The two figures measure different things, and that distinction is central to assessing the loss. The dollar estimate applies to the stablecoin movements; 22 million counts newly created WGNK. They cannot be combined into a larger loss estimate without a separate valuation.

For scale, the reported stablecoin outflow sits just below $1 million. The 22 million figure is not a dollar valuation and cannot be treated as $22 million.

What happened on Ethereum?

The account describes two on-chain actions:

  • Stablecoins were withdrawn through the Gonka bridge.
  • New WGNK was created on Ethereum.

Minting means creating tokens. Here, the creation accompanied the stablecoin outflow, and Blockaid characterized the resulting token supply as unbacked. The account provides no WGNK market price, reserve figure or redemption rate, so the 22 million tokens cannot responsibly be converted into dollars.

Several identifiers are also absent. The material does not name the exploit mechanism, attacker, transaction hash, Ethereum block or incident date. Without those details, readers cannot independently trace the complete transaction path from the account provided.

The practical distinction is simple: stablecoins left, while a separate token supply appeared.

What does Blockaid’s “unbacked” label establish?

The characterization addresses the tokens’ backing status, but the available account does not attach a dollar amount, reserve schedule or issuer disclosure to the 22 million supply.

It does not present the assessment as a court ruling, regulatory finding or conclusion about who bears legal responsibility. Nor does it establish how the minted tokens were distributed, whether they remain transferable or whether recovery efforts are underway.

The evidentiary bases differ. Ethereum records provide the quantities of USDT and USDC withdrawn; Blockaid provides the assessment of the separate WGNK creation. A skeptic should not convert that label into an assumed token value or treat it as proof of a second quantified loss.

The practical point is that Blockaid identified a backing problem without assigning it a dollar value.

Why do the stablecoin and token figures need to stay separate?

Adding $884,000 to 22 million WGNK would mix an asset outflow with token issuance. The reported loss is approximately $884,000 in stablecoins, while the second figure counts minted tokens without a disclosed dollar valuation.

For counterparties, several operational questions follow. Can the newly created WGNK circulate? Can they be frozen or burned? Can any withdrawn stablecoins be recovered? The account answers none of those questions.

It also does not identify affected addresses, state whether bridge reserves were depleted, or provide evidence of reimbursement. Those omissions prevent a firm conclusion about who bears losses or whether the new token supply reached secondary markets.

The practical point is that only the stablecoin outflow has a defensible dollar figure.

What remains unresolved?

The available account names the bridge, chain, assets, token and Blockaid, but not the attack vector, responsible party or formal response. No remediation timetable appears in the material.

That leaves no disclosed deadline against which any restriction on the newly created token supply can be measured. The account also provides no evidence that withdrawn stablecoins have been frozen or returned, although that omission does not establish that recovery is impossible.

With no remediation deadline disclosed, the market-structure change to watch is an on-chain freeze or burn covering the unbacked WGNK; until then, only the stablecoin outflow has a reported dollar value.

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