DisclosureLens
Leak SiteState AGConfirmed8 filings · 6 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedlockbit_3high sensitivity
Merged incident · 8 filings

Clackamas Community College — January 2024 breach

Clustered 8 filings across 7 jurisdictions · filing window Jan 19, 2024 Apr 3, 2024. View entity profile → Other incidents for this victim →

Determination

Confirmed

Members

8 filings

States

6

Affected · reported

8,797

First → last filing

Jan 19, 2024 Apr 3, 2024

Merge confidence

100%

incident inc_8c40840ecb084d51 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 6 regulatory filings and 2 unverified claims. Intrusion Jan 18, 2024, discovered Jan 19, 2024 — the first regulatory filing landed 73 days later. 8,797 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), and PII. Notifications rolled out on a 75-day schedule across 6 filings beginning Jan 19, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
73days

Discovered → first regulatory filing

Discovery variance
41days

Range of discovered_at dates across filings

Leak precedence
73days 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
75days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delayno SEC 8-K in this cluster.

Regulatory clocksMaine ME AG >30d · 32dLeak gap Leak >30dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jan 18, 2024breach begins
Jan 19, 2024discovered · members disagree
notification delay · 73 days
Apr 1, 2024first filing
Apr 3, 2024most 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. JAN 19Leak sitelockbit_3 postfirst filing · attacker claim · unverifiedday 0
  2. JAN 30Leak sitelockbit_3 postattacker claim · unverified+11d
  3. APR 1MT AGMT AG notice11 MT residents+73d
  4. APR 1ME AGME AG noticestates nationwide total 8,797+73d
  5. APR 1IN AGIN AG noticestates nationwide total 8,797+73d
  6. APR 1NH AGNH AG notice1 NH residents+73d
  7. APR 1OR AGOR AG noticestates nationwide total 8,797+73d
  8. APR 3MA AGMA AG noticemost recent · 6 MA residents+75d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jan 18, 2024
ME AG
Discovered
Jan 19, 2024MT AG + NH AGFeb 29, 2024ME AGfilings disagree on discovery
Data types
Identity (basic) · Government ID · PII
MT AG + ME AG + NH AG +1
Attack vector
Ransomware
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)

8,797

Sum of filed state slices

27· 0.3% of stated

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

US8,797
MT11
IN6
MA6
ME3
NH1

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 claim2 members

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

75 days

Cadence

~1 / 10.7d

vs. multi-state median

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