Prior exploit count
Maple Finance's assessment for RD-F-077 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
1 documented incident: Orthogonal Trading credit default December 2022, ~$36M bad debt. Not a smart-contract exploit. Recovery was partial (depositors faced up to 80% losses). No smart-contract exploits on record. Yellow per methodology (1 incident with partial recovery).
Detail #
Orthogonal Trading defaulted on eight loans totalling ~$36M on December 5, 2022. They misrepresented financial exposure to FTX. Pool cover was < $2M across affected pools. Kroll engaged for recovery. No full restitution confirmed. The broader FTX contagion cycle (Celsius, Alameda pool delegates also in distress) added to platform stress — total sour debt was approximately $54M per CoinDesk Dec 12 — but this is context for the same credit crisis period, not a separate discrete incident. Rekt DB: zero entries. hacksdatabase: no entries found for maple or orthogonal. Methodology threshold: green = 0 prior exploits; yellow = 1 exploit with full recovery (partial recovery here keeps it at yellow even though event class is credit, not code).
Sources #
- URLFTX Contagion Spreads as Orthogonal Trading Gets Default Notice for $36M Debt on Maple FinanceCoinDesk — Maple severs ties with Orthogonal Trading, Dec 5 2022retrieved 2026-04-27
- Maple Finance's $54M of Sour Debt Shows Risks of Crypto Lending Without CollateralCoinDesk — $54M sour debt, Dec 12 2022retrieved 2026-04-27
- Data cache sources.rekt.incidents = []Rekt DB via data cache — zero incidents listed for maple-financeretrieved 2026-04-27
Methodology #
Count the number of distinct incidents in the hack database affecting this protocol.
See the full factor methodology and distribution across all protocols →