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

Southern Oregon Educational Services District — December 2024 breach

Clustered 8 filings across 8 jurisdictions · filing window Feb 28, 2025 → Mar 3, 2025 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

8 filings

States

8

Affected · reported

2,982

First → last dated filing

Feb 28, 2025 → Mar 3, 2025

Merge confidence

100%

incident inc_5287655fdeae4400 · merged by deterministic · confidence 100%

Part of the Carruth Compliance Consulting supply-chain incident (2025) — at least 46 organizations filed notifications naming this third party.
Confirmed breach. Merged as one breach: 8 regulatory filings. The filings describe a third-party compromise. Intrusion Dec 21, 2024–Feb 24, 2025, discovered Dec 21, 2024 — the first regulatory filing landed 69 days later. 2,982 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 4 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
69days

Discovered → first regulatory filing

Discovery variance
65days

Range of discovered_at dates across filings

Filing span
3days

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 bdayMaine⏱ ME AG >30d · 47dOregon✓ OR AG ≤45dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

financial_credentialsidentity_government

Incident timeline

Dec 21, 2024breach begins
Dec 21, 2024discovered · members disagree
notification delay · 69 days
Feb 28, 2025first dated filing
Mar 3, 2025most 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 about this breach

  1. FEB 28IN AGIN AG noticefirst filing · states nationwide total 2,982day 0
  2. FEB 28MT AGMT AG notice1 MT residentsday 0
  3. FEB 28NE AGNE AG noticefiling day not on record · no count stated—
  4. FEB 28VT AGVT AG noticeno count statedday 0
  5. MAR 1OR AGOR AG noticestates nationwide total 2,982+1d
  6. MAR 1MA AGMA AG notice2 MA residents+1d
  7. MAR 1ME AGME AG noticestates nationwide total 2,982+1d
  8. MAR 3NH AGNH AG noticemost recent · no count stated+3d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 21, 2024
IN AG
Discovered
Dec 21, 2024MT AG + VT AGJan 13, 2025ME AG + NH AGFeb 24, 2025NE AG + OR AGfilings disagree on discovery
Data types
Employment · Financial account · Financial credentials · Health (basic) · Identity (basic) · Government ID · PII
MT AG + VT AG + ME AG +2
Attack vector
Third-Party / Supply Chain
MT 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)

2,982

Sum of filed state slices

5· 0.2% of stated

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

US2,982
MA2
IN1
MT1
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 claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing8 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 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

3 days

Cadence

~1 / 0.5d

vs. multi-state median

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