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

Clackamas Community College — September 2025 breach

Clustered 8 filings across 8 jurisdictions · filing window Oct 29, 2025 → Jan 8, 2026. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

8 filings

States

7

Affected · reported

33,381

First → last filing

Oct 29, 2025 → Jan 8, 2026

Merge confidence

100%

incident inc_84274693227f4676 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 7 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Sep 10, 2025–Oct 30, 2025, discovered Sep 10, 2025 — the first regulatory filing landed 120 days later (flagged late). 33,381 individuals reported across the linked filings. Data reported: Government ID and Identity (basic). Notifications rolled out on a 70-day schedule across 7 filings beginning Oct 29, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
120days

Discovered → first regulatory filing

Discovery variance
99days

Range of discovered_at dates across filings

Leak precedence
70days 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
70days

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 >180dOregon✗ OR AG >45dVermont✗ VT AG >45 bdayMaine✓ ME AG ≤30d · 21dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Sep 10, 2025breach begins
Sep 10, 2025discovered · members disagree
notification delay · 120 days
Jan 8, 2026first filing
—watching for filings

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

  1. OCT 29Leak sitemedusa postfirst filing · attacker claim · unverifiedday 0
  2. JAN 8ME AGME AG noticestates nationwide total 33,381+70d
  3. JAN 8NE AGNE AG noticeno count stated+70d
  4. JAN 8MT AGMT AG notice22 MT residents+70d
  5. JAN 8OR AGOR AG noticestates nationwide total 33,381+70d
  6. JAN 8IN AGIN AG noticestates nationwide total 33,381+70d
  7. JAN 8VT AGVT AG noticeno count stated+70d
  8. JAN 8MA AGMA AG noticemost recent · 9 MA residents+70d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Oct 24, 2025 – Oct 30, 2025
ME AG
Discovered
Sep 10, 2025NE AG + MT AG + VT AGOct 24, 2025OR AGDec 18, 2025ME AGfilings disagree on discovery
Data types
Identity (basic) · Government ID
ME AG + NE 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)

33,381

Sum of filed state slices

41· 0.1% of stated

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

US33,381
MT22
IN9
MA9
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 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
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

70 days

Cadence

~1 / 10d

vs. multi-state median

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