ERA Wallet

Gonka AI Bridge Exploit: How a Signing Key Change Enabled Unbacked Tokens

Gonka AI Bridge Exploit: How a Signing Key Change Enabled Unbacked Tokens

On November 18, 2026, a bridge exploit targeting Gonka AI's Ethereum bridge led to withdrawals of approximately $884,800 in stablecoins and the minting of 22 million WGNK tokens described as unbacked. Blockaid reported that an attacker changed the bridge signing key before the unauthorized operations. Users' wallet keys were not implicated.

What Happened in the Gonka AI Bridge Exploit?

Gonka is a decentralized AI computing network whose Ethereum bridge supports wrapped GNK (WGNK) and other assets.

According to The Defiant's examination of Ethereum transactions, an attacker-linked address registered a new epoch signing key on November 18. Withdrawals and token minting followed within minutes. Investigators have not established why the bridge accepted that key.

Gonka Bridge Attack Timeline

  • 18:00:59 UTC, Key Registration. An Ethereum transaction registered a new BLS group key for the bridge's epoch.

  • 18:01 UTC, Stablecoin Withdrawals. The attacker-linked address received 884,150.87 USDT and 647.74 USDC from bridge reserves.

  • 18:02 UTC, WGNK Mint. The Ethereum contract minted 22 million WGNK that Blockaid characterized as unbacked.

  • 18:05 UTC, Token Burn. The same address burned 13 million WGNK. That Ethereum transaction alone does not prove that native GNK was released on Gonka.

Blockaid initially estimated about $1.05 million in realized proceeds across roughly five transactions. This preliminary estimate is not interchangeable with the approximately $884,800 withdrawn in the two identified stablecoin transfers. The final impact remains uncertain.

How Crypto Bridges Work and Who Trusts the Signature

To understand how crypto bridges work, consider that Ethereum needs evidence of events on Gonka before releasing or minting assets.

For GNK moving to Ethereum, native tokens are placed in escrow on Gonka and WGNK is minted on Ethereum. For the reverse journey, WGNK is burned and native GNK can be released from escrow. Stablecoin routes use reserves.

Gonka's official documentation describes a validator-based BLS signature system. Validators collectively authorize outgoing operations, while the Ethereum bridge contract checks those signatures against the currently registered group public key. The contract must trust the correct key.

That group key changes at the start of each epoch, approximately once a day. The new key is supposed to be signed by the previous epoch's key, creating a verifiable sequence. Anyone can submit the public update transaction, but the contract is designed to accept only the next sequential epoch key with an appropriate validation signature.

Public submission does not authorize arbitrary keys. Why the suspicious update was accepted remains unresolved.

Why Gonka Was Different From the Ankr Bridge Exploit

The Ankr bridge exploit involved a different failure. In November 2026, an attacker submitted forged cross-chain receipts referring to events on Optimism. Those receipts carried cryptographically valid signatures from a trusted signer, and Ankr's Ethereum bridge released approximately $304,500.

At Ankr, the signed claims were false even though the signatures were valid. The critical question was whether the claimed source-chain events had actually happened. At Gonka, the observed concern appeared one stage earlier: the public key used to verify authorized bridge operations had changed.

Bridges must verify both the reported event and the authority attesting to it.

The Liquid Network incident offers another illustration of why signature arrangements must be evaluated alongside withdrawal rules. A multisignature structure is not a blanket guarantee that assets cannot leave through an unexpected path.

Why Unbacked WGNK Can Still Appear in a Wallet

Under Gonka's intended mechanism, each WGNK created on Ethereum corresponds to GNK locked in escrow on the source network. Redemption depends on that relationship remaining intact. If tokens are minted without matching deposits, their recorded supply exceeds the assets available to redeem them.

Blockaid described the 22 million newly minted WGNK as unbacked. A token balance may still display normally in a wallet, move between addresses or trade on a market. None of those properties independently establishes that the issuer or bridge can redeem it for the underlying asset.

A market price does not guarantee redemption, and liquidity may disappear. The Arcus accounting exploit showed a related distinction: a balance recorded by software is not necessarily proof of accessible funds.

The 13 million WGNK burn does not itself confirm a GNK release on Gonka.

What to Check Before Using a Crypto Bridge

  • Signing authority. Identify who approves withdrawals and how that authority is established. Check whether operators, validators or administrators can replace the keys that the destination contract trusts.

  • Multisig and timelocks. Determine which actions actually require multiple approvals or a delay. A validator BLS group signature should not automatically be treated as an administrative multisig, and neither mechanism eliminates every contract risk.

  • Reserves and redemption. Look for verifiable escrow or reserve balances and understand how wrapped tokens are redeemed. Stablecoin reserves on Ethereum and GNK backing WGNK are separate accounting questions.

  • Emergency controls. Check whether the bridge has withdrawal limits, a pause function and clear procedures for activating them. Emergency restrictions may reduce losses but can also interrupt legitimate withdrawals.

  • Incident disclosures. Prefer projects that publish contract addresses, technical explanations and specific recovery updates. An absence of further suspicious transactions does not demonstrate that the original weakness has been fixed.

An audit can provide useful evidence about reviewed code, but its scope matters. A contract may verify a signature correctly while relying on flawed assumptions about how trusted signing keys are selected.

How to Limit Exposure to Wrapped Assets

A test transfer can expose network, destination or redemption errors, but cannot guarantee future security. Check both directions before a large transfer.

Consider whether a wrapped asset is needed after the intended cross-chain activity ends. Holding it indefinitely means continuing to rely on bridge reserves, key management and redemption mechanisms. Splitting transfers may limit exposure; different interfaces may share one contract.

Controlling your private keys lets you authorize your own wallet transactions. Once assets are locked in a bridge, their redemption also depends on infrastructure outside your wallet's control.

FAQ: The Gonka AI Bridge Exploit

What Caused the Gonka AI Bridge Exploit?

Blockaid reported that an attacker rotated the bridge's epoch BLS group key before unauthorized transfers and minting. The mechanism that allowed this key update to be accepted has not been conclusively established.

How Much Was Taken From the Gonka Bridge?

Identified transfers withdrew 884,150.87 USDT and 647.74 USDC. Blockaid separately reported a preliminary estimate of approximately $1.05 million in realized proceeds.

What Happened to the 22 Million WGNK?

The Ethereum bridge minted 22 million WGNK described by Blockaid as unbacked. An attacker-linked address subsequently burned 13 million WGNK, but the burn alone does not verify redemption on Gonka.

What Is Bridging in Crypto?

Bridging transfers value between separate blockchains, often by locking an asset on one network and minting a corresponding wrapped representation on another.

How to Bridge Crypto More Carefully?

Verify the official bridge contract, supported network, signing authority and reserves. Test the transfer and redemption process with a small amount, while recognizing that a successful test cannot rule out future infrastructure failures.

The Bottom Line

Gonka's incident highlights a specific bridge security question: how does a contract know that a newly registered signing key is truly authorized? Cryptographic approval cannot secure reserves if the process establishing who may approve withdrawals is compromised.

Before transferring substantial funds, examine the bridge's key-update rules, backing and emergency controls. Minimize unnecessary time in wrapped assets, and treat bridge solvency as a separate concern from the security of your own wallet.

Protect your keys, and examine the infrastructure that holds your assets. Use code ERABLOG20 for 20% off: Explore ERA Wallet

Originally published at https://blog.era-wallet.com

 


Did you enjoy this article?


Era Wallet
Era Wallet

ERA Wallet builds secure, air-gapped hardware and software for self-custody, offline transaction signing, and digital asset protection.


ERA Wallet
ERA Wallet

ERA Wallet builds secure, air-gapped hardware and software for self-custody. We write about hardware wallet security, supply chain verification, blind signing risks, and how to actually verify a device instead of just trusting the manufacturer's word.

Publish0x Publish0x

Reward the author with $0.01 in crypto, and earn yourself as you read!

20% to author / 80% to me.
Rewards are FREE. Publish0x pays them, not you.

Page not displaying correctly?