Preview surface — demo data. Where real data exists today (e.g. RealT, BlackRock BUIDL, Lift Dollar) we render it; everywhere else we render synthetic enrichment generated deterministically from public signal and clearly marked Demo or Inferred. The Phase 3 roadmap replaces every synthetic source with live ingestion — see Methodology → Exposure Graph & Similarity Engine.
← back to incident ledger

reentrancyDemo

May 3, 2023 · $5.2M · protocol

Narrative

On 2023-05-03, Jupiter suffered a reentrancy incident resulting in approximately $5,207,916 in losses. The exploit targeted the protocol layer. Attribution: unknown. This is a demonstration entry — not a real incident.

Victims

Classification

Root cause
reentrancy
Secondary causes
Attack layer
protocol
Strategy
tech_vuln
Actor role
target
Attribution
unknown
Attacker address
0xcf771851d40cc736257f77cc5a75436c7f26c4ac
Flash loan
no
Audited at time
no
Bounty at time
no

AADAPT mappings

DEMO:AADAPT.TA0004DEMO:AADAPT.TA0040DEMO:AADAPT.T1190

Evidence

Disclosure date
May 6, 2023
Funds recovered
Audit firms at time
Post-mortem URLs (synthetic)
  • https://medium.com/jupiter/post-mortem-jupiter-2023-05-03
  • https://rekt.news/jupiter-rekt
  • https://blog.jupiter.xyz/incident-report
tx hashes (4)
  • 0x2ddb245ef6932fc3ebb31e591369643bbe90e3176842b821c3552195d29a19a7
  • 0xe45a74c4799b4e92987050a6647553a5d12c51b2929614c8ee71430e3bc3c89c
  • 0x511be346ccebd99badf276f68bb3101bcef0638a64ebfae13ca69e21ba2651a9
  • 0x44e8a16c0724ead063491cb588e3b82a616e8bb918035ac773d00f8fea4bef91