Clustered 2 filings across 2 jurisdictions · filing window Jul 25, 2023 → Jul 26, 2023. View entity profile → Other incidents for this victim →
incident inc_1578b68f36ec4d64 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Identity (basic) · Government ID
Time between earliest and latest filing
Not recorded for this incident
Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.
ME VT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jan 24, 2023 → Mar 1, 2023
When the intrusion reportedly occurred, per the linked filings
Mar 1, 2023
Reported by VERMONT AG filing
May 23, 2023
Reported by MAINE AG filing
BASIS Educational Group, LLC notified consumers of a cyber incident identified around March 1, 2023, involving unauthorized copying of files containing names and Social Security numbers. The company launched an investigation, assessed system security, and offered complimentary Experian identity monitoring services. The incident is currently contained.
BASIS Educational Group, LLC reported a data breach to the Maine Attorney General, indicating that an external system breach (hacking) occurred between January 24, 2023, and March 1, 2023. The breach was discovered on May 23, 2023. One Maine resident was affected, and their name and Social Security number were compromised. The company provided written notification to the affected individual on July 25, 2023, and offered 12 months of credit monitoring and identity restoration services through Experian.
Affected (this filing): 1
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.