Autheo

AUTHEO COMMUNITY UPDATE | OCTOBER 30, 2026

We’re sharing an update on security remediation following the October 12 incident, including progress on the fix, internal verification, and the steps being considered before services can resume.

The incident involved a flaw in Autheo Mainnet’s IBC asset-validation mechanism that allowed an unauthorized external asset to be converted into native THEO.

The development and security teams have developed a fix targeting the identified exploit pathway.

The fix introduces additional safeguards against unauthorized asset conversion and native-token issuance, requires authorization for new cross-chain connections, and strengthens cross-chain security controls.

The code remains in internal testing. It will not be deployed to production until testing and further verification are complete.

Internal reviews are assessing the fix, alternative attack pathways, and recovery procedures.

After internal testing, Autheo intends to engage an independent third-party auditor. These reviews will help determine the conditions required before Mainnet and affected cross-chain services can be restored.

Mainnet and affected cross-chain services remain suspended. There is no restart date at this time.

Supply reconciliation and recovery planning are continuing. We will communicate further developments through official Autheo channels as verified information becomes available.

AUTHEO COMMUNITY UPDATE | OCTOBER 20

A week ago, on October 12, Autheo Mainnet was halted following a security incident involving the unauthorized creation of THEO.

Since then, our engineering and security teams, infrastructure partners, and independent specialists have been working to trace affected assets, develop and test corrective measures, and establish a responsible recovery process.

Where things stand:

• Mainnet and affected cross-chain services remain suspended.
• Remediation and supply reconciliation are ongoing.
• Independent security verification is required before affected services resume.
• No restart date has been announced.

Important:

Do not initiate new bridge transfers or repeat pending transfers. Beware of fake recovery offers, and never share your seed phrase or private keys.
We’ll continue sharing updates as meaningful milestones are verified.

Read the full update:
autheo.com/blog/autheo-co…

Autheo Community Update

We understand the concerns and uncertainty surrounding the recent security incident, and we want our community to know that we are taking this situation seriously.

Our team is working with our technical partners to assess what occurred and determine the appropriate next steps. At this time, please do not buy, sell or bridge THEO.

We recognize the impact this situation has on our community and do not take your trust lightly. We are committed to addressing the incident responsibly and sharing updates as verified information becomes available.

Thank you for your patience and continued engagement as we work through this. We remain focused on transparency, accountability, and keeping our community informed as the situation develops.

— The Autheo Team

We want to address the security incident affecting Autheo directly and transparently. On October 12, 2026, we became aware of an exploit involving the unauthorized minting of base:0xebe516a20238f79dc20b07ead6768e08891ed309 tokens by an unauthorized actor, followed by transfers to Base. We are investigating the circumstances of the incident, including the number of tokens affected and any associated transfers or sales. We are also assessing the impact on trading liquidity and the broader ecosystem. The full scope and financial impact of the incident have not yet been confirmed.

Our team is treating this with the utmost urgency. As an immediate precautionary measure, we coordinated with our infrastructure partners to halt block production on the Autheo Mainnet, take validator nodes offline, and stop the affected cross-chain relayer to prevent further unauthorized activity. These measures are intended to remain in place until the identified vulnerabilities have been addressed and the network can be safely restored. We are actively investigating the incident and determining the appropriate remediation and recovery steps.

We understand the concern this creates for our community, and we take this situation extremely seriously. Our priority is to establish the facts, address identified security risks, and determine the appropriate next steps, including potential remediation and recovery measures.

We will share further updates as we verify material information and have meaningful developments to report. Please rely on our official website and social channels for updates and be alert to impersonation accounts and unsolicited “recovery” offers. Never disclose your seed phrase or private keys, or connect your wallet to an unverified site claiming to provide incident-related support.

We know the community needs clear information. We will distinguish confirmed findings from matters still under investigation and correct any earlier information if our findings change.

🚨 URGENT SECURITY NOTICE

The Autheo team is investigating a security incident involving THEO. Our development team is actively looking into the issue.

⚠️ Until an official all-clear is issued:

🛑Do not buy, sell, or bridge THEO.
🛑Do not interact with suspicious links or contracts.
🛑Do not trust unsolicited recovery or compensation offers.
🛑Never share your seed phrase or private keys.

Transaction support is only via support@autheo.com
We will share verified updates exclusively through our official channels. Please stay alert and beware of impersonators.