GLOBALClaimed by VicesocietyFirst sightinglinked via operator-confirmed · 100%
Posted to leak site Jul 19, 2022bd_01d01ec3ed595743
Clustered 4 filings across 3 jurisdictions · filing window Jul 19, 2022 → Dec 20, 2022. View entity profile → Other incidents for this victim →
incident inc_c7ffbed9938d4fbb · 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.
Identity (basic) · Government ID
CA MT
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
May 22, 2022
When the intrusion reportedly occurred, per the linked filings
Jul 19, 2022
Reported by CALIFORNIA AG filing
San Luis Coastal Unified School District (SLCUSD) notified employees and dependents of a cybersecurity incident occurring around May 22, 2022, discovered on July 19, 2022. Unauthorized access resulted in the potential exposure of names, Social Security numbers, and dates of birth. SLCUSD engaged forensic experts, reported the incident to the FBI, and offered complimentary identity monitoring services to affected individuals.
San Luis Coastal Unified School District reported a data breach to the Montana Attorney General. The breach was reported on 2022-09-16. The breach occurred on 7/19/2022. 1 Montana residents were affected.
Affected (this filing): 1
Small neighborhood schools are a hallmark of the District where students are educated from preschool through twelfth grade and a world-class adult school program offers unique, life-improving courses to thousands of community members.
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.