Young Consulting — April 2024 breach
Clustered 23 records across 14 jurisdictions: 21 filings, 1 press report and 1 leak-site claim · filing window Aug 26, 2024 → Jul 3, 2025 (dated filings only). View entity profile → Other incidents for this victim →
incident inc_cc35db67dcb34887 · merged by human · confidence 100%
Litigation Timing
SupplementalRange of discovered_at dates across filings
Time between earliest and latest filing
Not recorded for this incident
Leak precedence · Materiality delta · SEC filing delay — no SEC 8-K in this cluster.
Sensitive data
identity_governmentIncident timeline
Dashed segments are unestablished, not zero — they fill in as filings merge into this incident. Filings without a recorded filing day, or recorded as filed before the breach they report began, are not placed on this rail.
Member cascade — every filing and leak-site claim in this incident
- APR 10Leak siteblacksuit postfirst record · attacker claim · unverifiedoperator-confirmedday 0
- AUG 1IL AGIL AG noticefiling day not on record · no count statedoperator-confirmed—
- AUG 26CA AGCA AG noticeno count statedoperator-confirmed+138d
- AUG 26MT AGMT AG notice1,733 MT residentsoperator-confirmed+138d
- AUG 26NH AGNH AG notice1,839 NH residentsoperator-confirmed+138d
- AUG 26OR AGOR AG noticestates nationwide total 954,177operator-confirmed+138d
- AUG 26ME AGME AG noticestates nationwide total 954,177operator-confirmed+138d
- AUG 27SC AGSC AG notice4,895 SC residentsauto-linked+139d
- AUG 27MA AGMA AG notice8,527 MA residentsoperator-confirmed+139d
- AUG 27VT AGVT AG noticeno count statedoperator-confirmed+139d
- SEP 11HHS OCRHHS OCR noticestates nationwide total 961,003operator-confirmed+154d
- SEP 18WA AGWA AG noticestates nationwide total 20,732+161d
- JAN 25IN AGIN AG noticestates nationwide total 16,612operator-confirmed+290d
- JAN 29MD AGMD AG notice120 MD residentsoperator-confirmed+294d
- JAN 29CA AGCA AG noticeno count statedoperator-confirmed+294d
- APR 11CA AGCA AG noticeno count statedoperator-confirmed+366d
- APR 11NH AGNH AG notice22 NH residentsoperator-confirmed+366d
- APR 11ME AGME AG noticestates nationwide total 1,020,108auto-linked+366d
- JUL 2NH AGNH AG notice28 NH residentsoperator-confirmed+448d
- JUL 2ME AGME AG noticestates nationwide total 1,071,336operator-confirmed+448d
- JUL 2CA AGCA AG noticeno count statedoperator-confirmed+448d
- JUL 3TX AGTX AG noticemost recent · states nationwide total 1,071,336operator-confirmed+449d
- Watching for additional filings — new sources merge into this incident automatically.
Roll-up facts — reconciled across members
- Breach window
- Apr 10, 2024 – Apr 13, 2024 CA AG
- Discovered
- Apr 10, 2024IL AGApr 13, 2024MT AG + NH AG + ME AG +5Jun 28, 2024OR AG + ME AG + TX AGAug 26, 2024NH AGfilings disagree on discovery
- Data types
- Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII IL AG + ME AG + MA AG +9
- Attack vector
- Unauthorized Access MT AG
Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.
Count reconciliation
per-state reported counts
Nationwide (stated in a filing)
1,071,336
Sum of filed state slices
86,182· 8.0% of stated
92% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.
State AGs report only their own residents; teal bars show each state's reported slice. The gray US row is the nationwide total reported in a linked filing.
Evidence ladder — rungs this incident occupies
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
No SEC filing or victim statement yet.
Merge provenance
- Method
- human
- Confidence
- 1.00 · above the 0.85 auto-merge floor
- Reviewed
- operator-reviewed Aug 25, 2026 · at least one link edge was human-adjudicated
- Audit
- Every link edge records its method, confidence and model + prompt versions (100% is the strongest edge).
Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.
Filing velocity
Spread
311 days
Cadence
~1 / 16.4d
vs. multi-state median
62.2× slower
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. This page states only what the linked filings agree on; each filing's own account stays on its own record, linked from the timeline below.
The weekly clock on records like this one
The Disclosure Clock is a weekly briefing on what landed in the disclosure record, and the gap between the criminals' post and the regulator's filing — measured on the whole record, with the method shown.
Weekly. Double opt-in, one-click unsubscribe, and the address goes nowhere else.