GLOBALClaimed by AvoslockerFirst sightinglinked via operator-confirmed · 100%
Posted to leak site Dec 26, 2022bd_de866ea760ad4477
samples of: Confidential agreements Military personnel (white house service members) related files taxation data
Clustered 3 filings across 3 jurisdictions · filing window Dec 26, 2022 → Jan 26, 2023. View entity profile → Other incidents for this victim →
incident inc_5d4d82e65abd4658 · merge_method human · confidence 100%
Discovered → first regulatory filing
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Materiality delta · SEC filing delay — no SEC 8-K in this cluster; needs two dated filings.
MT VT
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Aug 26, 2022
When the intrusion reportedly occurred, per the linked filings
Aug 27, 2022
Reported by VERMONT AG filing
samples of: Confidential agreements Military personnel (white house service members) related files taxation data
Stratford University notified consumers of a data security incident detected on August 27, 2022. An unauthorized individual accessed systems on August 26, 2022, obtaining personal information from the student database. The university engaged third-party forensic experts and is offering 12 months of credit monitoring and fraud assistance to affected individuals.
Stratford University reported a data breach to the Montana Attorney General. The breach was reported on 2023-01-26. The breach occurred from 8/26/2022 to 11/11/2022. 7 Montana residents were affected.
Affected (this filing):
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.