DisclosureLens
Leak SiteState AGConfirmed6 records · 4 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedblacksuithigh sensitivity
Merged incident · 6 records

MERS Missouri Goodwill Industries — March 2023 breach

Clustered 6 records across 4 jurisdictions: 5 filings and 1 leak-site claim · filing window May 9, 2024 → May 16, 2024 (dated filings only). View entity profile → Other incidents for this victim →

Determination

Confirmed

Members

6 records

States

4

Affected · reported

70,678

First → last dated filing

May 9, 2024 → May 16, 2024

Merge confidence

100%

incident inc_4222a7edab064b58 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Mar 10, 2023–Mar 15, 2023, discovered Mar 10, 2023. 70,678 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), and PII. Notifications rolled out on a 7-day schedule across 4 dated filings beginning May 9, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
392days

Range of discovered_at dates across filings

Filing span
7days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delay — no SEC 8-K in this cluster.

Regulatory clocksLeak gap✗ Leak >180dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Mar 10, 2023breach begins
Mar 10, 2023discovered · members disagree
May 9, 2024first dated filing
May 16, 2024most recent dated filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident. Filings without a recorded filing day, or recorded as filed before the breach they report began, are not placed on this rail.

Member cascade — every filing and leak-site claim in this incident

  1. MAR 27Leak siteblacksuit postfirst record · attacker claim · unverifiedday 0
  2. MAY 1IL AGIL AG noticefiling day not on record · no count stated—
  3. MAY 9IN AGIN AG noticestates nationwide total 70,678+409d
  4. MAY 16ME AGME AG notice2 affected+416d
  5. MAY 16ME AGME AG notice2 affected+416d
  6. MAY 16MT AGMT AG noticemost recent · 3 MT residents+416d
  7. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Mar 10, 2023
IN AG
Discovered
Mar 10, 2023IL AGMar 15, 2023MT AGApr 5, 2024ME AGfilings disagree on discovery
Data types
Identity (basic) · Government ID · PII
ME AG + MT AG
Attack vector
Unauthorized Access
ME 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)

70,678

Sum of filed state slices

29· 0.0% of stated

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

US70,678
IN24
MT3
ME2

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 claim1 member

Attacker assertion only. Establishes: claim date, group, alleged victim.

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
human
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Oct 22, 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

7 days

Cadence

~1 / 2.3d

vs. multi-state median

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