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

Upstream RollCo, LLC — January 2023 breach

Clustered 5 filings across 5 jurisdictions · filing window Sep 15, 2023 → Sep 18, 2023. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

5 filings

States

5

Affected · reported

35,605

First → last filing

Sep 15, 2023 → Sep 18, 2023

Merge confidence

100%

incident inc_ec0c32f42a2a4c41 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings. Intrusion Jan 24, 2023–Feb 9, 2023, discovered Jan 24, 2023 — the first regulatory filing landed 234 days later (flagged late). 35,605 individuals reported across the linked filings. Data reported: Government ID, PII, Identity (basic), and 3 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
234days

Discovered → first regulatory filing

Discovery variance
16days

Range of discovered_at dates across filings

Filing span
3days

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 >90dMassachusetts✓ MA credit monitoring dueSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jan 24, 2023breach begins
Jan 24, 2023discovered · members disagree
notification delay · 234 days
Sep 15, 2023first filing
Sep 18, 2023most 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. SEP 15MA AGMA AG noticefirst filing · 4 MA residentsday 0
  2. SEP 15MT AGMT AG notice59 MT residentsday 0
  3. SEP 15CA AGCA AG noticeno count statedday 0
  4. SEP 15WA AGWA AG notice14,247 WA residentsday 0
  5. SEP 18SC AGSC AG noticemost recent · 21,295 SC residents+3d
  6. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jan 24, 2023 – Feb 9, 2023
MT AG
Discovered
Jan 24, 2023MT AG + SC AGFeb 9, 2023WA AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
MA AG + WA AG + MT AG +2
Attack vector
Phishing
MT AG

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

Affected residents by state

per-state reported counts

SC21,295
WA14,247
MT59
MA4

State AGs report only their own residents; teal bars show each state's reported slice.

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 filing5 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

3 days

Cadence

~1 / 0.8d

vs. multi-state median

2.0× 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.