All incidents View linkage analytics →Get the evidence package — $79 what’s inside →

Confirmed5 filings · 4 statesUnverified claimConfirmedEnforcedbianlianhigh sensitivity

Merged incident · 5 filings

Growers Express — September 2023 breach

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

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

5 filings

States

Affected · reported

1,775

First → last filing

Nov 5, 2023 → Nov 21, 2023

Merge confidence

100%

incident inc_99f84011b71c4784 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 4 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Sep 20, 2023, discovered Oct 9, 2023 — the first regulatory filing landed 27 days later. 1,775 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 2 more. Notifications rolled out on a 16-day schedule across 4 filings beginning Nov 5, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Notification delay

27days

Discovered → first regulatory filing

Discovery variance

0days

Range of discovered_at dates across filings

Leak precedence

Noneclaim trailed by 16d

Days between the first leak-site claim and the first regulatory filing. Positive = the claim came first (public exposure before disclosure). Negative = the claim trailed the filing, so there was no pre-disclosure leak. Counts regulatory filings only — press coverage is not a regulatory disclosure.

Filing span

16days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksMassachusetts✓ MA credit monitoring dueMaine✓ ME AG ≤30d · 27dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Sep 20, 2023breach begins

Oct 9, 2023discovered

notification delay · 27 days

Nov 5, 2023first filing

—watching for filings

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

Member cascade — every filing about this breach

NOV 5CA AGCA AG noticefirst filing · no count statedauto-linkedday 0
NOV 5MA AGMA AG notice1 MA residentsauto-linkedday 0
NOV 5MT AGMT AG notice2 MT residentsoperator-confirmedday 0
NOV 5ME AGME AG noticestates nationwide total 1,775operator-confirmedday 0
NOV 21Leak sitebianlian postmost recent · attacker claim · unverified+16d
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: Sep 20, 2023
Discovered: Oct 9, 2023· 19d undetected
Data types: Employment · Financial account · Identity (basic) · Government ID · PII
Attack vector: Unauthorized Access

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)

1,775

Sum of filed state slices

4· 0.2% of stated

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

US1,775

MT2

MA1

ME1

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 filing4 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
Reviewed: operator-reviewed Jun 6, 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

16 days

Cadence

~1 / 4d

vs. multi-state median

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