Clustered 4 filings across 3 jurisdictions · filing window May 24, 2024 → May 31, 2024. View entity profile → Other incidents for this victim →
incident inc_cb8bf9f551ce4499 · 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.
MT PA VT
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Apr 3, 2024
When the intrusion reportedly occurred, per the linked filings
Apr 3, 2024
Reported by VERMONT AG filing
AmerisourceBergen Specialty Group, LLC reported to HHS on 2024-05-24 a Hacking/IT Incident affecting 252214 individuals. Breached information located on Network Server.
Affected (this filing): 252,214
AmerisourceBergen Specialty Group, LLC - The Lash Group reported a data breach to the Montana Attorney General. The breach was reported on 2024-05-31. The breach occurred on 4/3/2024. 8 Montana residents were affected.
Affected (this filing): 8
AmerisourceBergen Specialty Group, LLC notified consumers of a data security incident where data was exfiltrated from its information systems. The incident, confirmed on April 3, 2024, potentially exposed personal information including names, health insurance/Medicare/Medicaid numbers, treatment/prescription info, and dates of birth. ABSG engaged law enforcement and cybersecurity experts, reinforced security protocols, and offered 24 months of credit monitoring via Experian IdentityWorks.
AmerisourceBergen Specialty Group, LLC reported to HHS on 2024-05-31 a Hacking/IT Incident affecting 3102 individuals. Breached information located on Network Server.
Affected (this filing): 3,102
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.