Clustered 2 filings across 2 jurisdictions · filed Aug 2, 2023. View entity profile → Other incidents for this victim →
incident inc_eeed4e95dfdc4286 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
Identity (basic) · Government ID
CA ME
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
May 31, 2023
When the intrusion reportedly occurred, per the linked filings
Jul 3, 2023
Reported by MAINE AG filing
Serco, Inc. reported a data breach on May 31, 2023, involving unauthorized access to employee personal information via a ransomware attack on a third-party platform. Affected data may include names, SSNs, DOBs, addresses, emails, and health benefit info. No evidence of misuse. NortonLifeLock monitoring provided.
Serco, Inc. reported an external system breach (hacking) occurring on May 31, 2023, discovered on July 3, 2023. The incident affected 10,140 individuals, including 39 Maine residents. Personal information acquired included names and Social Security Numbers. Serco provided written notification on August 1, 2023, and offered one year of complimentary identity theft protection and credit monitoring through NortonLifeLock.
Affected (this filing): 10,140
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.