Taken i
—
No dollar figure was reported, so we do not rank it by size.
At a glance
- Date
- Apr 25, 2024
- Severity
- —
- Way in
- Smart contract
- How
- Security vulnerability
- Chain
- —
- Recovered
- None reported
What happened i
On April 25, io.net's metadata APIs were compromised when a malicious party exploited exposed mappings between user and device identifiers to alter metadata, though GPU access remained intact.
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
- Apr 25, 2024 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 io.net i
| When | How | Taken |
|---|---|---|
| Aug 29, 2024 | Account compromise | — |
Source: BlockBoard. Information only, not advice.