Aave Loop Safe Module exploit: 114 ETH into Railgun in 98 minutes, and a bounty offer that came four hours late

PublicAML · On-chain investigation · 14 October 2026

On 1 October an attacker emptied two Safe wallets that used FlashLoopAdapter, a third-party module that opens and closes leveraged Aave v3 positions. SlowMist put the loss at 114.09 ETH, about $305,000, and Aave said its own contracts were not affected. We read the wallets. The attacker paid for gas from Railgun and put all 114 ETH back into Railgun 98 minutes after the attack. The owners offered a 10% bounty on chain four hours after the money was already gone. Both drained Safes answer to one key, and the address that deployed the adapter works for other Safes of the same owner: the module was their own tool.

114.10 ETH

kept by the attacker, about $305,000, from 1,312.9 weETH of collateral

98 minutes

from the exploit transaction to the last ether entering Railgun

4 h 17 min

after that, the owners’ on-chain offer: keep 11.41 ETH, return 102.69

1 owner key

behind both drained Safes; of 24,998 module activations since July, only these two enabled the adapter

What is known

FlashLoopAdapter (0x16bb8b912da187870c23ec6756bb3fad061283d8) is a Safe module: a Safe that enables it lets the adapter open and close looped positions on Aave v3, where weETH is deposited as collateral, ether is borrowed against it and deposited again. SlowMist and Defimon Alerts reported on 1 October that the adapter's check could be passed by a fake Safe that simply answered "yes, the module is enabled", and that about 114.09 ETH was lost from two Safes. Aave's founder said the attack did not touch Aave v3 itself, only a module built on top of it.

Below is what the wallets show, read by us on 14 October 2026.

How the 114 ETH were taken

The attacker's wallet, 0x42c2633438609881c8fBAb82414eb9A0c45F9353, deployed a small factory at 14:44 UTC, and the factory created the attack contract 0xF09168963ac7b31917A02Aa82fA9Cd667F4B67ff at 15:02. At 15:08 that contract borrowed 11,537 WETH from Morpho in a flash loan and used it to repay the Aave debt of the first Safe, 0xcfedf95a3653a128dfc2e4288758a1a1850d169f: 1,335.26 WETH. With the debt gone, the adapter released the Safe's collateral, 1,306.48 weETH, and the second Safe, 0xe3b23e47df7cd85876ac6cb05bdb9d7cd5b28520, gave up another 6.43 weETH.

The 1,312.9 weETH were sold in the same transaction through Curve, Fluid, Uniswap and the Paraswap router for 1,449.35 WETH. The flash loan was repaid, and what remained, 114.10 ETH, went to the attacker. The owners lost the difference between their collateral and their debt, the equity of the position.

When (UTC)FromToAmountTx
1 Oct 14:150xAc9f36…2aD4050x42c263…5F93530.049875 ETH
gas money, unshielded from Railgun
0xc5dc26…63852b
1 Oct 14:440x42c263…5F93530x4a418c…b1f84acontract created
factory deployed by the attacker
0x378c12…c08e71
1 Oct 15:020x4a418c…b1f84a0xF09168…4B67ffcontract created
attack contract created by the factory
0x0c2bba…6a3884
1 Oct 15:080xcfedf9…0d169f0xF09168…4B67ff1,306.48 weETH + 6.43 weETH
weETH collateral released from both Safes after the flash-loan repayment
0x75328f…616fc4
1 Oct 15:080xF09168…4B67ff0x42c263…5F9353114.10 ETH
what was left after repaying the flash loan
0x75328f…616fc4
1 Oct 16:450x42c263…5F93530x951Ad2…A32f1a114.13 ETH
to a fresh address
0x3a5663…f753f9
1 Oct 16:460x951Ad2…A32f1a0xAc9f36…2aD405114.03 ETH
deposited into Railgun one minute later
0xa20636…266dc9
1 Oct 21:030x329c54…543eD40x42c263…5F9353message, 0 ETH
the owners’ 10% bounty offer, 4 h 17 min after the Railgun deposit
0x94b691…3289d0

Railgun in, Railgun out

The attacker's wallet received its first and only funding at 14:15 UTC, 53 minutes before the attack: 0.049875 ETH from Railgun's relay contract 0xAc9f360Ae85469B27aEDdEaFC579Ef2d052aD405. That is 0.05 ETH minus Railgun's 0.25% unshield fee. At 16:45 the wallet sent 114.13 ETH to a fresh address, 0x951Ad21B85C1Ce165F15d548a7C7D42520A32f1a, and one minute later that address deposited 114.03 ETH into Railgun through the same relay contract. Nothing was left on either wallet but change.

Railgun is a privacy system: from the deposit onwards, the chain no longer shows where the ether goes. We have not tried to follow it further.

The bounty offer came after the money had gone

At 21:03 UTC the owner of both Safes, 0x329c54289Ff5D6B7b7daE13592C6B1EDA1543eD4, sent the attacker a message in a zero-value transaction. It offered a 10% whitehat bounty: keep 11.41 ETH, return 102.69 ETH by 3 October 18:00 UTC, and the matter would be closed. By then the ether had been in Railgun for four hours and seventeen minutes. Nothing came back, and the owner's later transactions show no return.

Whose module was this

Both drained Safes have exactly one owner, the same key 0x329c54289Ff5D6B7b7daE13592C6B1EDA1543eD4, with a threshold of one. They were set up on 17 and 18 July 2026, the days after the adapter was deployed on 16 July by 0x3Cbded22F878aFC8d39dCD744d3Fe62086B76193.

That deploying address is not a Safe owner, but it submits transactions to three other Safes, among them 0x8353D558114BCd3Fa3405BB374452BD42A780DB6, whose owners include the same key 0x329c54289Ff5D6B7b7daE13592C6B1EDA1543eD4. In other words, the people who deployed the adapter and the people who lost money through it work with the same keys. We also read every module activation on Ethereum since the adapter was deployed, 24,998 of them: only two Safes ever enabled FlashLoopAdapter, the two that were drained. The press called it "an Aave-linked exploit"; on chain it looks like a team's own tool that only the team used.

The attacker was poisoned too

From 1 to 14 October the attacker's wallet received a long stream of fake transfers: tokens named "ETH", including copies written with look-alike letters, sent from and to addresses that start with 0x951A and end with 2f1a, like the real exit address 0x951Ad21B85C1Ce165F15d548a7C7D42520A32f1a. This is address poisoning: someone hopes the attacker will copy a look-alike address from the wallet's history and send the next payment to it. It shows that poisoning bots watch hack wallets as closely as anyone else's.

What we did

Two of the attacker's addresses, the wallet and the exit address, were already marked as hack in our database. We added the attack contract and the factory that created it. We did not mark the two Safes, their owner or the adapter's deployer: they are the victims.

To check an address yourself, use the address check.

What this page does not say

It does not say who the attacker is, or that Aave, Morpho, Railgun, Safe or any exchange did anything wrong. The mechanics and the 114.09 ETH figure were first reported by SlowMist and Defimon Alerts. The Railgun funding and exit, the timing of the bounty offer, the single owner key and the link between the adapter's deployer and the owners are ours, read on 14 October 2026.

Addresses in this case

Check an address yourself

Free, no sign-up. Paste any address to see whether it is linked to this or any other incident:

Sources: SlowMist and Defimon Alerts on the incident and its mechanics; Aave founder Stani Kulechov on the scope; crypto.news, Cointelegraph and CryptoSlate coverage; Ethereum data via Blockscout and public nodes, read by PublicAML on 14 October 2026. The dollar value is the one reported on 1 October. This is an information resource about transactions between addresses, not financial or legal advice, and it names no individual as responsible for anything.