Corban OneSource, USA - maximize risks to compliance. Company provides comprehensive HR outsourcing services, including payroll administration, employee benefits management, and HR support, aimed at reducing risks and improving organizational ...
Clustered 2 filings across 2 jurisdictions · filing window Oct 3, 2025 → Feb 4, 2026. View entity profile → Other incidents for this victim →
incident inc_84585f6f44d54b36 · 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.
PII · Government ID
ME
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Sep 9, 2025
When the intrusion reportedly occurred, per the linked filings
Corban OneSource, USA - maximize risks to compliance. Company provides comprehensive HR outsourcing services, including payroll administration, employee benefits management, and HR support, aimed at reducing risks and improving organizational ...
Jan 12, 2026
Reported by MAINE AG filing
On September 9, 2025, Corban OneSource, LLC identified unauthorized access to certain systems within their network. A file containing names and Social Security numbers of 2 Maine residents (employees, customers, or vendors) was accessed without authorization. Discovery was confirmed January 12, 2026. Written notifications were sent February 4, 2026. One-year Epiq credit monitoring was offered to affected individuals.
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.
Affected (this filing): 2