Onchain Files
File #005 · Base vault exploit: 1,783 wstETHMONITORINGv0.3 · findings locked · Oct 9, 2026

Drained in 17 minutes. Now leaving Base.

Base bridge→Attacker wallet→Attack contract→Vault→Aave (redeem)→Holding wallet

An unnamed vault on Base lost 1,783.067 aBaswstETH in six withdrawals between 08:55 and 09:12 UTC on Oct 4. The attacker redeemed it for wstETH and moved it to a second wallet. On Oct 9, 1,001 wstETH came out of Base's official bridge on Ethereum, and two minutes later the last 782.067 wstETH on Base went into the same bridge. Every figure below is tied to a transaction.

1,783.067wstETHTaken from the vault in six withdrawals. Reported as ≈ $6.0M (ExVul).
17minFrom the first withdrawal (08:55 UTC) to the last (09:12 UTC).
1,001wstETHOn Ethereum in 0xc734…7f8d unmoved (read Oct 13).
782.067wstETHSent into the slow bridge from Base on Oct 9, 13:55 UTC. The previous batch took about five days.
MONITORING

On Ethereum

1,001 wstETH

In the bridge to Ethereum

782.067 wstETH (sent Oct 9 13:55 UTC)

Still on Base

0 wstETH

Last move

Oct 9, 13:55 UTC

Last checked

Oct 13

The findings are locked. The status bar updates when the watched addresses move. Additions are logged below.

Update v0.3 · Oct 9, 15:15 UTC. On Oct 9 the holding wallet completed its withdrawals on Ethereum: 1 wstETH at about 11:50 UTC (tx 0xf3303041…b088) and 1,000 wstETH at about 13:54 UTC (tx 0xd17830a8…b681). Two minutes later, at 13:55:53 UTC, it sent its last 782.067 wstETH on Base into the same bridge (tx 0xb59dbbcc…e669). At 15:10 UTC it held 1,001 wstETH on Ethereum, unmoved, and nothing on Base. The 1,000 wstETH took about five days to clear the bridge, faster than the seven days we estimated.

Update v0.2 · Oct 4, 13:45 UTC. At 12:10:59 UTC the holding wallet sent a second transaction to the same wstETH bridge it used for the 1-coin test (tx 0x7b856099…3e14). Its balance fell from 1,782.067 to 782.067 wstETH, so about 1,000 wstETH is now on the slow route to Ethereum, where it can be released no earlier than about Oct 11. 782.067 wstETH remains on Base. We are watching both sides.

Current exposure

Stolen1,783.067 wstETH
Returned—
Frozen—
Still traceable≈ $5.5M

Where it can still be stopped

  • Monitored, not freezable today · WSTETH held in self-custody. If it reaches an exchange or a service, that is the moment to act; we watch for it around the clock.
  • Law enforcement · a full evidence pack (every transaction, CSV) is available on request.

The claim

"A brand-new contract was added to the vault's whitelist, then borrowed aBaswstETH from the vault and sent the aTokens to the attacker's contract. ~$2.02M drained so far across ~4 txs."

Blockaid on X, Oct 4 (early alert) Attributed

"An unnamed vault was drained of 1,783.067 aBaswstETH (~$6.0M) across six vault outflows. Root cause (preliminary): a newly whitelisted contract used the vault's borrowing path."

ExVul, Oct 4 (later alert) Attributed

The evidence

  • Verified

    Six withdrawals from the vault to the attack contract: 1 + 100 + 500 + 500 + 500 + 182.067 = 1,783.067 aBaswstETH, 08:55–09:12 UTC. The vault now holds 0.0007.

  • Verified

    The attack contract was created by the attacker's wallet at 07:28 UTC, 86 minutes before the first withdrawal.

  • Verified

    At 09:23 the attacker redeemed all 1,783.067 aBaswstETH for wstETH and sent it to a second wallet, 0xc734…7f8d, which still holds 1,782.067 wstETH.

  • Verified

    0xc734 sent 1 wstETH into the official wstETH bridge to Ethereum at 09:27 and submitted the withdrawal proof on Ethereum at 10:43.

  • Inferred

    The 1 wstETH is a test of the route for the rest. Method: same wallet, one coin, then a proof submitted within the hour.

The unknown

  • Unknown

    Who runs the vault, and its name.

  • Unknown

    How the attack contract got permission to withdraw. The vault itself logged no events; we have not found a whitelisting transaction.

  • Unknown

    Where the attacker's first 0.05 ETH came from on Ethereum before it was bridged to Base.

  • Unknown

    Who the attacker is.

01 · The window

Funded, armed and emptied before lunch.

The attacker's wallet received its first ETH at 06:49 UTC. It deployed three contracts, armed the last one, and drained the vault in six withdrawals between 08:55 and 09:12. By 10:47 the wstETH had moved to a second wallet, and a test coin was on its way to Ethereum.

2026-10-04 · UTC

Hover a marker for the transaction

Chart loading…

Shaded: the drain. Red ring: a look-alike address sending dust. Times UTC.

02 · Key findings

What the chain shows.

F1

Six withdrawals, one pattern

Verified

From 08:55 UTC the attacker's wallet called the attack contract twice per round: once to pull aBaswstETH out of the vault (1, then 100, then 500, 500, 500 and 182.067), once to pass it on to the wallet. The first round moved a single token. Thirteen minutes later the attacker came back for the rest. The six vault withdrawals add up to 1,783.067 aBaswstETH, matching ExVul's figure. The vault holds 0.0007 aBaswstETH today.

Evidence: Withdrawals 0x0ec75c3b…f491 … 0xf1c9448c…cd7e; payouts 0x6001ea94…ae29 … 0x8e434d44…7db7.

F2

Built that morning

Verified

The attacker's wallet was funded with 0.05 ETH at 06:49 UTC through Base's own bridge contract, so the money came from Ethereum. It deployed three contracts between 07:17 and 07:28. The third, 0xcdFE…569d, is the one that drained the vault. It was initialised at 08:10, 45 minutes before the first withdrawal.

Evidence: Funding 0x29aba031…7171; deploys 0x566e3d7e…3c26, 0x112b2347…5d34, 0xb4d1c2f4…8692; initialise 0x122dc220…9ce5.

F3

How it got in is not yet shown

AttributedUnknown

Blockaid and ExVul say the contract was added to the vault's whitelist and used the vault's borrowing path. The vault itself has logged no events since Sep 1, and we have not found the transaction that granted access. If the contract was whitelisted after it existed, that happened in the 86 minutes between 07:28 and 08:55.

Evidence: Vault event log, Sep 1 – Oct 4: empty. Contract created 07:28:57 UTC.

F4

Redeemed, then moved

Verified

At 09:23 the attacker withdrew the full 1,783.067 from Aave on Base: the aTokens were burned and the same amount of wstETH paid out. It sent 1 wstETH to a second wallet, 0xc734…7f8d, at 09:24, and the remaining 1,782.067 at 10:47.

Evidence: Redeem 0x557bfd0e…ee8c; transfers 0xe824b27c…85d2, 0x20fb64ee…e145.

F5

A test coin on the slow road

VerifiedInferred

At 09:27 the holding wallet sent 1 wstETH into the official wstETH bridge from Base to Ethereum. At 10:43, on Ethereum, the same address submitted the proof for that withdrawal to Base's bridge contract. Withdrawals on this route can only be completed after a waiting period of about seven days. One coin, then a proof within the hour, reads like a test of the route.

Evidence: Base 0x9c55eed4…81bc; Ethereum 0x3fdc8148…865b.

F6

Off Base, onto Ethereum

Verified

At 11:52 UTC, 0xc734…7f8d held 1,782.067 wstETH. Apart from the test coin it has spent only gas and 0.0074 ETH sent to an unidentified service contract. We are watching it on Base and on Ethereum. Update, Oct 9: the withdrawals cleared. 1,001 wstETH reached the same address on Ethereum (13:54 UTC), and at 13:55 the last 782.067 wstETH on Base went into the bridge. Nothing is left on Base.

Evidence: Balance read 11:52 UTC; 0xb2640faa…ec66. Oct 9: Ethereum 0xd17830a8…b681; Base 0xb59dbbcc…e669.

F7

Noise around the attacker

Verified

At 09:03 an address imitating the holding wallet (0xc73a…7f8d) sent the attacker dust, the usual address-poisoning trick; we filtered 10 such transfers. From 10:58 an unrelated wallet sent the attacker three on-chain messages urging further withdrawals. We record that they were sent and do not reproduce them.

Evidence: 0xcc455f64…0956; messages from 10:58 UTC (0x41c29f0d…0211 and two more).

03 · Money flow

Where the 1,783 wstETH went.

Every unit that left the vault reached the holding wallet. One unit is on its way to Ethereum; the rest has not moved since 10:47 UTC.

Value by route, wstETH

Hover a band for amounts

Chart loading…

04 · The whole trail

Every edge shows its evidence. Click one.

A grey line is a transfer we read on-chain. A dotted box is a name taken from a public label or a contract's own functions. Times UTC, Oct 4.

PREP · 06:49–08:10 DRAIN · 08:55–09:15 REDEEM · 09:23 NOW Base bridge0.05 ETH from Ethereum Attacker wallet0x0B51…B034 Attack contract0xcdFE…569d · from 07:28 Vault0xD189…CABC · unnamed Aave on BaseaBaswstETH → wstETH Holding wallet0xc734…7f8d · 1,001 wstETH on Ethereum Bridge782.067 wstETH · sent Oct 9

Click or tap any line in the map to see its evidence: status, transactions, time and amount.

Verified transferDirect cross-chain linkInferred linkNamed by label

05 · Evidence map

Every link, and what supports it.

LinkEvidenceStatus
Vault → attack contractSix aBaswstETH transfers, 1,783.067 in totalVerified
Why the vault paid the contractBlockaid, ExVul: a newly whitelisted contract using the borrowing pathAttributed
The access grant itselfNo vault events since Sep 1; transaction not foundUnknown
Contract → attacker walletEight payouts, 1,783.067 aBaswstETHVerified
aBaswstETH → wstETHwithdraw() at Aave's pool on Base; aTokens burned, wstETH paidVerified
Attacker → holding walletwstETH transfers at 09:24 and 10:47Verified
Holding wallet balance1,782.067 wstETH at 11:52 UTCVerified
Test withdrawal to EthereumwithdrawTo() on Base; proof on EthereumVerified
It is a test of the routeOne coin, proof within the hour, rest still on BaseInferred
Ethereum origin of the 0.05 ETHNot yet readUnknown
Verified
  • 1,783.067 aBaswstETH left the vault in six withdrawals
  • 1,001 wstETH sits in 0xc734…7f8d on Ethereum (Oct 9)
  • 782.067 wstETH is in the bridge to Ethereum (sent Oct 9)
Inferred
  • The 1 wstETH is a test of the route
Attributed
  • Whitelisted contract, borrowing path (Blockaid, ExVul)
  • Dollar value ≈ $6.0M (ExVul)
Unknown
  • Who runs the vault
  • How access was granted
  • Where the first 0.05 ETH came from
  • Who the attacker is

The two alerts gave different totals because the attack was still running: about $2.02M across about 4 transactions in Blockaid's early alert, 1,783.067 aBaswstETH (≈ $6.0M) across six outflows in ExVul's later one. The chain agrees with the later figure.

06 · Timeline

In order.

Oct 4 · 06:49Attacker wallet funded through the Base bridge: 0.05 ETH
Oct 4 · 07:17–07:28Three contracts deployed; the third, 0xcdFE…569d, is the attack contract
Oct 4 · 08:10Attack contract initialised
Oct 4 · 08:55First withdrawal from the vault: 1 aBaswstETH
Oct 4 · 09:08–09:12Five more withdrawals: 1,782.067 aBaswstETH
Oct 4 · 09:23Redeemed at Aave for 1,783.067 wstETH
Oct 4 · 09:27Holding wallet sends 1 wstETH into the bridge to Ethereum
Oct 4 · 10:43Withdrawal proof submitted on Ethereum
Oct 4 · 10:471,782.067 wstETH moved to the holding wallet
Oct 4Blockaid and ExVul alerts Attributed
Oct 4 · 12:10Holding wallet sends ≈ 1,000 wstETH into the bridge to Ethereum
Oct 9 · 11:501 wstETH test withdrawal completed on Ethereum
Oct 9 · 13:541,000 wstETH withdrawal completed on Ethereum
Oct 9 · 13:55Last 782.067 wstETH on Base sent into the bridge to Ethereum
Oct 9 · 15:10Last checked: 1,001 wstETH on Ethereum (unmoved), 782.067 in the bridge, 0 on Base

07 · Ledger

The transactions.

Every step, from funding to the test withdrawal.

Transactions
UTCEventAmountTransaction
Oct 4 · 06:49:43Attacker wallet funded via the Base bridge0.05 ETH0x29aba031…7171
Oct 4 · 07:28:57Attack contract 0xcdFE…569d deployed—0xb4d1c2f4…8692
Oct 4 · 08:10:53Attack contract initialised—0x122dc220…9ce5
Oct 4 · 08:55:01Vault → contract (withdrawal 1)1 aBaswstETH0x0ec75c3b…f491
Oct 4 · 09:08:13Vault → contract (withdrawal 2)100 aBaswstETH0xa08b0267…459b
Oct 4 · 09:09:21Vault → contract (withdrawal 3)500 aBaswstETH0x08327097…a154
Oct 4 · 09:10:19Vault → contract (withdrawal 4)500 aBaswstETH0x212dc5e0…80ac
Oct 4 · 09:11:11Vault → contract (withdrawal 5)500 aBaswstETH0x327e47ad…543f
Oct 4 · 09:12:37Vault → contract (withdrawal 6)182.067 aBaswstETH0xf1c9448c…cd7e
Oct 4 · 09:23:13Redeemed at Aave1,783.067 wstETH0x557bfd0e…ee8c
Oct 4 · 09:24:15Attacker → holding wallet1 wstETH0xe824b27c…85d2
Oct 4 · 09:27:29Holding wallet → bridge to Ethereum1 wstETH0x9c55eed4…81bc
Oct 4 · 10:43:11Withdrawal proof submitted on Ethereum—0x3fdc8148…865b
Oct 4 · 10:47:23Attacker → holding wallet1,782.067 wstETH0x20fb64ee…e145
Oct 4 · 12:10:59Holding wallet → bridge to Ethereum≈ 1,000 wstETH (balance 1,782.067 → 782.067)0x7b856099…3e14
Oct 9 · ≈11:50Test withdrawal completed on Ethereum1 wstETH0xf3303041…b088
Oct 9 · ≈13:54Withdrawal completed on Ethereum → holding wallet1,000 wstETH0xd17830a8…b681
Oct 9 · 13:55:53Holding wallet → bridge to Ethereum (balance 782.067 → 0)782.067 wstETH0xb59dbbcc…e669

Download every transaction behind this File (CSV): chain, time, from, to, amount, status and an explorer link for each. Check any line yourself.

08 · Method and standard

How we know.

Our engine traced the case from the attacker's wallet on Base, Ethereum, Arbitrum and Optimism, with fake tokens and look-alike addresses filtered. We then read the vault's token transfers and event log, the attack contract's creation and calls, and the holding wallet's activity on both chains, through Etherscan's API, and its balance at 11:52 UTC. Function names come from the contracts' public interfaces. Dollar figures are ExVul's.

Verified

Read on-chain by us. A direct link is proven by records on both chains.

Inferred

Our deduction from patterns. The method is stated.

Attributed

Someone else's claim or label. The source is named.

Project-reported

A statement from the project involved.

Unknown

What we could not establish, listed.

Sources