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

Lewis and Clark Community College — November 2021 breach

Clustered 8 records across 7 jurisdictions: 7 filings and 1 leak-site claim · filing window Apr 15, 2022 → Apr 25, 2022 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

8 records

States

7

Affected · reported

44,769

First → last dated filing

Apr 15, 2022 → Apr 25, 2022

Merge confidence

100%

incident inc_68226b86dfc049c3 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 7 regulatory filings and 1 unverified claim. Intrusion Nov 1, 2021–Nov 30, 2021, discovered Nov 1, 2021. 44,769 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 3 more. Notifications rolled out on a 10-day schedule across 6 dated filings beginning Apr 15, 2022. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Discovery variance
136days

Range of discovered_at dates across filings

Filing span
10days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksLeak gap⏱ Leak >90dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Nov 1, 2021breach begins
Nov 1, 2021discovered · members disagree
Apr 15, 2022first dated filing
Apr 25, 2022most 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 and leak-site claim in this incident

  1. JAN 1IL AGIL AG noticefiling day not on record · no count stated—
  2. JAN 13Leak sitequantum postfirst record · attacker claim · unverifiedday 0
  3. APR 15ME AGME AG noticestates nationwide total 44,769+91d
  4. APR 15IN AGIN AG noticestates nationwide total 44,769+91d
  5. APR 19NH AGNH AG notice2 NH residents+95d
  6. APR 25MT AGMT AG notice3 MT residents+101d
  7. APR 25ID AGID AG notice1 ID residents+101d
  8. APR 25MA AGMA AG noticemost recent · 3 MA residents+101d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Nov 3, 2021 – Nov 23, 2021
ME AG
Discovered
Nov 1, 2021IL AGNov 23, 2021NH AGMar 17, 2022ME AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
ME AG + NH AG + MT AG +2
Attack vector
Unauthorized Access
ME 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)

44,769

Sum of filed state slices

52· 0.1% of stated

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

US44,769
IN42
MT3
MA3
NH2
ME1
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 filing7 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 Oct 23, 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

10 days

Cadence

~1 / 2d

vs. multi-state median

1.7× 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.