GLOBALClaimed by VicesocietyFirst sightinglinked via operator-confirmed · 100%
Posted to leak site Sep 30, 2022bd_d73fcc8603946a6a
Clustered 3 filings across 2 jurisdictions · filing window Sep 30, 2022 → Mar 24, 2023. View entity profile → Other incidents for this victim →
incident inc_e2d2738bea6d4091 · merge_method human · confidence 100%
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 · Health (basic)
CA
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jul 31, 2022 → Sep 3, 2022
When the intrusion reportedly occurred, per the linked filings
Los Angeles Unified School District notified the California Attorney General of a cyberattack involving unauthorized access to its network between July 31, 2022, and September 3, 2022. An unauthorized actor accessed and acquired labor compliance documents, including certified payroll records, containing names, addresses, and Social Security numbers of contractor and subcontractor employees. The district secured systems, notified law enforcement, and is offering identity protection services.
Los Angeles Unified School District experienced a cyberattack involving unauthorized access to its computer systems. An unauthorized actor began digital monitoring as early as July 31, 2022, and attacked the system on September 3, 2022, subsequently posting illegally obtained data to the dark web. The incident affected students, parents, and employees, potentially exposing personal information including names, addresses, Social Security numbers, and medical records. The District secured systems, notified law enforcement, and is offering credit monitoring services.
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.