Skip to content
Crypto.world

The Ledger

IBC Exploit Created 219 Million Unauthorized THEO, Autheo Says

An IBC asset-validation flaw allowed an attacker to create about 219 million unauthorized THEO on Autheo's mainnet, the company says. The company says about 28 million were sold after tokens moved to Base and Robinhood Chain, while the network remains suspended during recovery work.

IBC Exploit Created 219 Million Unauthorized THEO, Autheo Says

“The vulnerability originated within Autheo Mainnet's IBC asset-validation mechanism.”

Autheo Team, Autheo

Autheo traces the unauthorized issuance to IBC validation

Autheo says an attacker created approximately 219 million unauthorized THEO on its mainnet by exploiting a flaw in how the network validated certain assets arriving through Inter-Blockchain Communication (IBC). The company disclosed the figure in an October 20 community update, eight days after it halted mainnet operations in response to the incident.

According to Autheo, the attacker connected an external blockchain under their control and introduced an asset that the network wrongly treated as eligible for conversion into native THEO. The company identifies the asset-validation mechanism—not the Base or Robinhood Chain bridges—as the source of the unauthorized issuance.

The disclosure adds detail to Autheo’s October 13 update, which confirmed unauthorized minting but said the number of tokens affected and the financial impact were still under investigation. The newer account gives an approximate supply figure and describes subsequent token movements, while noting that reconciliation work continues.

About 28 million THEO were sold after cross-chain transfers

Some of the unauthorized tokens moved through existing cross-chain infrastructure to Base and Robinhood Chain, Autheo says. About 28 million THEO were sold there, the company says. It is also tracking funds transferred to Ethereum that it links to sales of the unauthorized tokens, but its update gives no amount for those proceeds.

The company cautions that the bridges were routes used after the incident, not the source of the original issuance. It also says that a token’s movement or presence on another network does not by itself establish that its holder took part in the attack. Its investigation, Autheo says, distinguishes the exploit from later transfers, market transactions and the actions of legitimate holders.

Mainnet remains suspended as Autheo reviews supply

Mainnet operations and affected cross-chain services were suspended after the incident, and the network remains offline. The company says it has identified the vulnerable code path and is developing and testing corrections, while working with forensic firm ZeroShadow and coordinating with infrastructure providers, exchanges and other counterparties.

Substantial quantities of the affected supply have been identified and restricted, Autheo says, but it is still reconciling exact amounts, current balances and transaction histories. Autheo's objective is to prevent unauthorized issuance from becoming a lasting addition to legitimate THEO supply while considering the rights of good-faith holders. The company has not announced a final recovery method or a restart date.

Restart depends on testing, not a calendar date

The recovery plan sets out four stages: remediation and independent verification; a controlled mainnet restart; gradual restoration of approved cross-chain services; and publication of a technical post-mortem alongside a final supply reconciliation. Services will resume only after their security requirements are met, Autheo says, and affected bridge routes will remain restricted until reopening conditions are satisfied.

That leaves the amount of unauthorized THEO still outstanding—and its eventual treatment—unresolved in the October 20 update. For now, the network remains halted while Autheo tests its corrections and completes the tracing and reconciliation work.

Sources

  1. Original source · Blog post Autheo · Autheo community update october autheo.com

Other pages read

  1. Autheo · Autheo community update october autheo.com

Related stories

Explore

More articles