Clustered 8 filings across 7 jurisdictions · filing window Apr 10, 2024 → Apr 11, 2025. View entity profile → Other incidents for this victim →
incident inc_cc35db67dcb34887 · merge_method human · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Materiality delta · SEC filing delay — no SEC 8-K in this cluster.
Identity (basic) · Health (basic) · Financial account
CA FEDERAL ME MT OR WA
Leak Site · HHS OCR · State AG
per-filing reported counts
State AGs report only their own residents; bars show per-filing counts.
Earliest sighting first · deep chronology in Litigation Timeline
8 filings across 7 jurisdictions · Apr 10, 2024 – Apr 11, 2025 · 3 milestones
Apr 10, 2024
When the intrusion reportedly occurred, per the linked filings
Young Consulting is the market leader in providing software solutions to the employer stop loss marketplace.
Apr 13, 2024
Reported by WASHINGTON AG, CALIFORNIA AG filings
Young Consulting is the market leader in providing software solutions to the employer stop loss marketplace.
Jun 28, 2024
Reported by OREGON AG, MAINE AG filings
Young Consulting LLC reported a data breach to the Oregon Attorney General. The breach was reported on 2024-08-26. The breach occurred during 4/10/2024 - 4/13/2024. The breach was discovered on 6/28/2024. 954,177 individuals were affected. Notice was sent on 8/26/2024.
Young Consulting LLC reported a data breach to the Montana Attorney General. The breach was reported on 2024-08-26. The breach occurred from 4/10/2024 to 4/13/2024. 1,733 Montana residents were affected.
Affected (this filing): 1,733
The business associate (BA), Young Consulting LLC, reported that it experienced a ransomware attack that affected the protected health information (PHI) of 961,003 individuals. The PHI involved included names, dates of birth, health insurance information, diagnoses, and other treatment information. The BA notified HHS, affected individuals, the media, law enforcement, and published substitute notice on its website. In response to the breach, the BA reviewed and strengthened its policies and procedures, implemented a variety of additional security software protections, hired additional security staff, and required additional training.
Young Consulting LLC, a business sector entity reported a ransomware incident to the Washington Attorney General. The organization became aware of the incident on 2024-04-13 and filed notice on 2024-09-18. 20,732 Washington residents were affected. 158 days elapsed between awareness and notification. 3 days to identify the breach. 0 days to contain the breach.
Affected (this filing): 20,732
Young Consulting LLC, a provider of administrative services to stop-loss insurance carriers, disclosed a data breach where an unauthorized actor accessed its network between April 10-13, 2024, and downloaded files containing names and health information. The incident was discovered on April 13, 2024. Systems were taken offline, a forensic investigation was launched, and law enforcement was notified. The company is offering 12 months of credit monitoring to affected individuals.
Young Consulting LLC (Atlanta, GA) reported an external system breach (hacking) that occurred on April 10, 2024 and was discovered June 28, 2024. The incident exposed name, Social Security number, tax ID number, and health information of approximately 1,020,108 total individuals, including 1,117 Maine residents. Notifications were issued in multiple waves: August 26, 2024, January 28, 2025, and April 11, 2025. Twelve months of credit monitoring via TransUnion was offered.
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): 954,177
Affected (this filing): 961,003
Affected (this filing): 1,117