Clustered 2 filings across 2 jurisdictions · filing window Mar 18, 2015 → Mar 23, 2015. View entity profile → Other incidents for this victim →
incident inc_a17c89973f3f4bad · 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.
Health (basic) · Identity (basic) · Government ID
CA FEDERAL
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Feb 23, 2015 → Feb 26, 2015
When the intrusion reportedly occurred, per the linked filings
Feb 26, 2015
Reported by CALIFORNIA AG filing
Advantage Consolidated LLC reported to HHS on 2015-03-18 a Hacking/IT Incident affecting 151,626 individuals. The breach occurred when user credentials were stolen via malicious software, compromising patient names, addresses, dates of birth, and Social Security numbers. In response, the company enhanced its security measures and updated its risk management plan.
Affected (this filing): 151,626
Advantage Consolidated LLC notified patients that an unauthorized person accessed a dental database between February 23 and February 26, 2015. The company discovered the illegal access on February 26, 2015, after a security review showed abnormal activity. Affected data may include names, addresses, phone numbers, dates of birth, and Social Security numbers. The company engaged law enforcement and offered two years of complimentary identity protection services through Experian.
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.