Clustered 2 filings across 1 jurisdiction · filing window Jun 9, 2023 → Jul 10, 2023. View entity profile → Other incidents for this victim →
incident inc_7cc1b7c48b314eec · merge_method deterministic · confidence 90%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Identity (basic) · Government ID · Financial account
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.
DE
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Mar 20, 2023 → Mar 27, 2023
When the intrusion reportedly occurred, per the linked filings
Mar 27, 2023
Reported by DELAWARE AG filings
Onix Group LLC experienced a ransomware incident in March 2023 affecting internal systems. An unauthorized actor accessed the network between March 20 and March 27, 2023, using valid credentials, corrupted systems, and exfiltrated HR and payroll files containing names, SSNs, and financial account data. Onix engaged cybersecurity experts, secured systems, and offered one year of Experian IdentityWorks to affected individuals.
Onix Group, LLC reported a ransomware incident affecting internal systems between March 20 and March 27, 2023. Unauthorized access resulted in system corruption and file removal. Affected employee data included names, Social Security numbers, and financial account information. Onix engaged cybersecurity experts, secured systems, and offered one year of Experian IdentityWorks 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.