Fact-check findings
What an automated fact-checker found when it re-read FlashLoopAdapter (Aave v3 Safe Module Exploit) against the sources the page cites. Only the most recent review is shown.
These findings are produced by an automated reviewer, and its results vary between runs: the same page, checked three times on the same day, came back with 15%, 20% and 34% of its claims disputed, mostly because each run extracted a different number of claims. Treat what follows as leads, not rulings.
“Disputed” means the reviewer could not reconcile the claim with the evidence it cited. It does not mean the claim is false. “Unverifiable” means no reachable source settled it either way.
Nothing here changes the page on its own. A proposed correction is applied only after a human moderator approves it; until then the page reads as it did when reviewed.
disputed
1 claimThe reviewer could not reconcile the claim with the evidence it cited. This is a lead, not a ruling that the claim is false.
- #6[disputed][awaiting moderator]in section: Technical Vulnerability
“The root cause is a classic reentrancy-adjacent pattern: caller-controlled input to a privileged function with insufficient identity validation.”
reviewerRoot cause is a 'classic reentrancy-adjacent pattern'No source characterizes this as reentrancy. The label is the page author's own and conflicts with the cited access-control description.Proposed correction (not yet applied)The root cause is insufficient caller validation: the module trusted a caller-supplied contract's own isModuleEnabled response and then made a raw call with caller-controlled calldata.
unverifiable
2 claimsNo source the reviewer could reach confirms or contradicts the claim.
- #8[unverifiable][awaiting moderator]in section: Attack Execution and Financial Impact
“The two on-chain transactions referenced in reporting include hash 0x75328f916b1a0878724d364da5eb12b255160b894cb36c63ed5d718efc616fc4 for the primary Safe withdrawal.”
reviewerTransaction hash 0x75328f... is the primary Safe withdrawalI could not find this hash in any source I fetched. The 'two transactions' framing is also unexplained, since the page says the attack was a single transaction. - #9[unverifiable][awaiting moderator]in section: Post-Incident Response and Recovery Efforts
“Following the exploit, both victim Safe wallets disabled the vulnerable FlashLoopAdapter module to prevent further losses.”
reviewerBoth victim Safes disabled the FlashLoopAdapter module after the attackThe cited Blockfence article does not say this. I did not check the other cited sources for it.
partially supported
5 claimsThe cited evidence supports part of the claim but not all of it.
- #1[partially supported][awaiting moderator]in the summary
“draining approximately 114.09 ETH (estimated at $305,000–$310,000) from two Safe multisig wallets on Ethereum”
reviewerExploit drained about 114.09 ETH (about $305K-$310K) from two Safe walletsFigures match reporting. The victims lost about 1,313 weETH of collateral, and 114.09 ETH is the attacker's net profit. The page's own attack-steps section says this correctly. - #3[partially supported][awaiting moderator]in section: Incident Overview
“Blockchain security firm SlowMist first publicly identified and reported the vulnerability.”
reviewerSlowMist first publicly identified and reported the vulnerabilityThe sources show SlowMist analyzed and reported it, and Defimon Alerts detected the attack. 'First' is not established, and the page's own Security Firm section says Defimon and ExVul also identified it. - #4[partially supported][awaiting moderator]in section: Incident Overview
“Both affected Safe wallets are reported by multiple sources to have belonged to the same owner, identified on-chain by the ENS name aavechan.eth.”
reviewerBoth Safes belonged to the same owner, aavechan.ethSame-owner is supported. The ENS identification appears in the Blockfence bounty report, which this section does not cite. - #11[partially supported][awaiting moderator]in section: Post-Incident Response and Recovery Efforts
“No law enforcement referral or on-chain tracing to a known entity has been publicly reported.”
reviewerAs of Oct 2, no reporting on attacker's response; no on-chain tracing reportedNo attribution to a known entity was found, so the sentence is defensible. The page omits the reported fund movement and the bounty deadline has since passed; see omissions. - #12[partially supported][awaiting moderator]in section: Audit and Development History
“One report noted this incident resembles a pattern of third-party module vulnerabilities built on top of Aave v3, suggesting the exploit may not be isolated.”
reviewerIncident resembles a pattern of third-party module vulnerabilities built on Aave v3Supported, but Blockfence names a concrete prior incident (about $7.8M rsETH, September) that the page leaves unspecified.
confirmed
5 claimsThe cited evidence supports the claim as written.
- #2[confirmed][no action needed]in section: Incident Overview
“On October 1, 2026, at approximately 15:08:57 UTC, an attacker exploited a critical access control vulnerability in FlashLoopAdapter”
reviewerExploit occurred at about 15:08:57 UTC on Oct 1, 2026, in a single transactionTimestamp is the detection time reported by Defimon Alerts. - #5[confirmed][no action needed]in section: Technical Vulnerability
“The attacker set the router address to a victim Safe wallet and the calldata to execTransactionFromModule”
reviewerFake Safe contract and _swap() raw call to execTransactionFromModuleThe technical description matches SlowMist's analysis. - #7[confirmed][no action needed]in section: Attack Execution and Financial Impact
“withdrawing approximately 1,306.48 weETH from the first Safe (0xcfedf95a3653a128dfc2e4288758a1a1850d169f) and 6.4 weETH from the second Safe (0xe3b23e47df7cd85876ac6cb05bdb9d7cd5b28520)”
reviewerAttack steps: Morpho flash loan, about 1,335 WETH debt repaid, 1,306.48 weETH and 6.4 weETH withdrawnAmounts and addresses match. The page's '1,306.48' is more precise than the sources I read, which say about 1,306. - #10[confirmed][no action needed]in section: Post-Incident Response and Recovery Efforts
“the attacker could retain 11.41 ETH and was asked to return 102.69 ETH before October 3, 2026 at 18:00 UTC”
reviewer10% bounty: attacker keeps 11.41 ETH and returns 102.69 ETH by Oct 3 18:00 UTCTerms match Blockfence. - #13[confirmed][no action needed]in section: Incident Overview
“Aave founder Stani Kulechov publicly clarified that the affected contract was a third-party external adapter and had zero effect on Aave v3.”
reviewerAave founder quote: 'zero effect on Aave v3'Corroborated by crypto.news and mpost.