State AGConfirmed4 filings · 4 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedmoderate sensitivity
Merged incident · 4 filings
2nd Swing — March 2026 breach
Clustered 4 filings across 4 jurisdictions · filed May 7, 2026. View entity profile → Other incidents for this victim →
⚠ 1 cross-filing discrepancy →Merge100%
incident inc_8fe87f71bdb14af4 · merged by deterministic · confidence 100%
Confirmed breach. Merged as one breach: 4 regulatory filings. The filings describe unauthorized access. Intrusion Mar 20, 2026–Mar 31, 2026, discovered Mar 31, 2026 — the first regulatory filing landed 37 days later. 222 individuals reported across the linked filings. Data reported: Identity (basic), PCI, and Financial account. Each member filing remains the legal record for its jurisdiction.
Litigation Timing
Notification delay
37days
Discovered → first regulatory filing
Discovery variance
0days
Range of discovered_at dates across filings
Filing span
0days
Time between earliest and latest filing
Not recorded for this incident
Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.
Regulatory clocksMaine⏱ ME AG >30d · 37dMassachusetts⏱ MA AG >30dFull clock table in Litigation Timeline
The weekly clock on records like this one
The Disclosure Clock is a weekly briefing on what landed in the disclosure record, and the gap between the criminals' post and the regulator's filing — measured on the whole record, with the method shown.
Weekly. Double opt-in, one-click unsubscribe, and the address goes nowhere else.