DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteState AGConfirmed13 records · 12 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedcl0phigh sensitivity
Merged incident · 13 records

TRUSTEES OF DARTMOUTH COLLEGE — August 2025 breach

Clustered 13 records across 12 jurisdictions: 12 filings and 1 leak-site claim · filing window Nov 24, 2025 → Nov 25, 2025 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

13 records

States

12

Affected · reported

98,990

First → last dated filing

Nov 24, 2025 → Nov 25, 2025

Merge confidence

100%

incident inc_1563a45fc12c4026 · merged by human · confidence 100%

Part of the ORACLE CORPORATION supply-chain incident (2025) — at least 7 organizations filed notifications naming this third party.
Confirmed breach. Merged as one breach: 12 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Aug 9, 2025–Aug 12, 2025, discovered Aug 12, 2025. 98,990 individuals reported across the linked filings. Data reported: Government ID, Financial account, and Identity (basic). Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
79days

Range of discovered_at dates across filings

Filing span
1days

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 >90dOregon✗ OR AG >45dVermont⏱ VT AG >14 bdayMassachusetts✓ MA credit monitoring dueMaine✓ ME AG ≤30d · 25dTexas✓ TX AG ≤30dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Aug 9, 2025breach begins
Aug 12, 2025discovered · members disagree
Nov 24, 2025first dated filing
Nov 25, 2025most 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

  1. NOV 1IL AGIL AG noticefiling day not on record · no count stated—
  2. NOV 13Leak sitecl0p postfirst record · attacker claim · unverifiedday 0
  3. NOV 24IN AGIN AG notice413 IN residents+10d
  4. NOV 24MT AGMT AG notice193 MT residents+10d
  5. NOV 24WA AGWA AG notice1,496 WA residents+10d
  6. NOV 24MA AGMA AG notice8,533 MA residents+10d
  7. NOV 24NE AGNE AG noticefiling day not on record · 103 NE residents—
  8. NOV 24VT AGVT AG noticeno count stated+10d
  9. NOV 24OR AGOR AG noticestates nationwide total 98,990+10d
  10. NOV 24ME AGME AG notice1,494 ME residents+10d
  11. NOV 24CA AGCA AG noticeno count stated+10d
  12. NOV 24NH AGNH AG notice31,742 NH residents+10d
  13. NOV 25TX AGTX AG noticemost recent · states nationwide total 98,990+11d
  14. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Aug 9, 2025
IN AG
Discovered
Aug 12, 2025WA AG + OR AGOct 30, 2025IL AG + MT AG + NE AG +4filings disagree on discovery
Data types
Financial account · Identity (basic) · Government ID
IL AG + WA AG + MA AG +7
Attack vector
Unauthorized Access
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)

98,990

Sum of filed state slices

45,930· 46.4% of stated

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

US98,990
NH31,742
MA8,533
TX1,956
WA1,496
ME1,494
IN413
MT193
NE103

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 filing12 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 25, 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

1 days

Cadence

~1 / 0.1d

vs. multi-state median

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