Cellframe Bridge 2026 hack and illegal token issuance
In a May 14, 2026 AMA, Cellframe said the team had announced a hack of the Cellframe bridge and illegal token issuance. The AMA cited about $2,000 for the illegal issuance in the question boundary, while explicitly stating that total damage had not yet been calculated and the internal investigation continued.
Incident facts
- Incident title
- Cellframe Bridge 2026 hack and illegal token issuance
- Bridge
- Cellframe Bridge
- Incident date
- 2026-05
- Incident type
- Exploit
- Major incident
- Yes
- Affected chains
- Unknown
- Affected assets
- USDC, Unknown
- Attack category
- Unknown
- Reported loss
- Approximately $2,000 was cited for illegal token issuance; total incident damage was explicitly not yet calculated.
- Amount confidence
- High
- Loss amount basis
- First Party AMA; Partial Amount Only
- Recovery
- Partial
- Reimbursement
- Unknown
- Restart
- Limited
- Current outcome
- Limited After Incident
- Postmortem
- Partial
- Resolution
- Unresolved
- Last reviewed
- 2026-08-27
- Last verified
- 2026-08-27
Amount and valuation
Approximately $2,000 was cited for illegal token issuance; total incident damage was explicitly not yet calculated.
The $2,000 figure is not promoted to a total-loss estimate.
Why this remains unresolved
- Cellframe said the internal investigation was continuing and total damage had not been calculated.
Timeline events
Cellframe discloses bridge hack and illegal token issuance2026-05
Cellframe described a bridge hack and illegal token issuance, said USDC was moved off older protocols, and described hot/cold bridge hardening while investigation continued.
The official AMA does not provide a complete total-loss figure.
Evidence records
- AMA with Dmitry Gerasimov, May 7, 2026Cellframe · Tier 1 · High reliability · primary · 2026-05-14Claim scope: Incident Case
First-party AMA documenting the bridge hack / illegal token issuance boundary, bridge hardening, partial frozen funds, ongoing investigation, and explicit uncertainty around total damage.
Source tiers describe evidence authority, not certainty for every claim. Tier 1 is the strongest source class; Tier 2 and Tier 3 provide progressively more secondary or supporting context. Source notes define what each record actually supports.
Known unknowns
- Total damage remains unquantified in the reviewed first-party source.
- The complete attack path and final recovery boundary are not established.
Help maintain incident aftermath records
Support recovery, reimbursement, restart, migration, shutdown, evidence, and correction checks.
Report a correction
Report missing evidence, incorrect dates, outcome changes, recovery details, reimbursement status, or broken links. GitHub Issues are preferred for structured review; the Google Form is available if you do not use GitHub.