Taken i
—
No dollar figure was reported, so we do not rank it by size.
At a glance
- Date
- May 16, 2023
- Severity
- —
- Way in
- Smart contract
- How
- Royalty vulnerability
- Chain
- —
- Recovered
- None reported
What happened i
A reported vulnerability on OpenSea affected how NFT project royalties could be set or changed, due to a change in ownership identification standards. The outcome for affected parties 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
- May 16, 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 OpenSea i
| When | How | Taken |
|---|---|---|
| Oct 28, 2022 | Contract vulnerability | — |
| May 6, 2022 | Account compromise | — |
| Feb 20, 2022 | Phishing attack | $3.4M |
| Jan 25, 2022 | Withdrawal Logic Flaw | $1.0M |
| Oct 13, 2021 | Malicious code injection attack | — |
Source: BlockBoard. Information only, not advice.