Incident case

Commons Bridge 2026 proxy compromise

The Commons Bridge proxy on Base was compromised and approximately 18.45 million SYND were drained or controlled through the affected path. Public reporting placed realized sale proceeds around USD 330,000–400,000. Commons was later wound down and all users were automatically reimbursed with their SYND plus an additional 15 percent.

reviewedcurrent

Incident facts

Incident title
Commons Bridge 2026 proxy compromise
Bridge
Commons Bridge
Incident date
2026-04-29
Incident type
Exploit
Major incident
Yes
Affected chains
Base, Commons Chain, Ethereum
Affected assets
SYND
Attack category
Unknown
Reported loss
Approximately USD 330,000–400,000 realized proceeds
Amount confidence
Medium
Loss amount basis
Mixed Sources
Recovery
None
Reimbursement
Completed
Restart
Not Reopened
Current outcome
Dead After Incident
Postmortem
Unclear
Resolution
Final outcome known
Last reviewed
2026-07-28
Last verified
2026-07-28

Amount and valuation

Approximately 18.45 million SYND were reported drained or controlled through the compromised bridge proxy and sold for roughly USD 330,000–400,000.

Token quantity, realized attacker proceeds, user loss, market-price impact, and treasury-funded reimbursement measure different scopes and remain separate.

Timeline events

  • Commons Bridge proxy compromised2026-04-29

    The Commons Bridge proxy on Base was compromised, enabling unauthorized control or removal of approximately 18.45 million SYND.

    Exploit OccurredHigh
  • Syndicate disclosed Commons Bridge compromise2026-04-29

    Syndicate disclosed the bridge compromise, began tracing the attacker, and advised users not to provide liquidity during response.

    Hack DisclosedHigh
  • Commons Bridge operations paused2026-04-29

    Commons Bridge operation and related liquidity activity were paused during containment and investigation.

    Bridge PausedHigh
  • Syndicate began tracing and security investigation2026-04-29

    Syndicate engaged security firms and began tracing attacker activity while assessing reserves and affected users.

    OtherHigh
  • Syndicate committed reserves for affected users2026-04-29

    Syndicate stated that sufficient SYND reserves were available to help affected users while the incident response continued.

    Reimbursement AnnouncedHigh
  • Commons users automatically reimbursed2026-05-21

    The official shutdown page states that every SYND balance on Commons, including staked SYND and unclaimed rewards, was returned to the corresponding Base wallet plus an additional 15 percent.

    Reimbursement CompletedHigh
  • Commons network and bridge wind-down announced2026-05-21

    Syndicate announced the Commons wind-down alongside the Labs lifecycle update and reimbursement outcome.

    Shutdown AnnouncedHigh

    The operator stated that the bridge compromise did not cause the separate Labs wind-down decision.

  • Commons Bridge permanently shut down2026-05-21

    The official Commons page states that Commons has shut down and no user claim action is required.

    Shutdown EffectiveHigh

Evidence records

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

Independent incident archive

Help maintain incident aftermath records

Support recovery, reimbursement, restart, migration, shutdown, evidence, and correction checks.

Support BIR
Record maintenance

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.