Autheo’s THEO plunges 92% after suspected bridge exploit on Base

Autheo’s THEO plunges 92% after suspected bridge exploit on Base

An unauthorized mint of 19 million tokens was dumped into thin liquidity, and Autheo is telling holders to stop buying, selling and bridging THEO.

Autheo’s THEO token lost 92% of its value in 24 hours after 19 million tokens appeared out of nowhere on Base. The unauthorized mint on October 13, 2026, is being treated as a suspected bridge exploit.

The attacker reportedly swapped the freshly minted tokens for approximately 700.8 ETH, valued at around $1.76 million at the time. THEO holders got the bill.

What happened on Base

Someone minted 19 million THEO on Base without authorization, then sold them into the market.

THEO traded at approximately $0.08 before the incident. Within a day it had fallen to around $0.006.

Base-based trading venues such as Hydrex had thin liquidity for THEO, which greatly amplified the sell pressure on the token.

The funds were moved off Base rather than held on the network, a pattern that makes recovery harder because assets leave the chain where the incident occurred.

Advertisement

Autheo responded by urging users not to buy, sell or bridge THEO while it investigates.

The bridge at the center of it

THEO lives on more than one chain. The project uses a Hyperlane-based bridge to move tokens between its own mainnet, Base and Robinhood Chain.

The official bridged THEO contract on Base is 0xebE516a20238F79DC20b07eaD6768e08891Ed309. Traders checking whether their holdings are the real thing should verify against that address.

The exact root cause has not been confirmed. The incident is described as a suspected bridge exploit, and Autheo’s investigation is ongoing.

Autheo has undergone security audits by Halborn, CertiK and Avelar Labs.

A short road from launch to crisis

Autheo launched its mainnet on May 14, 2026, pitching itself as an “Internet Operating System.” The platform ties together validator staking and transaction fees, with plans to expand into compute, storage and AI layers. As of September 2026, it counted 151 active validators.

THEO began trading at $0.05 on August 20, 2026, with an initial market cap of roughly $18.7 million. It picked up a listing on MEXC on October 1, 2026, widening its trading venues.

THEO has a maximum supply of 7 billion tokens, with approximately 5.3% circulating at launch. The token is strictly a utility asset with no governance rights.

What this means for holders and the market

For current THEO holders, the immediate priority is following Autheo’s guidance and avoiding the bridge until the team publishes findings.

If 19 million unauthorized tokens remain in circulation on Base, Autheo will need to explain how it plans to account for them, whether through contract upgrades, migrations or other remediation.

Hyperlane-connected projects will be watching for the root cause. Until Autheo pins down whether the issue lies in its own deployment or somewhere deeper, other teams relying on similar setups have reason to double-check their configurations.

Disclosure: This article was edited by Vivian Nguyen. For more information on how we create and review content, see our Editorial Policy.
Autheo’s THEO plunges 92% after suspected bridge exploit on Base
Autheo’s THEO plunges 92% after suspected bridge exploit on Base

An unauthorized mint of 19 million tokens was dumped into thin liquidity, and Autheo is telling holders to stop buying, selling and bridging THEO.

Autheo’s THEO token lost 92% of its value in 24 hours after 19 million tokens appeared out of nowhere on Base. The unauthorized mint on October 13, 2026, is being treated as a suspected bridge exploit.

The attacker reportedly swapped the freshly minted tokens for approximately 700.8 ETH, valued at around $1.76 million at the time. THEO holders got the bill.

What happened on Base

Someone minted 19 million THEO on Base without authorization, then sold them into the market.

THEO traded at approximately $0.08 before the incident. Within a day it had fallen to around $0.006.

Base-based trading venues such as Hydrex had thin liquidity for THEO, which greatly amplified the sell pressure on the token.

The funds were moved off Base rather than held on the network, a pattern that makes recovery harder because assets leave the chain where the incident occurred.

Advertisement

Autheo responded by urging users not to buy, sell or bridge THEO while it investigates.

The bridge at the center of it

THEO lives on more than one chain. The project uses a Hyperlane-based bridge to move tokens between its own mainnet, Base and Robinhood Chain.

The official bridged THEO contract on Base is 0xebE516a20238F79DC20b07eaD6768e08891Ed309. Traders checking whether their holdings are the real thing should verify against that address.

The exact root cause has not been confirmed. The incident is described as a suspected bridge exploit, and Autheo’s investigation is ongoing.

Autheo has undergone security audits by Halborn, CertiK and Avelar Labs.

A short road from launch to crisis

Autheo launched its mainnet on May 14, 2026, pitching itself as an “Internet Operating System.” The platform ties together validator staking and transaction fees, with plans to expand into compute, storage and AI layers. As of September 2026, it counted 151 active validators.

THEO began trading at $0.05 on August 20, 2026, with an initial market cap of roughly $18.7 million. It picked up a listing on MEXC on October 1, 2026, widening its trading venues.

THEO has a maximum supply of 7 billion tokens, with approximately 5.3% circulating at launch. The token is strictly a utility asset with no governance rights.

What this means for holders and the market

For current THEO holders, the immediate priority is following Autheo’s guidance and avoiding the bridge until the team publishes findings.

If 19 million unauthorized tokens remain in circulation on Base, Autheo will need to explain how it plans to account for them, whether through contract upgrades, migrations or other remediation.

Hyperlane-connected projects will be watching for the root cause. Until Autheo pins down whether the issue lies in its own deployment or somewhere deeper, other teams relying on similar setups have reason to double-check their configurations.

Disclosure: This article was edited by Vivian Nguyen. For more information on how we create and review content, see our Editorial Policy.