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

Loren D. Stark Company — October 2022 breach

Clustered 8 filings across 8 jurisdictions · filing window Aug 4, 2023 → Aug 23, 2023. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

8 filings

States

8

Affected · reported

51,659

First → last filing

Aug 4, 2023 → Aug 23, 2023

Merge confidence

100%

incident inc_e480457447074952 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 8 regulatory filings. The filings describe unauthorized access. Intrusion Oct 18, 2022, discovered Oct 18, 2022 — the first regulatory filing landed 290 days later. 51,659 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), and PII. Notifications rolled out on a 19-day schedule across 8 filings beginning Aug 4, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
290days

Discovered → first regulatory filing

Discovery variance
383days

Range of discovered_at dates across filings

Filing span
19days

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

Sensitive data

identity_government

Incident timeline

Oct 18, 2022breach begins
Oct 18, 2022discovered · members disagree
notification delay · 290 days
Aug 4, 2023first filing
Aug 23, 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. AUG 4CA AGCA AG noticefirst filing · no count statedday 0
  2. AUG 4VT AGVT AG noticeno count statedday 0
  3. AUG 4ME AGME AG noticestates nationwide total 51,659day 0
  4. AUG 4IN AGIN AG noticestates nationwide total 51,659day 0
  5. AUG 5MT AGMT AG notice43 MT residents+1d
  6. AUG 11NH AGNH AG notice58 NH residents+7d
  7. AUG 22MA AGMA AG notice188 MA residents+18d
  8. AUG 23SC AGSC AG noticemost recent · 1,522 SC residents+19d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Oct 18, 2022
CA AG
Discovered
Oct 18, 2022MT AG + SC AGJun 16, 2023ME AGNov 5, 2023NH AGfilings disagree on discovery
Data types
Identity (basic) · Government ID · PII
CA AG + VT AG + ME AG +4
Attack vector
Unauthorized Access
CA 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)

51,659

Sum of filed state slices

2,147· 4.2% of stated

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

US51,659
SC1,522
IN274
MA188
ME62
NH58
MT43

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 filing8 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
human
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Jun 12, 2026 · at least one link edge was human-adjudicated
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

19 days

Cadence

~1 / 2.7d

vs. multi-state median

2.4× slower

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.