Morning Edition · Saturday, October 3, 2026Published at 1:57 AM EDT · New York
The FlashLoopAdapter asked the caller whether it was allowed, instead of verifying it independently, and two multisig wallets lost about $305,000.

An attacker drained 114.09 Ether, worth roughly $305,000, from two Safe multisig wallets on Ethereum on October 2 by exploiting a third-party adapter those wallets had enabled as a module. Security researchers at DeFiHackLabs published a reproducible proof of concept labelling the root cause broken self-attestation.
The vector was access control, and the flaw was in who answered the authorization question. The adapter's open and close functions did not independently establish that the caller was a genuine Safe. They asked the calling contract whether the adapter was enabled as one of its modules, by calling isModuleEnabled on msg.sender. The attacker deployed a contract that simply returned true, then directed the adapter to execute arbitrary actions on its behalf. SlowMist, which traced the transactions, reported that the attacker took a Morpho flash loan in wrapped Ether, repaid roughly 1,300 wrapped Ether of debt to unlock the victims' collateral, and kept the surplus. Aave's core lending pools and the Safe wallet contracts themselves were used as designed and were not compromised. No recovery or freeze has been reported.
Two smaller incidents followed the same week. DeFiHackLabs published a proof of concept for an attack on SKYDAO worth about 59,900 Tether, in which the attacker burned tokens held by the liquidity pair and then forced a reserve resynchronization, moving the pool price before trading against it. A separate case drained roughly 32,000 Tether from a position manager contract that priced vault shares off a live spot pool, allowing an attacker to inflate share value before redeeming.
Security firms and audit providers gain commercial argument for extending reviews to third-party modules, and Aave and Safe benefit from the finding that their own contracts behaved as specified.
Part of a tracked trend
Losses Move to Components That Worked as Designed
A growing share of DeFi losses will come not from buggy contract code but from components behaving exactly as specified — oracle forwarders, validator signature sets, governance votes and other trusted off-contract inputs — so audits and bug bounties scoped to on-chain code keep missing the failure surface, and protocols will be repeatedly forced to extend review, scope and monitoring to their privileged operational infrastructure.
Start a discussion in Townsquare.
More from this edition
The 114.09 Ether figure and the forged-module mechanism are independently traced by SlowMist and reproduced by DeFiHackLabs, but the collateral unlocked was wrapped staked Ether (approximately 1,306 weETH) rather than wrapped Ether, and the "Aave-linked" label describes an unaffiliated third-party adapter, not Aave-authored code.
An open-source-intelligence read of how likely this story is true with its real nuance, not a judgment of any outlet. It assesses the claim, weighing independent and adversarial reporting. How we label confidence.
What this means
All three incidents share the same root cause: a trust-boundary error, where a contract trusted an input it should have verified independently. The adapter delegated an authorization decision to the party being authorized, and the two smaller contracts delegated a valuation decision to a pool the attacker could move. Audits scoped to a single contract pass in each case, because the contract does exactly what it was written to do. The exposed parties are users of composable modules, meaning anyone who grants an external adapter execution rights over a wallet, and the operators of vaults that read spot prices. Precedent runs from the 2020 bZx oracle manipulations through to the module and keeper compromises of the past two years, and in each wave losses moved toward privileged peripheral code. The likelier path over the coming months is more losses at integration points of this kind, with wallet interfaces beginning to surface module permissions more prominently, unless module registries start requiring independent verification of caller identity.
What to watch
Observations to monitor, not financial advice.
Synthesized from: DeFiHackLabs (proof of concept) · DeFiHackLabs (second commit) · DeFiHackLabs (SKYDAO proof of concept)
Comments
0No comments yet.