DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SiteState AGConfirmed9 filings · 8 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedvicesocietyhigh sensitivity
Merged incident · 9 filings

Lewis & Clark College — February 2023 breach

Clustered 9 filings across 9 jurisdictions · filing window Mar 31, 2023 → Feb 12, 2026. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

9 filings

States

8

Affected · reported

48,799

First → last filing

Mar 31, 2023 → Feb 12, 2026

Merge confidence

100%

incident inc_3fa036ecd287463e · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 8 regulatory filings and 1 unverified claim. Intrusion Feb 28, 2023, discovered Mar 3, 2023 — the first regulatory filing landed 385 days later (flagged late). 48,799 individuals reported across the linked filings. Data reported: Government ID, Education, Financial account, and 4 more. Notifications rolled out on a 1048-day schedule across 8 filings beginning Mar 31, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
385days

Discovered → first regulatory filing

Discovery variance
358days

Range of discovered_at dates across filings

Leak precedence
356days before filing

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
1048days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksLeak gap✗ Leak >180dCalifornia✗ CA 60-day late · 385dOregon✗ OR AG >45dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Feb 28, 2023breach begins
Mar 3, 2023discovered · members disagree
notification delay · 385 days
Mar 22, 2024first filing
Feb 12, 2026most 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. MAR 31Leak sitevicesociety postfirst filing · attacker claim · unverifiedday 0
  2. MAR 22WA AGWA AG notice9,725 WA residents+357d
  3. MAR 22ME AGME AG notice110 affected+357d
  4. MAR 22MT AGMT AG notice227 MT residents+357d
  5. MAR 22IN AGIN AG noticestates nationwide total 48,799+357d
  6. MAR 22VT AGVT AG noticeno count stated+357d
  7. MAR 22CA AGCA AG noticeno count stated+357d
  8. APR 10OR AGOR AG noticeno count stated+376d
  9. FEB 12ID AGID AG noticemost recent · 1 affected+1049d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 28, 2023
WA AG
Discovered
Mar 3, 2023WA AG + CA AGFeb 24, 2024ME AG + OR AGfilings disagree on discovery
Data types
Education · Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
WA AG + ME AG + MT AG +3
Attack vector
Ransomware
WA 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)

48,799

Sum of filed state slices

10,154· 20.8% of stated

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

US48,799
WA9,725
MT227
ME110
IN91
ID1

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 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
human
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Aug 9, 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

1048 days

Cadence

~1 / 131d

vs. multi-state median

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