DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
HHS OCRState AGConfirmed37 filings · 16 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 37 filings

CONDUENT BUSINESS SERVICES, LLC — October 2024 breach

Clustered 37 filings across 16 jurisdictions · filing window Jan 22, 2025 → Apr 27, 2026. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

37 filings

States

16

Affected · reported

62,224,658

First → last filing

Jan 22, 2025 → Apr 27, 2026

Merge confidence

100%

incident inc_47b17bf6229842b6 · merged by human · confidence 100%

Part of the CONDUENT BUSINESS SERVICES, LLC supply-chain incident (2025) — at least 4 organizations filed notifications naming this third party.
Confirmed breach. Merged as one breach: 37 regulatory filings. Intrusion Oct 21, 2024–Jan 13, 2025, discovered Jan 13, 2025 — the first regulatory filing landed 9 days later (flagged late). 62,224,658 individuals reported across the linked filings. Data reported: Government ID, Health (basic), Identity (basic), and 2 more. Notifications rolled out on a 460-day schedule across 37 filings beginning Jan 22, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
9days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
460days

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.

Regulatory clocksVermont✗ VT AG >45 bdayWashington✗ WA AG >90dOregon✗ OR AG >45dMaine✗ ME AG >90d · 284dHIPAA✓ HHS notifiedIowa✓ IA AG ≤5 bdayMassachusetts✓ MA credit monitoring dueSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Oct 21, 2024breach begins
Jan 13, 2025discovered
notification delay · 9 days
Jan 22, 2025first filing
Apr 27, 2026most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

  1. JAN 22WI AGWI AG noticefirst filing · 25 affectedday 0
  2. OCT 1IL AGIL AG noticeno count stated+252d
  3. OCT 8NH AGNH AG notice1 NH residents+259d
  4. OCT 8CA AGCA AG noticeno count stated+259d
  5. OCT 8MT AGMT AG notice358,882 MT residents+259d
  6. OCT 8HHS OCRHHS OCR noticestates nationwide total 62,224,658+259d
  7. OCT 24NH AGNH AG notice10,879 NH residents+275d
  8. OCT 24VT AGVT AG noticeno count stated+275d
  9. OCT 24IN AGIN AG notice5,892 IN residents+275d
  10. OCT 24WA AGWA AG notice786,927 WA residents+275d
  11. OCT 24OR AGOR AG noticestates nationwide total 10,515,849+275d
  12. OCT 24DE AGDE AG noticeno count stated+275d
  13. OCT 24NE AGNE AG noticeno count stated+275d
  14. OCT 24ME AGME AG notice374 ME residents+275d
  15. OCT 24IA AGIA AG notice643 IA residents+275d
  16. OCT 24CA AGCA AG noticeno count stated+275d
  17. OCT 25MA AGMA AG notice251,734 MA residents+276d
  18. OCT 25SC AGSC AG notice664,064 SC residents+276d
  19. OCT 31CA AGCA AG noticeno count stated+282d
  20. NOV 19NH AGNH AG notice915 NH residents+301d
  21. NOV 19CA AGCA AG noticeno count stated+301d
  22. DEC 18CA AGCA AG noticeno count stated+330d
  23. DEC 18NH AGNH AG notice44,010 NH residents+330d
  24. JAN 2NH AGNH AG notice12,666 NH residents+345d
  25. JAN 2CA AGCA AG noticeno count stated+345d
  26. JAN 2VT AGVT AG noticeno count stated+345d
  27. JAN 30CA AGCA AG noticeno count stated+373d
  28. JAN 30ME AGME AG noticestates nationwide total 5,875+373d
  29. FEB 2NH AGNH AG notice112,952 NH residents+376d
  30. FEB 2VT AGVT AG noticeno count stated+376d
  31. FEB 5VT AGVT AG noticeno count stated+379d
  32. FEB 9ME AGME AG noticestates nationwide total 16,991+383d
  33. MAR 24CA AGCA AG noticeno count stated+426d
  34. MAR 24NH AGNH AG notice112,325 NH residents+426d
  35. MAR 24VT AGVT AG noticeno count stated+426d
  36. APR 27NH AGNH AG notice4 NH residents+460d
  37. APR 27CA AGCA AG noticemost recent · no count stated+460d
  38. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Oct 21, 2024
WI AG
Discovered
Jan 13, 2025· 84d undetected
IL AG + NH AG + CA AG +9
Data types
Health (basic) · Identity (basic) · Government ID · PHI · PII
WI AG + IL AG + NH AG +11
Attack vector
Unauthorized Access
NH 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)

62,224,658

Sum of filed state slices

2,181,493· 3.5% of stated

96% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.

US62,224,658
WA786,927
SC664,064
MT358,882
MA251,734
NH112,952
IN5,892
IA643
ME374
WI25

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

Leak-site claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing37 members

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

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 26, 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

460 days

Cadence

~1 / 12.8d

vs. multi-state median

57.5× 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.