Confirmed breach. Intrusion Aug 9, 2025–Aug 20, 2025, discovered Sep 29, 2025 — the first regulatory filing landed 130 days later (flagged late). 1,897 individuals reported across the linked filings.
Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
Regulatory clocksVermont✗ VT AG >45 bdayFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforced
Affected (total reported)
1,897
Data types
—
Jurisdictions
2
IN VT
Linked filings
2
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Aug 9, 2025
When the intrusion reportedly occurred, per the linked filings
President and Fellows of Harvard College reported a data breach to the Indiana Attorney General. The breach occurred on 2025-08-09 and was reported on 2026-02-06. 5 Indiana residents were affected. 1,897 individuals affected in total.
Affected (this filing): 1,897
🍁Vermont State AGMost recentlinked via multistate filing link · 100%
Harvard College notified Vermont AG of a data breach where a third party exploited a vulnerability in Oracle E-Business Suite to access personal information (names, government IDs) of individuals between Aug 9-20, 2025. Incident discovered Sept 29, 2025. Harvard engaged forensic experts, isolated systems, applied patches, and offered 24 months of credit monitoring.
VT AG >45 bday
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. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.