All incidents View linkage analytics →Get the evidence package — $7.99 what’s inside →

Confirmed11 records · 9 statesUnverified claimConfirmedEnforcedhivehigh sensitivity

Merged incident · 11 records

Knox College — November 2022 breach

Clustered 11 records across 9 jurisdictions: 10 filings and 1 leak-site claim · filing window Jan 3, 2023 → Jan 5, 2023 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

11 records

States

Affected · reported

63,100

First → last dated filing

Jan 3, 2023 → Jan 5, 2023

Merge confidence

100%

incident inc_5cea768b93c64b56 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings and 1 unverified claim. Intrusion Nov 24, 2022, discovered Nov 24, 2022. 63,100 individuals reported across the linked filings. Data reported: Government ID and Identity (basic). Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Discovery variance

13days

Range of discovered_at dates across filings

Filing span

2days

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 clocksWashington⏱ WA AG >30dMassachusetts✓ MA credit monitoring dueMaine✓ ME AG ≤30d · 29dOregon✓ OR AG ≤45dCalifornia✓ CA 60-day OK · 40dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Nov 24, 2022breach begins

Nov 24, 2022discovered · members disagree

Jan 3, 2023first dated filing

Jan 5, 2023most 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

DEC 10Leak sitehive postfirst record · attacker claim · unverifiedoperator-confirmedday 0
JAN 1IL AGIL AG noticefiling day not on record · no count stated—
JAN 3IN AGIN AG noticestates nationwide total 63,100auto-linked+24d
JAN 4WA AGWA AG notice1,003 WA residentsauto-linked+25d
JAN 4MT AGMT AG notice89 MT residentsauto-linked+25d
JAN 5MA AGMA AG notice395 MA residentsauto-linked+26d
JAN 5ME AGME AG noticestates nationwide total 63,100auto-linked+26d
JAN 5OR AGOR AG noticestates nationwide total 63,100auto-linked+26d
JAN 5NH AGNH AG notice144 NH residentsauto-linked+26d
JAN 5ME AGME AG noticestates nationwide total 63,100auto-linked+26d
JAN 5CA AGCA AG noticemost recent · no count statedauto-linked+26d
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: Nov 24, 2022
Discovered: Nov 24, 2022IL AG + WA AG + MT AG +2Dec 7, 2022ME AG + OR AGfilings disagree on discovery
Data types: Identity (basic) · Government ID
Attack vector: Ransomware

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)

63,100

Sum of filed state slices

2,547· 4.0% of stated

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

US63,100

WA1,003

IN792

MA395

NH144

ME124

MT89

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 filing10 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

2 days

Cadence

~1 / 0.3d

vs. multi-state median

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