Illustrative scenarioDate not recordedIllustrative scenario

BGP Prefix Hijack Inadvertent Cryptocurrency Wallet Redirection

Rogue BGP route announcement redirected DNS queries for major cryptocurrency portal to malicious server for 2 hours.

Illustrative scenario, not a real incident

A composite failure pattern written by CollectSEA for learning and demos. It is NOT a documented real-world incident and has no primary source.

What happened

Contributing factors stated by the source

Rogue BGP route announcement redirected DNS queries for major cryptocurrency portal to mal...

The failure pattern

Duplicate action after an ambiguous resultA request times out, the caller assumes it failed and retries, and the money moves (or the order ships) twice.How to prevent it Destructive operation without verified recoveryA delete, cleanup or teardown runs against the wrong target, and the backups that should save the day turn out not to work.How to prevent it

Watch the pattern: Duplicate action after an ambiguous result

Related standards

CollectSEA's mapping through this incident's failure pattern; not an official determination by the standards bodies.

Building something similar?

Describe your design and see every precedent that applies, with safeguards you can hand to your coding agent.

Analyze your design

Documented incidentPublished 2017-02-22

Design reference: idempotency keys make retried payment API calls safe (Stripe)

Stripe explains that a client which cannot tell whether a request succeeded (for example after a network failure) needs to retry safely, and that without protection a retried charge could double-charge a customer.

Duplicate action after an ambiguous resultstripe.com

Security advisory2026-10-13

Software component issue could cause actions to run with inconsistent state

A public security advisory describes this issue. Review the linked source for the technical details and remediation guidance.