DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
State AGConfirmed15 filings · 15 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 15 filings

Columbia University — May 2025 breach

Clustered 15 filings across 15 jurisdictions · filing window Aug 1, 2025 → Aug 26, 2025. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

15 filings

States

15

Affected · reported

868,969

First → last filing

Aug 1, 2025 → Aug 26, 2025

Merge confidence

100%

incident inc_e53334f410314f2c · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 15 regulatory filings. The filings describe unauthorized access. Intrusion May 16, 2025–Jun 24, 2025, discovered May 16, 2025 — the first regulatory filing landed 77 days later. 868,969 individuals reported across the linked filings. Data reported: Government ID, Financial account, Health (basic), and 5 more. Notifications rolled out on a 25-day schedule across 15 filings beginning Aug 1, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
77days

Discovered → first regulatory filing

Discovery variance
53days

Range of discovered_at dates across filings

Filing span
25days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksVermont⏱ VT AG >14 bdayMassachusetts✓ MA credit monitoring dueOregon✓ OR AG ≤45dMaine✓ ME AG ≤30d · 30dIowa✓ IA AG ≤5 bdayFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

May 16, 2025breach begins
May 16, 2025discovered · members disagree
notification delay · 77 days
Aug 1, 2025first filing
Aug 26, 2025most 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. AUG 1IL AGIL AG noticefirst filing · no count statedday 0
  2. AUG 7MA AGMA AG notice28,138 MA residents+6d
  3. AUG 7OR AGOR AG noticestates nationwide total 868,969+6d
  4. AUG 7CA AGCA AG noticeno count stated+6d
  5. AUG 7SC AGSC AG noticeno count stated+6d
  6. AUG 7ME AGME AG noticestates nationwide total 868,969+6d
  7. AUG 7WA AGWA AG notice54,075 WA residents+6d
  8. AUG 7IN AGIN AG noticestates nationwide total 868,969+6d
  9. AUG 7NE AGNE AG noticeno count stated+6d
  10. AUG 7DE AGDE AG noticeno count stated+6d
  11. AUG 7MT AGMT AG notice686 MT residents+6d
  12. AUG 7VT AGVT AG noticeno count stated+6d
  13. AUG 8IA AGIA AG notice1,572 IA residents+7d
  14. AUG 12NH AGNH AG notice2,340 NH residents+11d
  15. AUG 26RI AGRI AG noticemost recent · 2,524 RI residents+25d
  16. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 16, 2025 – Jun 24, 2025
OR AG
Discovered
May 16, 2025WA AG + NE AGJun 24, 2025CA AG + SC AG + DE AG +5Jul 8, 2025IL AG + OR AG + ME AGfilings disagree on discovery
Data types
Education · Financial · Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
IL AG + MA AG + CA AG +10
Attack vector
Unauthorized Access
CA 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)

868,969

Sum of filed state slices

95,439· 11.0% of stated

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

US868,969
WA54,075
MA28,138
IN4,078
RI2,524
NH2,340
ME2,026
IA1,572
MT686

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 claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing15 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 Jun 12, 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

25 days

Cadence

~1 / 1.8d

vs. multi-state median

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