Fact-check findings
What an automated fact-checker found when it re-read MakerDAO Legacy Auction Keeper Exploit (October 2026) 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.
unverifiable
1 claimNo source the reviewer could reach confirms or contradicts the claim.
- #8[unverifiable][awaiting moderator]in the timeline
“On-chain monitoring accounts (Defimon Alerts, Cryptoiz Research) publicly flag the exploit and state that MakerDAO's core Vat, Flipper, and GemJoin contracts behaved as designed and were not breached.”
reviewerCore Vat, Flipper and GemJoin contracts functioned as designed; on-chain monitors Defimon Alerts and Cryptoiz Research flagged the exploitCrypto Times returned 403. Protos and CertiK are consistent with the core being unaffected, but the named monitoring accounts could not be checked.
partially supported
2 claimsThe cited evidence supports part of the claim but not all of it.
- #3[partially supported][awaiting moderator]in section: The Exploit
“The attacker's malicious module used the delegated authority to call deal() on a retired ETH-A Flipper auction contract, settling four 50-ETH auction lots (auction IDs 1457-1460) that the keeper had won with zero bids during the March 2020 'Black Thursday' market crash but had never claimed.”
reviewerFunction accepted arbitrary adapter, granted Vat.hope, no auth check; four 50-ETH auctions 1457-1460 settled via deal() on Flipper; flux and GemJoin exit as WETHCore mechanism and IDs confirmed. The step-level detail (flux, GemJoin WETH exit) was not individually confirmed in the fetched text, and KuCoin says the auctions were 'never paid for' rather than never claimed. - #6[partially supported][awaiting moderator]in section: Laundering via Tornado Cash
“The requester's description of 'ten batches' is consistent with reporting but could not be independently confirmed with precision across all sources, so this detail should be treated as approximate.”
reviewerPage text refers to 'the requester', an artifact of the research process that does not belong in published proseThe caveat itself is accurate. 'The requester' refers to a party the reader cannot identify. 'Ten batches' is probably a misreading of '10 ETH batches'.
confirmed
8 claimsThe cited evidence supports the claim as written.
- #1[confirmed][no action needed]in the summary
“On October 6, 2026, an attacker drained approximately 200 ETH (roughly $538,000-$543,000)”
reviewerAttacker drained about 200 ETH (~$538,000-$543,000) from a dormant third-party keeper on October 6, 2026CertiK gives $542,982. The $538K lower figure comes from the Crypto Times headline, which I could not fetch (403). - #2[confirmed][no action needed]in section: The Exploit
“At approximately 06:13:11 UTC on October 6, 2026, an attacker exploited function selector 0x8804d1de in a legacy MakerDAO auction-keeper implementation contract (address 0x68399ed8aa33C5b43F863EE6782de492006A5546), used via an upgradeable proxy.”
reviewerExploit at ~06:13:11 UTC via selector 0x8804d1de in implementation 0x68399ed8...5546Matches CertiK. - #4[confirmed][no action needed]in section: Root Cause: Missing Access Control
“Additionally, the function never called a corresponding 'nope' function to revoke the delegated Vat authority it granted, meaning the malicious module's control over the keeper's Vat account persisted after the transaction completed.”
reviewerFunction lacked ds-auth check and never called nope, leaving delegation activeConfirmed. - #5[confirmed][no action needed]in section: Laundering via Tornado Cash
“Reporting indicates the attacker's externally owned account was funded with a single 0.1 ETH withdrawal from a Tornado Cash pool prior to the attack, which CertiK's analysis states was the account's only funding source.”
reviewerAttacker EOA funded by a single 0.1 ETH Tornado Cash withdrawal, its only funding sourceConfirmed. - #7[confirmed][no action needed]in the timeline
“Roughly six minutes after the exploit, the attacker begins moving the stolen ETH back into Tornado Cash in multiple batches.”
reviewerLaundering began about six minutes after the exploitConsistent with KuCoin. Not independently checked against on-chain data. - #9[confirmed][no action needed]in section: Scope: Core Protocol Unaffected
“Protos reported that the exploited contract 'wasn't a core part of the current Sky ecosystem,'”
reviewerProtos reported the contract 'wasn't a core part of the current Sky ecosystem'Confirmed. - #10[confirmed][no action needed]in section: Pattern: Dormant Legacy Contracts as Attack Surface
“Protos observed that 'even contracts that haven't been central for half a decade can still be lucrative targets for attackers if they contain real value.'”
reviewerProtos quote about contracts not central for half a decade remaining lucrative targetsConfirmed. - #11[confirmed][no action needed]in section: Pattern: Dormant Legacy Contracts as Attack Surface
“No regulatory or law-enforcement action related to this specific incident had been reported as of the time of this writing, and the identity of the attacker has not been publicly established.”
reviewerNo regulatory or law-enforcement action reported and attacker unidentifiedA negative claim. A status search turned up no contrary reporting.