The University of Vermont — April 2019 breach
One linked filing — more sources may join as they report · filed Jul 29, 2019. View entity profile → Other incidents for this victim →
incident inc_ee0d0aa2d4154ce9 · merged by deterministic
Litigation Timing
Discovered → first regulatory filing
Not recorded for this incident
Discovery variance · Leak precedence · Materiality delta · SEC filing delay · Filing span — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
Incident timeline
Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.
Member cascade — every filing about this breach
- JUL 29NH AGNH AG noticeonly filing · states nationwide total 670day 0
- Watching for additional filings — new sources merge into this incident automatically.
Roll-up facts — reconciled across members
- Breach window
- Apr 13, 2019 – Apr 26, 2019 NH AG
- Discovered
- May 3, 2019· 20d undetected NH AG
- Data types
- Financial account · Identity (basic) NH AG
- Attack vector
- Third-Party / Supply Chain NH AG
- Response
- Engaged a leading IT forensic firm to assist in its comprehensive investigation · Provided notice to appropriate entities as required under applicable state laws · Sent individual notice to affected individuals NH 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)
670
Sum of filed state slices
27· 4.0% of stated
96% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.
Evidence ladder — rungs this incident occupies
No leak-site claim on record for this incident.
No press coverage linked yet.
Unlocks: discovery date, data types, affected count, compliance clock.
No SEC filing or victim statement yet.
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.