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

oracle manipulationDemo

Apr 29, 2024 · $8.8M · protocol

Narrative

On 2024-04-29, AWS Managed Blockchain suffered a oracle manipulation incident resulting in approximately $8,804,680 in losses. The exploit targeted the protocol layer. A flash loan was used to amplify the attack. Attribution: whitehat. This is a demonstration entry — not a real incident.

Classification

Root cause
oracle_manipulation
Secondary causes
flash_loan_governance
Attack layer
protocol
Strategy
market_manipulation
Actor role
target
Attribution
whitehat
Attacker address
0x6360c4b00342e227abc98baca883de4dfd40f3ef
Flash loan
yes
Audited at time
yes
Bounty at time
no

AADAPT mappings

DEMO:AADAPT.TA0040DEMO:AADAPT.TA0007DEMO:AADAPT.T1499.001DEMO:AADAPT.T1565.003

Evidence

Disclosure date
May 1, 2024
Funds recovered
$2M
Audit firms at time
Spearbit, Certora
Post-mortem URLs (synthetic)
  • https://medium.com/aws-managed-blockchain/post-mortem-aws-managed-blockchain-2024-04-29
  • https://rekt.news/aws-managed-blockchain-rekt
  • https://blog.aws-managed-blockchain.xyz/incident-report
tx hashes (3)
  • 0xb68a1715cf4b95f08f96b062c501199d71fdbdbd3b4ea8bb565f5adf2a6f7c0c
  • 0x59b8a16c608b8969aac08fa5a5c066141f5e3595695aa0eb4d1dc8f8cc3d5ee7
  • 0xa0a307214218187c77d68708a1b44f34a9bb01d6f515780c3f6fec8b0c6ad56c