Notes / Audits and snapshots

Authority-related incidents 2024 to September 2026: evidence table and what it can and cannot calibrate

Audits and snapshots2026-09-21Chain: not stated

Source: data/research_2026-09-21-authority-incidents-evidence-table.md in the repository, rendered here without changes. Source file

Compiled on 21 Sep 2026 by a research reviewer (web search and page reads only, no on-chain reads), then spot-checked by me. Read this as a lead list, not as verified data. I opened three rows (Humanity, AFX, CrediX) and corrected two details; two more incidents (SquidRouterModule, rsETH) I corroborated with separate searches, and Drift matches this repository's own backtest. The other rows are the reviewer's reading of the cited page and I did not open them.

DateProtocolLossClassConfiguration when it happened (only what the source states)How authority was obtainedSourceMy check
2024-03-26Munchables$62.5Minsiderupgradable proxy, owner is the developer's EOA, no timelockhired developer, DPRK link per HalbornHalbornnot opened
2024-05-20Gala Gamesabout $21.8M sold (5B GALA minted)role keyMINTER role on an EOA dormant for about 180 days, no timelockkey compromised, vector unknownHalbornnot opened
2024-07-18WazirX$235Mblind signingSafe 4/6 (5 WazirX + 1 Liminal), no timelockphishing and a fake Liminal UIQuillAuditsnot opened
2024-09-16DeltaPrime$6Madmin keyproxy admin is an EOA, no timelockkey leaked, cause unknownThe Blocknot opened
2024-10-16Radiant$53Mblind signingSafe 3/11, no timelock (72 h added afterwards)malware through a fake PDF, hardware wallet did not parse the Safe transactionRadiant post-mortemnot opened
2025-02-21Bybit$1.46BUI supply chainSafe 3/6, no timelock on the masterCopymalicious JavaScript served from Safe{Wallet}'s storageNCC Groupnot opened
2025-02-24Infini$49.5Minsideradmin role kept by the contract's developerrights never revokedDecryptnot opened
about 2025-02-05Ionic Money$8.6Mrole abuse (listing)listing admin, timelock unknownsocial engineering (fake Lombard)Rektnot opened
2025-04-01UPCX$70Madmin keyProxyAdmin key, no timelockkey leaked, cause unknownHalbornnot opened
2025-04-14KiloEx$7.5Maccess-control bugKeeper role, forwarder without a checkrole spoofed through a bugHalbornnot opened
2025-08-04CrediX$4.5Mrole grantsACLManager roles (pool, risk and bridge admin) given by the multisig to a new address about 6 days earliermultisig compromised or insiderHalbornsource unreachable (HTTP 429), not verified
2025-09-08SwissBorg$41Mdelegated authoritystake authority run by partner Kilnpartner API compromised, authority transferred on 31 AugQuillAuditsnot opened
2025-09-22UXLINKat least $11.3Mmultisig takeoverSafe, threshold unknown, no timelockdelegatecall then addOwnerWithThresholdThe Blocknot opened
2026-01-31Step Financeabout $40Mteam keysSolana treasury, configuration unknownexecutives' devices compromisedBleepingComputernot opened
2026-03-22Resolv$23M to $25Moff-chain service keySERVICE_ROLE signed off-chain, no cap or sanity checkAWS KMS compromisedChainalysisnot opened
2026-04-01Drift$285Mpre-signing and governanceSecurity Council 2/5, timelock 0 after a migration on 26-27 Martwo of five signers tricked (durable nonce, months of social engineering)BlockSecmatches this repository's own backtest and a QuillAudits read (2/5, zero timelock, admin transfer 1 Apr)
2026-04-18Kelp DAO bridge$292Mverification authorityverifier set of one (DVN 1-of-1), no timelocktwo LayerZero RPC nodes compromised plus DDoSChainalysisthe amount is also in this repository's README; not opened
2026-05-07TrustedVolumes$6.7Mself-assignable rolepublic signer-registration functionaccess-control bugFinanceFeedssingle aggregator source
about 2026-05-15SquidRouterModule$3.2M to $4Mfaulty Safe module86 Safes had enabled the module, which bypasses the thresholda fixed string readable in the verified codeHalborncorroborated by several outlets (Halborn, Common Prefix, AMBCrypto, others)
2026-05-18Echo eBTC$76.7M notional, about $0.87M realsingle admin keysingle-signature admin, no timelock, no mint capkey compromisedCointelegraphEcho is a live target of this oracle (37); not opened
2026-06 (reported 9 Jun)Humanity Protocol$32M to $36Mmultisig keys on one deviceSafe 3/6 (Ethereum) and 3/5 (BNB Chain); keys accidentally backed up to one compromised devicedevice compromiseCoinDeskchecked: loss, thresholds and cause match; the article does not state a ProxyAdmin timelock (the reviewer wrote "none")
2026-07-22AFX Trade$24.15Mquorum reached with stolen keystwo-thirds quorum, five hot validator signaturesvalidator keys held off-chain compromisedCoinDeskchecked: loss and quorum match; a 200-second dispute period existed (the reviewer wrote "no timelock") and the validator set size is not stated (the reviewer wrote 5 of 7)
2026-09-15rsETH Safe of a liquidity provider$7.7M to $7.8Mbuggy strategy modulemodule enabled by the owners, public DELEGATECALL entry, zero signatures neededpublic keeper multicallCrypto Timescorroborated by several outlets

Set aside for lack of a second source: Term Labs (August 2026, $8.5M, vault governance abuse) and THORChain (May 2026, $10.8M, malicious validator in a TSS scheme).

What the table supports (the reviewer's answers, with my edits)#

23 incidents, about $2.75B in total; amounts differ between outlets, and Bybit, WazirX, SwissBorg and Step are custodial actors rather than DeFi protocols, which inflates the key-and-signer share.

What this means for the oracle#

  1. Do not claim prediction. The honest claim is "measured exposure of the authority path", because the data cannot show that any configuration predicts incidents.
  2. Configuration changes are the leading indicator with days of lead time. Drift (timelock removed about five to six days before, per the reviewer's 26 Mar and QuillAudits' 27 Mar), CrediX (roles granted about six days before, unverified) and SwissBorg (authority transferred eight days before, unverified) all show a change on chain days before the loss. This is the evidence-based reason to prioritise the posture-change monitor: timelock lowered or removed, role granted to a new address, owner added or threshold lowered, module enabled.
  3. Publish what the oracle cannot see. Device compromise, falsified UI and supply-chain scripts, keys in a key-management service, pre-signed transactions, partner APIs, insider intent and module code all sit outside a configuration read (see the list above). A stated coverage limit is more credible than a silent one.

Not an audit, not investment advice. All notes ยท Back to the dashboard.