Autheo THEO exploit: two unbacked mints, 119 million tokens, and about 292 ETH taken — not 700
PublicAML · On-chain investigation · 14 October 2026
On 12 October someone received 19 million THEO on Base that had never been locked on Autheo’s own chain, sold them into the token’s pool and bridged the ether to Ethereum. The reports that followed put the take at 700.8 ETH, about $1.76 million. We read the wallets. There were two mints, not one: another 100 million THEO arrived 39 minutes after the first. The sales produced about 291.7 ETH, roughly $730,000. The 700.8 figure is the balance of the attacker’s Ethereum wallet after the bridge, and about 400 ETH of it was already there before the attack.
119,000,000 THEO
minted to one address on Base in two messages, 17:06 and 17:45 UTC on 12 Oct
291.7 ETH
what the sales actually produced, about $730,000; all of it bridged to Ethereum
≈400 ETH
already on the Ethereum wallet before the attack, part of the reported 700.8
93.5M THEO
unsold, sent to an older wallet funded by Binance and MEXC withdrawals
What is known
THEO is the token of Autheo. On Base it exists as a Hyperlane bridge token (0xebe516a20238F79dc20b07ead6768e08891Ed309): it is minted on Base when a message arrives saying the same amount was locked on Autheo’s chain. Defimon Alerts pointed out that the route accepted messages through a TrustedRelayerIsm, a security module that trusts a single relayer, and called the 12 October mint an unbacked cross-chain mint. PeckShield reported 19 million THEO minted and swapped for 700.8 ETH, about $1.76 million. The price of THEO fell about 92% within a day, and Autheo told holders not to buy, sell or bridge the token.
Below is what the wallets show, read by us on 14 October 2026.
Two mints, not one
At 16:45 and 16:46 UTC the receiving address, 0x3048b4Ee5A070F33b73E3401829847255079E0AD, sent 250 and 25 THEO from Base back to Autheo’s chain, the normal way, to two other addresses. Twenty minutes later, at 17:06, the bridge contract on Base minted 19,000,000 THEO to it. At 17:45 it minted another 100,000,000 THEO to the same address. Both mints came from messages that named Autheo’s chain as the origin and were delivered by 0xeF305Ec5DF4054B15295A0389787bf671Ab930CE, the relayer that had delivered 378 messages to the Hyperlane mailbox on Base since 23 July and kept delivering ordinary ones after the attack.
The reports describe only the first mint. We cannot read Autheo’s chain from here, so we cannot say whether the two messages were forged at the relayer or emitted on the origin chain by mistake. On Base, both were accepted as real.
What the sales produced
The first 19 million THEO were sold through the Hydrex router in four swaps between 17:16 and 17:17 UTC for 280.70 ETH. At 17:18 the address sent 280.45 ETH to the Relay bridge, and the same address on Ethereum received 278.52 ETH eight seconds later.
Of the second mint, only 6.49 million THEO were sold, between 17:47 and 17:50, for 11.04 ETH: the price had already collapsed. Those went over Relay too, 11.21 ETH arriving on Ethereum at 17:52. In total the THEO sales produced 291.7 ETH, about $730,000 at the price of the day. A further 0.1 ETH went from Base to Robinhood Chain.
| When (UTC) | From | To | Amount | Tx |
|---|---|---|---|---|
| 12 Oct 17:06 | 0x000000…000000 | 0x3048b4…79E0AD | 19,000,000 THEO first unbacked mint on Base | 0x4fdbbc…73cd88 |
| 12 Oct 17:16–17:17 | 0x3048b4…79E0AD | 0x599bFa…2071f4 | 19.0M THEO → 280.70 ETH sold through the Hydrex router, four swaps; first one linked | 0x9d2a60…e73fcb |
| 12 Oct 17:18 | 0x3048b4…79E0AD | 0x4cD00E…38BC31 | 280.45 ETH into the Relay bridge on Base | 0x88728a…222154 |
| 12 Oct 17:18 | 0xb92fe9…4fFf4f | 0x3048b4…79E0AD | 278.52 ETH delivered on Ethereum eight seconds later | 0x104184…b3a557 |
| 12 Oct 17:45 | 0x000000…000000 | 0x3048b4…79E0AD | 100,000,000 THEO second unbacked mint, 39 minutes after the first | 0x8c8dc4…660730 |
| 12 Oct 17:47–17:50 | 0x3048b4…79E0AD | 0x599bFa…2071f4 | 6.49M THEO → 11.04 ETH sold at a collapsed price, three swaps; first one linked | 0xefbeed…ef2c56 |
| 12 Oct 17:52 | 0xf70da9…A3dbEF | 0x3048b4…79E0AD | 11.21 ETH second bridge payout on Ethereum | 0xad15a4…7d5424 |
| 12 Oct 17:57 | 0x3048b4…79E0AD | 0x690d75…fc6c83 | 93,510,011 THEO the unsold tokens, to an older wallet | 0x366288…84dfa1 |
| 14 Oct 05:32 | 0x3048b4…79E0AD | 0xc703C9…8af1e2 | 14.56 ETH to a wallet it had already paid on 5 Oct | 0xab086b…7be623 |
Where the 700.8 ETH figure comes from
After the bridges, the Ethereum wallet held 700.81 ETH. That is the number in the reports. But the wallet did not start empty. It received its first funds on 5 October: 414.4 ETH in one transfer from 0xf77331B2893B275A5C58F97723469837A25fa574, which emptied itself into it. That wallet in turn had received 281.4 ETH through the NEAR Intents bridge on 30 September and 174.6 ETH from another wallet on 5 October.
Between 5 and 12 October the new wallet sent about 77 ETH out through Relay, mostly in amounts of 3 to 9 ETH, and on the morning of 12 October it received another 68.4 ETH through NEAR Intents. Just before the attack it held 400.8 ETH. So most of the reported 700.8 ETH was not taken from THEO holders. It is money that had been on the wallet for a week, and it came from somewhere else. Where it came from before NEAR Intents we have not traced.
The 93.5 million THEO that were not sold
At 17:57 UTC the attacker sent 93,510,011 THEO, almost all of the second mint, to 0x690d7552375Fcd23Bd2a5E1d74f7445FAdfc6c83. They are still there. This wallet is not new: it has been in use on Base since September 2024, mostly for small swaps and bridge transfers. It has been topped up nine times from a Binance hot wallet and seven times from a MEXC hot wallet, which is what withdrawals from an exchange account look like. A minute before it received the 93.5 million, it bought 15,364 THEO in the pool itself. On 13 October it approved the THEO contract three times but did not sell.
Receiving tokens does not make a wallet’s owner the attacker: anyone can send anything to any address. But this transfer was made by the attacker, deliberately, with the part of the loot that could not be sold. Binance and MEXC can say who withdrew to this address.
Where the ether is now
On 14 October the attacker’s Ethereum wallet still held 686.23 ETH. At 05:32 UTC that day it sent 14.56 ETH to 0xc703C9bF559F8f9E2128F9366688f59D398af1e2, a wallet it had already paid 5.115 ETH on 5 October, its first day. Nothing has gone to a mixer so far.
Within minutes of each large transfer, strangers sent zero-value transactions and dust to this wallet from addresses that begin and end like its real counterparties. This is address poisoning. Anyone copying an address from its history should check every character.
What we did
We marked 2 addresses on Ethereum in our database as the attacker’s: the wallet that received the minted tokens and bridged the proceeds, and the wallet it paid on 5 and 14 October. Neither was marked before. We did not mark the wallet holding the 93.5 million THEO, the older wallet that funded the attacker on 5 October, the relayer, the bridges or the router: the chain links them to the attacker, but it does not show who controls them.
To check an address yourself, use the address check.
What this page does not say
It does not say who the attacker is, how the two messages were produced, or that Autheo, Hyperlane, Relay, Hydrex, NEAR Intents, Binance or MEXC did anything unlawful. The mechanics are Defimon Alerts’; the 19 million mint and the 700.8 ETH figure were first reported by PeckShield. The second mint, the 291.7 ETH the sales actually produced, the 400 ETH that were on the wallet before, and the wallet that received the unsold tokens are ours, read on 14 October 2026.
Addresses in this case
Attacker wallets (Ethereum)
Check an address yourself
Free, no sign-up. Paste any address to see whether it is linked to this or any other incident:
Sources: Defimon Alerts on the mechanics; PeckShield, Cryptonomist, crypto.news and The Crypto Times on the incident and the 700.8 ETH figure; Autheo’s notice of 13 October 2026; Base and Ethereum data via Blockscout and public nodes, the Relay bridge’s public request record; read by PublicAML on 14 October 2026. Prices are those of 12 October. This is an information resource about transactions between addresses, not financial or legal advice, and it names no individual as responsible for anything.