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

Gelinas & Ward LLP — November 2024 breach

Clustered 6 filings across 4 jurisdictions · filing window Jun 26, 2025 → Aug 8, 2025. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

6 filings

States

4

Affected · reported

not comparable

First → last filing

Jun 26, 2025 → Aug 8, 2025

Merge confidence

100%

incident inc_1ebb73803fcd4033 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 6 regulatory filings. The filings describe unauthorized access. Intrusion Nov 6, 2024, discovered Nov 6, 2024 — the first regulatory filing landed 232 days later (flagged late). Data reported: Government ID, Financial account, PCI, and 1 more. Notifications rolled out on a 43-day schedule across 6 filings beginning Jun 26, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
232days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
43days

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 >90d · 232dVermont✗ VT AG >45 bdayMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Nov 6, 2024breach begins
Nov 6, 2024discovered
notification delay · 232 days
Jun 26, 2025first filing
Aug 8, 2025most 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. JUN 26MA AGMA AG noticefirst filing · 408 MA residentsday 0
  2. JUN 26ME AGME AG notice6 ME residentsday 0
  3. JUN 26VT AGVT AG noticeno count statedday 0
  4. JUN 26NH AGNH AG notice15 NH residentsday 0
  5. JUL 8MA AGMA AG notice408 MA residents+12d
  6. AUG 8NH AGNH AG noticemost recent · 44 NH residents+43d
  7. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Nov 6, 2024
ME AG
Discovered
Nov 6, 2024
ME AG + VT AG + NH AG
Data types
Financial account · Identity (basic) · Government ID · PCI
MA AG + ME AG + VT AG +1
Attack vector
Unauthorized Access
ME 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

MA408
NH44
ME6

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 filing6 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-confirmed · 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

43 days

Cadence

~1 / 8.6d

vs. multi-state median

5.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.