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

Linn Benton Lincoln Education Service District — December 2024 breach

Clustered 2 filings across 2 jurisdictions · filed Feb 28, 2025. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

2 filings

States

2

Affected · reported

12

First → last filing

Feb 28, 2025

Merge confidence

100%

incident inc_d48feb92274e46b2 · 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, 2 legal records. Intrusion Dec 21, 2024. 12 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

Filing span
0days

Time between earliest and latest filing

Not recorded for this incident

Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.

Sensitive data

identity_government

Incident timeline

Dec 21, 2024breach begins
Feb 28, 2025first filing
—watching for filings

No discovery date is recorded on any filing in this cluster, so the notification delay is not computable. Dashed segments fill in as filings merge.

Member cascade — every filing about this breach

  1. FEB 28MD AGMD AG noticefirst filing · 4 MD residentsday 0
  2. FEB 28MA AGMA AG noticemost recent · 8 MA residentsday 0
  3. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 21, 2024
MD AG
Discovered
—
Data types
Government ID · Identity (basic) · Financial account · Health (basic)
MD AG + MA AG
Response
Began working with third-party specialists to investigate the activity · Notified the Federal Bureau of Investigation · Established a toll-free call center through IDX to answer questions about the incident
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 filing2 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

0 days

vs. multi-state median

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