DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79
State AGConfirmed3 filings · 2 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 3 filings

Lane ESD — December 2024 breach

Clustered 3 filings across 2 jurisdictions · filing window Feb 28, 2025 → Mar 1, 2025. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

3 filings

States

2

Affected · reported

1

First → last filing

Feb 28, 2025 → Mar 1, 2025

Merge confidence

100%

incident inc_9958d98af33a4631 · merged by deterministic · confidence 100%

Part of the Carruth Compliance Consulting supply-chain incident (2025) — at least 59 organizations filed notifications naming this third party.
Confirmed breach. One breach, 3 legal records. Intrusion Dec 21, 2024, discovered Dec 21, 2024 — the first regulatory filing landed 69 days later. 1 individuals reported across the linked filings. This page is the deduped roll-up; each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
69days

Discovered → first regulatory filing

Discovery variance
23days

Range of discovered_at dates across filings

Filing span
1days

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 clocksVermont⏱ VT AG >14 bdayMaryland⏱ MD AG >30dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Dec 21, 2024breach begins
Dec 21, 2024discovered · members disagree
notification delay · 69 days
Feb 28, 2025first filing
Mar 1, 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. FEB 28VT AGVT AG noticefirst filing · no count statedday 0
  2. FEB 28VT AGVT AG noticeno count statedday 0
  3. MAR 1MD AGMD AG noticemost recent · 1 MD residents+1d
  4. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 21, 2024
VT AG
Discovered
Dec 21, 2024VT AGJan 13, 2025MD AGfilings disagree on discovery
Data types
Identity (basic) · Government ID · Financial account · Employment · PHI
VT AG + MD AG
Attack vector
Third-Party / Supply Chain
MD AG
Response
Began an investigation to determine what happened and what data was involved · Working with third-party specialists to investigate the activity · Notified the Federal Bureau of Investigation
MD AG

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

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

1 days

Cadence

~1 / 0.5d

vs. multi-state median

5.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. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.