Cybersecurity incident affects USDR token operations — Stablecoin Event

Connected records

Affected records

Assets and organizations connected to this event.

Sources

Sources used for this record, with archival copies where available.

1 source identity · 1 evidence relation
Source	Publisher and date	Relevance	Archive
StablR Discloses Cybersecurity Incident Affecting USDR and EURR Token Operations Source details Source category Official statement or announcement Provenance Subject-controlled source Primary or secondary Primary source Reliability High	StablR Published 2026-05-25	Security Incident, Unauthorized Issuance, Minting Suspension, Redemption Suspension, Backing Impairment, May 24 Unauthorized Access Issuance and Immediate Mint Redeem Suspension	Archive index or wildcard

Official statement or announcement

High

Publisher: StablR
Published: 2026-05-25
Provenance: Subject-controlled source
Primary or secondary: Primary source
Supported claims: Security Incident, Unauthorized Issuance, Minting Suspension, Redemption Suspension, Backing Impairment, May 24 Unauthorized Access Issuance and Immediate Mint Redeem Suspension
Archive: Archive index or wildcard
Reliability: High

Record details
Classification, review, and event-specific data

Record ID: sog_ev_usdr_incident_batch_v
Severity: Critical
Event type: Security Incident
Public category: Security and chain incident
Lifecycle effect: Restricted or impaired
Recovery or reversal: Not applicable
Recovery date: Not yet recorded
Cause or mechanism: Unauthorized external access affected token operations and led StablR to suspend minting and redemption. The initial disclosure stated that circulating EURR and USDR supply was not fully backed at the required 1:1 ratio after the incident.
Structured detail kind: Security Incident
Record confidence: High
Evidence relations: 1

Summary: Unauthorized external access affected token operations and led StablR to suspend minting and redemption. The initial disclosure stated that circulating EURR and USDR supply was not fully backed at the required 1:1 ratio after the incident.
Status: Contained Recovery Ongoing
Loss or exposure: Unknown after review
Resolution date: Not yet recorded
Affected deployments: sog_dep_usdr_ethereum_batch_v, sog_dep_usdr_plasma_batch_v, sog_dep_usdr_concordium_batch_v
Related organizations: sog_issuer_stablr

Maintenance

Use the documented correction path and methodology.