DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteState AGConfirmed7 filings · 6 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedlockbit2high sensitivity
Merged incident · 7 filings

Centralia College — January 2022 breach

Clustered 7 filings across 7 jurisdictions · filing window Feb 19, 2022 → Aug 12, 2022. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

7 filings

States

6

Affected · reported

41,068

First → last filing

Feb 19, 2022 → Aug 12, 2022

Merge confidence

100%

incident inc_c143fdd0cc1a4fb5 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 6 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Jan 19, 2022–Feb 14, 2022, discovered Feb 14, 2022 — the first regulatory filing landed 170 days later (flagged late). 41,068 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), PII, and 2 more. Notifications rolled out on a 173-day schedule across 6 filings beginning Feb 19, 2022. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
170days

Discovered → first regulatory filing

Discovery variance
144days

Range of discovered_at dates across filings

Leak precedence
164days 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
173days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksWashington✗ WA AG >90dLeak gap⏱ Leak >90dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jan 19, 2022breach begins
Feb 14, 2022discovered · members disagree
notification delay · 170 days
Aug 3, 2022first filing
Aug 12, 2022most 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 19Leak sitelockbit2 postfirst filing · attacker claim · unverifiedday 0
  2. AUG 3ME AGME AG noticestates nationwide total 41,068+164d
  3. AUG 3MT AGMT AG notice39 MT residents+164d
  4. AUG 3IN AGIN AG noticestates nationwide total 41,068+164d
  5. AUG 3MA AGMA AG notice7 MA residents+164d
  6. AUG 8NH AGNH AG notice6 NH residents+169d
  7. AUG 12WA AGWA AG noticemost recent · 38,418 WA residents+173d
  8. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jan 19, 2022 – Feb 14, 2022
ME AG
Discovered
Feb 14, 2022WA AGJul 8, 2022ME AG + MT AG + NH AGfilings disagree on discovery
Data types
Education · Financial account · Identity (basic) · Government ID · PII
ME AG + MT AG + NH 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)

41,068

Sum of filed state slices

38,482· 93.7% of stated

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

US41,068
WA38,418
MT39
IN11
MA7
NH6
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 claim1 member

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

No press coverage linked yet.

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

173 days

Cadence

~1 / 28.8d

vs. multi-state median

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