Quick Take
- Bitquery's Nov. 12 update estimates $401,900 in losses across nine wallets linked to the Across website hijack.
- The largest traced loss involved an Aave deposit token moved through signed spending permissions, exposing a separate lending position.
- Across Protocol pledged to reimburse affected users after reporting its domain restored.
A depositor in Aave lost about $305,000 in a deposit token during the Nov. 10 hijack of the cross-chain bridge Across Protocol's website, according to a Bitquery investigation updated Nov. 12.
Bitquery links the loss to spending permissions requested through the compromised interface, exposing a lending position held outside the bridge.
Bitquery's revised trace estimates $401,900 taken from nine wallets across five blockchains, using prices at the time the assets were stolen, and the Aave depositor accounts for about 76% of the traced losses. The update adds a previously missed ether sweep.
Across Protocol said its domain was taken over on Nov. 10 through social engineering involving its registrar, Namecheap.
How the Aave deposit token moved after the Across Protocol hack
The asset taken from the largest wallet was aWETH, an interest-bearing token representing an Aave deposit. Aave's documentation explains that its deposit tokens can be transferred and that a signed permit can authorize another account to spend them.
In Bitquery's reconstruction, the fake site requested a permit, which the attacker then used to move the depositor's tokens, and that spending permission put the separate lending position within reach.
The first transfer transaction on Nov. 10 recorded an unlimited approval followed by about 115.23 aWETH sent to one wallet and 28.81 aWETH to another. Bitquery identifies those recipients as the attacker's wallet and the drainer's fee wallet, respectively, matching an 80/20 split.
The depositor's transfer history shows four pulls ending three minutes after the first. Bitquery says the owner revoked the approval a minute after the last pull, but the transfers had already happened by that point.
How the website attack reached an Aave deposit
Bitquery links a signed permit to the loss of an Aave deposit token. The first transaction records spending approval followed by two transfers.
Inside the first Aave-token transaction
Bitquery describes a signed permit. The transaction records unlimited approval before the token transfers.
The same transaction sent about 115.23 aWETH and 28.81 aWETH to the wallets Bitquery identifies as attacker and fee recipients.
Spending permission over a transferable deposit token can expose a lending position held outside the bridge.
Bitquery infers the website connection from timing and recipient wallets. Blockchain records do not show the visited site or off-chain signing time. The split diagram covers only the first pull; $304,500 is the whole traced Aave-token loss.
Sources and evidence
Sources
Supporting facts
- Bitquery's November 12 investigation update estimates $401,900 taken from nine wallets on Ethereum, Arbitrum, Base, BNB Chain and Optimism during the November 10 Across website hijack. [1]
- Bitquery identifies the largest affected wallet as an Aave depositor that lost 148.60 aWETH, which it values at about $304,500, or 76% of its traced losses. [1] [4]
- Aave's aTokens represent supplied assets and accrued yield, can be transferred or traded, and support permit messages that authorize another account to spend them. [2]
- At 20:09:23 UTC on November 10, an Ethereum transaction recorded an unlimited aToken approval from wallet 0x42e7...483c and transfers of about 115.23 aWETH to 0x2846...1fde and 28.81 aWETH to 0x0c7c...d37b. [3] [1]
- The Aave depositor's transfer history shows four outgoing aToken pulls between 20:09:23 and 20:12:23 UTC on November 10; Bitquery says the owner revoked the approval a minute after the last pull. [4] [1]
- The Aave transaction records show approval-based transfers of the depositor's aToken, consistent with Bitquery's account of a signed-permit theft. [1] [2] [3]
- Bitquery links the drains to across.to through their timing and recipient wallets, while acknowledging that on-chain records do not identify which website a victim visited. [1]
Method
Uses reported rounded figures and the reported 76% share; the bar is 76% filled. Approval and transfer views show two parts of the same first transaction, not separate website observations. The total Aave loss spans four pulls.
Scope
Bitquery infers the website connection from timing and recipient wallets. Blockchain records do not show the visited site or off-chain signing time. The split diagram covers only the first pull; $304,500 is the whole traced Aave-token loss.
CryptoSlateThe Nov. 12 addition was a separate 26.38 ETH sweep from another victim, valued by Bitquery at about $54,000 at the time. Its Ethereum transaction records show ETH leaving on Nov. 10.
The revised tally also differs from the widely circulated $294,000 figure, as Bitquery says that number matched the fee wallet's holdings, including funds that predated the Across attack.
Bitquery ties the drains to Across through timing and recipient wallets, while acknowledging that blockchain records cannot show which website a victim visited.
On Nov. 11, Across Protocol said the domain was back under its control and pledged to make affected users whole and publish a postmortem.
Editorial credits
