Slippage Protection Logic Flaw
Treat this as a reported explanation to test against code, traces, transaction data, and other primary evidence.
Preparing your view
Checking the session, access policy, and current workspace data.
Checking the session, access policy, and current workspace data.
Slippage Protection Logic Flaw
Slippage protection failed to account for reused intermediate tokens in multi-step swaps, causing $18.4M drain.
Imported-record overview
These fields reproduce or normalize claims in an imported research record. “Reported” describes provenance; it does not mean ChainRadar has confirmed the claim.
Treat this as a reported explanation to test against code, traces, transaction data, and other primary evidence.
Date-free learning path
Synthetic study sequence for learning purposes; timestamps and ordering may not reproduce the full verified incident chronology. Synthetic dates are deliberately omitted below.
STUDY PHASE
Ref.create_pool(fake_token)Ref.add_liquidity()STUDY PHASE
Route.construct(reused_tokens)STUDY PHASE
Rhea.borrow(debt_tokens)DEX.swap(fake_pools)STUDY PHASE
Rhea.liquidate(multiple_positions)STUDY PHASE
Reserve.withdraw(all_assets)STUDY PHASE
NEAR.delete_account(55_accounts)Teaching model
Educational reconstruction intended to explain the reported attack pattern, not a transaction-level evidentiary trace.
Start at Stage 1 and follow the numbered arrows. Every label is derived from the imported flow actions and structure.
Values describe reported movement between stages. Repeated amounts are not additional losses.
| Step | From | To | Reported action | Value |
|---|---|---|---|---|
| 01 | Liquidity Injection | Rhea Finance system | Liquidity Injection | $5M |
| 02 | Rhea Finance system | Routed assets · Stage 3 | Route Construction | $18.40M |
| 03 | Routed assets · Stage 3 | Routed assets · Stage 4 | Borrow & Route | $18.40M |
| 04 | Routed assets · Stage 4 | Value destination | Reserve Drain | $18.40M |
Imported indicators
Contract entries are reproduced from the local research archive. Confirm chain, bytecode, ownership, and incident relevance against primary evidence before using them in an investigation.
The absence of an address in this record does not establish that no contract was involved.
Defensive prompts
These imported mitigation labels are study prompts, not a complete or validated remediation plan. Test them against the protocol's actual architecture and failure mode.
Investigator workflow
Turn this background study into questions for a separate, evidence-led investigation. Never promote an educational edge or imported label into a finding without corroboration.
Preserve official disclosures, on-chain transactions, code, retrieval times, and other evidence supporting each material claim.
Start from corroborated addresses or transactions and trace each hop without assuming the educational flow is exact.
Compare decoded calls, logs, bytecode, and state changes with the reported cause.
Record provenance for every claim and identify gaps that still require confirmation.
Source status: cataloged. Classification: educational. Risk methodology: heuristic only. Primary-source verification remains required for every material claim.