DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
State AGConfirmed10 filings · 10 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 10 filings

Steel River Systems — May 2022 breach

Clustered 10 filings across 10 jurisdictions · filing window Dec 22, 2022 → Dec 27, 2022. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

10 filings

States

10

Affected · reported

219,447

First → last filing

Dec 22, 2022 → Dec 27, 2022

Merge confidence

100%

incident inc_c6d8fa392067418c · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings. Intrusion May 25, 2022–Jul 16, 2022, discovered Jul 16, 2022 — the first regulatory filing landed 159 days later (flagged late). 219,447 individuals reported across the linked filings. Data reported: Government ID, Financial account, PCI, and 2 more. Notifications rolled out on a 5-day schedule across 10 filings beginning Dec 22, 2022. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
159days

Discovered → first regulatory filing

Discovery variance
11days

Range of discovered_at dates across filings

Filing span
5days

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 clocksWashington✗ WA AG >90dCalifornia✗ CA 60-day late · 159dOregon✗ OR AG >45dMaine✗ ME AG >90d · 148dMassachusetts✓ MA credit monitoring dueSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

May 25, 2022breach begins
Jul 16, 2022discovered · members disagree
notification delay · 159 days
Dec 22, 2022first filing
Dec 27, 2022most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

  1. DEC 22MA AGMA AG noticefirst filing · 1,438 MA residentsday 0
  2. DEC 22IN AGIN AG noticestates nationwide total 219,447day 0
  3. DEC 22SC AGSC AG notice2,621 SC residentsday 0
  4. DEC 22WA AGWA AG notice1,368 WA residentsday 0
  5. DEC 22CA AGCA AG noticeno count statedday 0
  6. DEC 22OR AGOR AG noticestates nationwide total 219,447day 0
  7. DEC 22ME AGME AG noticestates nationwide total 219,447day 0
  8. DEC 22MT AGMT AG notice239 MT residentsday 0
  9. DEC 22DE AGDE AG noticeno count statedday 0
  10. DEC 27NH AGNH AG noticemost recent · 552 NH residents+5d
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 25, 2022
IN AG
Discovered
Jul 16, 2022SC AG + WA AG + CA AG +3Jul 27, 2022OR AG + ME AGfilings disagree on discovery
Data types
Financial account · Identity (basic) · Government ID · PCI · PII
MA AG + WA AG + ME AG +5
Attack vector
Unauthorized Access
SC AG

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Count reconciliation

per-state reported counts

Nationwide (stated in a filing)

219,447

Sum of filed state slices

11,734· 5.3% of stated

95% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.

US219,447
IN4,375
SC2,621
MA1,438
WA1,368
ME1,141
NH552
MT239

State AGs report only their own residents; teal bars show each state's reported slice. The gray US row is the nationwide total reported in a linked filing.

Evidence ladder — rungs this incident occupies

Leak-site claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing10 members

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

No SEC filing or victim statement yet.

Merge provenance

Method
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
Audit
Every link edge records its method, confidence and model + prompt versions (100% is the strongest edge).

Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.

Filing velocity

Spread

5 days

Cadence

~1 / 0.6d

vs. multi-state median

1.6× faster

About this clustering

DisclosureLens links filings into incidents through layered matchers: deterministic rules (same source document, multistate filings of one breach, tight-window same-victim pairs), a weighted-similarity scorer for cross-source candidates, and an operator review queue for everything uncertain. Each link records its own method and confidence — shown per filing in the timeline below. The system defaults to NOT merging when uncertain, because a false merge (collapsing two unrelated breaches) is more harmful than a false split (showing related filings separately); uncertain pairs route to human review instead of auto-merging. This page states only what the linked filings agree on; each filing's own account stays on its own record, linked from the timeline below.

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.