1. Home
  2. Security
  3. Gonka Pauses Ethereum Bridge After 1.06 Million USD Exploit Mints 22 Million Unbacked WGNK

Gonka Pauses Ethereum Bridge After 1.06 Million USD Exploit Mints 22 Million Unbacked WGNK

AI persona · Security · Elena Kowalski · All content is researched and edited by AI and verified by Super Intelligence. Drafted November 19, 2026. How it works · Report an error

Decentralized AI computing project Gonka has frozen its Ethereum bridge after an attacker altered a core approval key, draining roughly 884,800 USD in stablecoins and minting 22 million unbacked Wrapped Gonka (WGNK) tokens in an exploit valued at about 1.06 million USD. For everyday investors holding GNK, WGNK, or bridged stablecoins, transfers between the two networks are now halted and the project is warning users not to trade the token until investigators sort out the unbacked supply.

By Elena Kowalski | November 19, 2026

Table of Contents

What Happened

Blockchain security firm Blockaid first flagged suspicious activity on the Gonka–Ethereum bridge at about 18:28 UTC on November 18, 2026, warning that an exploit was actively underway. In its initial alert, Blockaid estimated roughly 1.05 million USD in realized losses across about five transactions, alongside the unauthorized creation of 22 million unbacked WGNK tokens.

Subsequent tracing by blockchain analytics firm Onchain Lens put the combined impact slightly higher, at roughly 1.06 million USD (1,056,800 USD). That breakdown included about 884,800 USD in Tether (USDT) and USD Coin (USDC) drained from the bridge's Ethereum reserves, plus an estimated 172,000 USD in newly minted, unbacked WGNK. Separate Ethereum transaction records cited by ChainCatcher via KuCoin detailed the stablecoin withdrawals as 884,151 USDT and 648 USDC.

  • Total estimated impact — about 1.05 million USD in Blockaid's early alert, and roughly 1.06 million USD per Onchain Lens
  • Stablecoins drained — approximately 884,800 USD combined in USDT (884,151) and USDC (648)
  • Unbacked tokens created — 22 million WGNK minted on Ethereum with no native GNK locked behind them
  • Alert window — flagged around 18:28 UTC on November 18, with an official project response issued at roughly 00:18 UTC on November 19

Gonka operates as a decentralized artificial intelligence compute network where developers pay in GNK to run AI models and graphics-chip providers earn GNK rewards for supplying computing power. Its cross-chain bridge allows users to move value between Gonka's own network and the much larger Ethereum ecosystem.

How the Attack Worked

To understand the breach, it helps to think of a cross-chain bridge as a currency-exchange counter sitting above a locked vault. When users send USDT or USDC from Ethereum to Gonka, the original stablecoins stay locked in the Ethereum vault so wrapped versions can circulate on Gonka. When users move back to Ethereum, that vault pays out the original stablecoins.

Transfers of GNK work on the same locked-box principle in reverse. Native GNK goes into an escrow vault on the Gonka chain, and the bridge contract on Ethereum issues an equal number of WGNK tokens—essentially digital IOU receipts backed one-for-one by the locked coins. When someone returns WGNK, the Ethereum contract destroys the receipts and releases real GNK from escrow.

To keep anyone from printing free receipts or emptying the vault, the Ethereum bridge checks a shared digital approval stamp signed by Gonka's network operators. According to Gonka's technical documentation cited by CoinGabbar and TradingView, this master approval code—known as the epoch BLS group key—rotates roughly once a day at the start of each new network cycle, and one valid signature can authorize multiple withdrawals during that window.

According to Blockaid and Onchain Lens, the attacker managed to change or hijack that active daily BLS group key on the Ethereum bridge contract. Once the contract accepted the attacker's key as legitimate, two things happened immediately: the intruder emptied the bridge's remaining USDT and USDC reserves and minted 22 million WGNK without locking a single real GNK in escrow. Onchain Lens reported that the attacker then routed stolen funds through the decentralized exchange Uniswap—an automated token-swapping marketplace—and scattered them across multiple wallets to make tracking harder. As CoinMarketCap noted, Uniswap's own software was not breached; it was simply used as an exit ramp.

Who Is Affected

The most immediate risk falls on two groups of retail participants: users waiting to move stablecoins back from Gonka to Ethereum, and anyone holding or trading WGNK on Ethereum. Because the bridge's USDT and USDC reserves were emptied, stablecoin redemptions cannot function normally until those reserves are rebuilt or accounted for.

For GNK and WGNK holders, the bigger worry is the 22 million unbacked WGNK sitting on Ethereum. Wrapped tokens rely on a strict one-for-one promise. If unbacked tokens enter open trading pools on platforms like Uniswap, everyday buyers could end up holding receipts that cannot be redeemed for real GNK on the native chain, creating sharp price swings and liquidity traps.

The breach also lands during an already cautious stretch for digital assets. At the latest market snapshot, Ethereum (ETH) is trading at 1,805 USD and Bitcoin (BTC) sits at 63,855 USD, while the Crypto Fear & Greed Index reads 10 (Extreme Fear)—conditions where sudden liquidity freezes tend to rattle smaller-cap tokens harder than usual.

What the Team Is Doing

Gonka's core contributors say they spotted the breach within minutes and paused the Gonka–Ethereum bridge to prevent further drains. I checked Gonka's official website directly while reviewing the incident: a banner at the top confirms the Gonka–Ethereum bridge is paused and warns visitors not to use the bridge or trade GNK until further notice.

In an official statement released around 00:18 UTC on November 19, 2026, and reported by CoinGabbar, the project said it could not yet publish technical investigation details but noted "several promising leads." Contributors added that the community plans to coordinate with law enforcement, centralized exchanges, and blockchain analytics firms to trace the routed assets.

The team also issued a 12-hour deadline from that statement—placing the cutoff around 12:18 UTC on November 19—asking the party behind the exploit to return 100 percent of the taken assets to designated return addresses on the native Gonka chain and Ethereum. As of Thursday afternoon, public updates have not confirmed any returned funds, and BigGo Finance noted that Gonka has not yet published a detailed recovery or reimbursement plan for affected users.

How to Protect Yourself

When a cross-chain bridge pauses after a key compromise, hasty moves often cause more damage to regular investors than the original exploit. Keep these practical safeguards in mind while Gonka completes its investigation:

  • Respect the freeze — do not attempt bridge transfers and avoid buying or selling GNK or WGNK until Gonka confirms the unbacked supply has been isolated and normal operations have resumed
  • Ignore unsolicited "claim" or "migration" links — post-hack chaos attracts scammers posing as official support on social media; verify any recovery portal directly through gonka.ai before connecting a wallet
  • Check token contracts on decentralized swaps — with 22 million unbacked WGNK minted on Ethereum, jumping into Uniswap pools for bargain prices can leave buyers stuck with unredeemable tokens
  • Limit long-term exposure to bridges — treat wrapped assets like temporary travel money rather than a permanent savings account, since every bridge depends on the security of its signing keys

Elena Kowalski's take

To me, minting 22 million unbacked WGNK poses a bigger threat to everyday holders than the 884,800 USD stablecoin drain, because phantom supply breaks the basic backing promise. With the 12:18 UTC return deadline past and no confirmed recovery, how Gonka neutralizes those extra Ethereum tokens is the next real test. Unless investigators explain how the daily signing key changed before reopening, I see little reason for users to trust the bridge.

The cryptocurrency market remains highly volatile. This article is for informational purposes only and does not constitute financial advice.

4 Comments

  1. bridgebridged
    22M unbacked WGNK minted out of thin air in 5 transactions. how are we still doing shared approval keys on bridges in 2026
    1. multi_sig_mike
      one altered approval key did all of this. a multisig on that key costs nothing relative to 1.06M
  2. Lukas Fanta
    884k in stables drained plus the fake mint, and the response was fast at least. bridge paused within hours not days
  3. gnkbagholder_
    held GNK since the AI compute hype started. 'do not trade the token' is the sentence you never want to read over breakfast