Taken i
—
No dollar figure was reported, so we do not rank it by size.
At a glance
- Date
- Jun 8, 2023
- Severity
- —
- Way in
- Smart contract
- How
- Contract vulnerability
- Chain
- —
- Recovered
- None reported
What happened i
A bug in Arbitrum's sequencer code caused a temporary outage in the network's batch transaction submission, preventing transactions from being confirmed on the main chain. The issue was fixed, but the impact on users remains unclear.
Funds after the attack i
Nothing recovered, returned or frozen has been reported so far. Funds often come back days or weeks after a theft; this updates when the record does.
Timeline i
- Jun 8, 2023 The attack · Funds taken
- Added to our incident archive
BlockBoard stories i
Similar past incidents i
| When | Who | How | Taken |
|---|---|---|---|
| Nov 17, 2026 | B18 TimeBank | Smart contract vulnerability | $404.5k |
| Nov 17, 2026 | Paytaca | Backend vulnerability | — |
| Nov 16, 2026 | MORE Markets | Smart contract vulnerability | $308.0k |
| Nov 15, 2026 | Chain Games | Smart contract vulnerability | $20.0k |
| Nov 14, 2026 | Kava Lend | Smart contract vulnerability | $3.8M |
| Nov 14, 2026 | Luxor | Software vulnerability | $10.5k |
Earlier incidents at Arbitrum i
| When | How | Taken |
|---|---|---|
| Jul 20, 2024 | DNS attack | — |
Source: BlockBoard. Information only, not advice.