Conduent Data Breach Settlement: the $80M Fund, the $3,500 Claims and the Court Dates That Matter

Key Takeaway

• 📜 The Conduent data breach settlement is signed but the claims process is not open: the settlement agreement was signed and filed October 16, 2026 in the US District Court for the District of New Jersey (Exhibit 10.1 to Conduent’s Form 8-K), and it awaits preliminary approval — there is no claim form, no payment date, and no settlement website yet. Anyone selling a “claims filing” today is running a scam.
• 🔢 The affected population is roughly 62.2 million people: Conduent’s June 2026 report to HHS placed the count at 62,224,658, and per the HIPAA Journal the incident ranks as the third-largest healthcare data breach reported, behind Change Healthcare (more than 192 million) and Anthem. The incident traces to unauthorized access that began October 21, 2024 and continued until January 13, 2025, attributed in reporting to the SafePay ransomware operation.
• 🧮 The proposed settlement, as filed: an $80 million non-reversionary fund that covers everything — documented-loss claims up to $3,500 per claimant, one year of credit or medical-data monitoring, attorneys’ fees (a 34% request), administration, and service awards — plus a pro-rata cash payment option for the roughly 22-million-person Subclass B and a 20% supplement for California residents at the time of the breach.
• 🗓️ The court schedule is the only reliable calendar: Judge Michael E. Farbiarz ordered more case-specific detail on October 22 before preliminary approval, and the preliminary-approval hearing is scheduled for December 11, 2026 — a date that remains subject to change. Claims would be due 75 days after the notice process begins, under the proposed terms.
• 🛡️ What to do now costs nothing: document any fraud or identity theft with dates and amounts (the evidence a documented-loss claim requires), place the credit freeze or monitoring your notification letter recommends, watch medical billing for care you did not receive, and treat every “settlement registration” call, text or website as a scam until the court-appointed administrator’s site exists.

Table of Contents

The Conduent data breach settlement was signed and filed on October 16, 2026 — an $80 million fund covering the healthcare-data incident that unauthorized access set off in October 2024 and that Conduent now reports at roughly 62 million affected individuals. The weeks between “signed” and “approved” are where the scams operate, in this settlement cycle as in every large one. This breakdown covers the documented record as filed: what the 2024 incident involved and why the affected count grew from 25 million to 62 million, what the settlement as filed proposes to pay and to whom, which court dates now govern the process, what the breach letters in circulation mean, what to do before the claims process opens, and how the follow-on scams run. The material terms described here are proposed and subject to court approval; deadlines become fixed only when the court approves the plan and notices go out.

What Happened: the 2024 Incident and the Count That Grew to 62 Million

The incident: unauthorized third-party access to Conduent’s network, beginning October 21, 2024 and continuing until January 13, 2025, allegedly by the SafePay ransomware operation, exposing personal and health data including Social Security numbers and medical details. Conduent is a business-services vendor performing back-office work for government health programs, health plans and toll systems, which is why the records involved belong to clients’ members and customers as much as to the company’s own workforce.

The affected count changed with review, and the history matters for reading the numbers attached to this case: reporting placed it near 25 million at first disclosure; Conduent’s June 2026 report to HHS raised it to 62,224,658, and per the HIPAA Journal’s ranking cited in the Infosecurity coverage, the incident ranks as the third-largest healthcare data breach reported as of October 2026, behind Change Healthcare (more than 192 million) and Anthem. Count revisions of this kind follow a common pattern: early notifications name the records confirmed first, and later forensic review adds populations stored in harder-to-reach systems. That history also explains the settlement’s subclass structure — roughly 40 million people whose stolen data was stored in a harder-to-access form, and roughly 22 million whose data was more readily exposed.

The Settlement as Filed: the Fund, the Payments, the Monitoring

The agreement’s shape as reported from the October 16 filing: an $80 million settlement, signed and awaiting preliminary approval, funding a non-reversionary fund — non-reversionary meaning unused money stays with the class rather than returning to Conduent — that has to cover everything: documented material losses up to $3,500 per claimant (fraud or identity theft that can be evidenced), one year of credit or medical data monitoring, attorneys’ fees and administration. Conduent has separately agreed to strengthen its data-security practices, and the agreement is not an admission of fault or liability, which the company denies.

The class-division terms, per the proposed notice: members of both subclasses can claim up to $3,500 for documented, unreimbursed losses connected to the incident (documentation required at filing). Members of the roughly 22-million-person Subclass B can additionally elect a pro-rata cash payment, whose value depends on what remains of the fund after fees, monitoring, administration and service awards; the proposed fee request is 34% of the fund, with $1,500 service awards per class representative. California residents at the time of the breach would receive a supplement equal to their pro-rata payment increased by 20%, a provision specific to that state in the proposed agreement. Monitoring under the proposed terms: one year of single-bureau credit monitoring, with medical-data monitoring referenced for members affected through health programs. Epiq is proposed as the settlement administrator. These are proposed terms; the court can accept, question, or require changes before approval.

The Court Calendar: Dates That Matter Now

The case sits in the US District Court for the District of New Jersey (In re: Conduent Business Services Data Breach Litigation, No. 2:25-cv-16953) before Judge Michael E. Farbiarz, and its recent sequence explains where settlement money actually stands: the parties told the court on September 10, 2026 (in Conduent’s SEC filing and a joint status report) that an agreement in principle had been reached in August 2026; the case stayed on September 11; the signed agreement and a preliminary-approval motion landed October 16; and on October 22 the judge did not grant preliminary approval, a two-page order found the motion needed more case-specific support on the fairness factors used in this circuit. The preliminary-approval hearing is scheduled for December 11, 2026, a date that remains scheduled and subject to change.

Under the proposed terms: notice to the class starts no more than 40 days after preliminary approval, claims would be due 75 days after the notice process begins, and the objection/exclusion dates run on their own schedule in the approval order. None of those dates is final until the court approves the plan. Until then: no claim form exists to file, and any date circulating on social media is a guess.

What the Breach Letters Do and Do Not Do

Notification letters continue arriving even while the settlement awaits approval, because state breach-notification laws run on their own timelines and revised counts trigger new rounds. The letters carry the documented source material for individual claimants: what data of yours was involved, what monitoring is offered, and the specific instructions for the period ahead. A legitimate notification letter asks for nothing that costs money: it does not request a fee to process a claim (class claims are free), your passwords, PINs, your full Social Security number “to verify your settlement,” or a payment method “to release funds.” Treat those requests as impersonation.

A practical reading order, the same one our health-data-breach guide applies: your letter first; any announcement from a court-appointed settlement administrator second (none exists yet in this case); the court docket third; social-media summaries last. The state-level regulators’ inquiries (Texas, Montana and Missouri, per the reporting) run independently of the class process, and the Infosecurity coverage of the filing remains the most complete single reference for the deal’s structure.

While the Process Is Closed: the Do-Now List

Documented-loss claims are the Conduent data breach settlement’s portion that rewards preparation, because they pay against evidence, not sentiment: claimants with dated, documented fraud or identity-theft records can collect up to $3,500; someone who only suspects damage to their name cannot clear that documentation requirement. Five steps fit the months before the claims process opens:

1. Document. Assemble the record of any fraud or identity theft you experienced: unauthorized charges, accounts opened in your name, the dates, the amounts, the bank disputes and their outcomes, the police report if one exists. Screenshots with timestamps, sorted chronologically.
2. Freeze and check. Place the credit freeze (free freezes stop new-account fraud; monitoring reports it afterward), and review the free annual credit reports you are entitled to.
3. Watch medical billing. Because the incident involved health data, review explanation-of-benefits statements for care you did not receive, unexpected billing in your name is the standard sign of medical identity theft (the health-data-breach guide’s flow).
4. Treat settlement outreach as unverified. Every call, text or page about “settlement registration” is a scam candidate until the administrator is appointed by the court and its website is announced, a sequence covered in the next section.
5. Mark the real calendar. The 75-day claims window starts at the notice process, not at approval. The December 11 hearing date and the docket are how you track it; the docket watch takes minutes and beats waiting for someone else’s summary.

What the Deal Signals for Health-Data Vendors

The settlement’s size and structure say something about the sector’s exposure: a business-services vendor, not a hospital, not an insurer, carrying a 62-million-person breach to an $80 million proposed class resolution. The exposure structure generalizes: the data your pharmacy, insurer or county program handles often lives on vendors’ networks, and a vendor’s breach reaches the covered entity’s members directly, the delegated-trust architecture our MSP-breach guide dissects, here in a healthcare setting. The settlement lifecycle (agreement in principle, SEC disclosure, signed agreement, preliminary approval, notice, claims window, final approval, distribution) also gives claimants a way to read any “claims are open today” message: a settlement at the preliminary-approval stage has no claim form, and a checklist of which stage produces which artifact makes the counterfeit messages findable.

One factual note on what remains ahead: payments happen only after final approval and any appeals resolve; a year of monitoring activates after approval under the proposed notice. Anyone promising either earlier is ahead of the court, and behind the truth.

How to Avoid the Scams Around This Settlement

Settlement cycles attract follow-on scams, and their shapes are predictable from previous cases: a “claims processor” calling for a fee to register (class claims carry no fees, administration costs come from the fund, on the court’s order); an “expedited payout” text asking for a verification payment; a fake monitoring upgrade that bills your card for a service the settlement funds; a phishing site imitating the administrator’s eventual website before that website exists; and a “lawyer representing you” call requesting a retainer from a class member owed money. This follow-on-fraud activity will run for months at minimum, and the defense is one principle: every legitimate action in this case is free. The claims, the monitoring enrollment, and the letters’ instructions cost nothing; a request for money is the scam itself.

Report what arrives: any scam operation tied to the Conduent data breach belongs with the FTC, IC3 or the local consumer-protection desk, and the same patterns ran against cryptocurrency victims (our stolen crypto recovery guide covers that review), the same operations target whichever breach settlement letters circulate next, and the reports are how the patterns get documented.

Frequently Asked Questions

What Is the Conduent Data Breach Settlement?

A proposed $80 million class-action settlement over the 2024–2025 unauthorized access at the business-services vendor Conduent, signed and filed October 16, 2026 in the US District Court for the District of New Jersey, now awaiting preliminary approval (a hearing is scheduled for December 11, 2026, subject to change). The proposed fund covers documented material losses up to $3,500 per claimant, one year of credit or medical data monitoring, attorneys’ fees and administration; Subclass B members can elect a pro-rata cash payment instead, and California residents at the time of the breach would receive a 20% supplement to that payment. The agreement is not an admission of fault, which Conduent denies.

How Many People Were Affected by the Conduent Data Breach?

Roughly 62.2 million: Conduent’s June 2026 report to HHS placed the affected count at 62,224,658, ranking the incident as the third-largest healthcare data breach reported, per the HIPAA Journal, behind Change Healthcare (more than 192 million) and Anthem. The count started near 25 million and grew through later forensic review, as storage systems and record populations were identified, the count revised upward. That revision history explains the settlement’s two-subclass division (about 40 million in harder-to-access form, about 22 million more readily exposed).

Can I File a Conduent Settlement Claim Today?

No, as of this writing, the claims process is not open: there is no claim form, no settlement website, no payment date, because the settlement has not received preliminary approval (the judge asked for more supporting detail on October 22, 2026, and the hearing is scheduled for December 11, 2026). Under the proposed terms, claims would be due 75 days after the notice process begins, whenever that actually starts. Anyone offering a “claims filing” today is running a scam, not the settlement.

What Should I Do With a Conduent Breach Letter?

The Conduent data breach letters arriving now pre-date the claims process. Read yours as the documented source: what data of yours was involved, what monitoring is offered, and the instructions for the months ahead. Then prepare: document every fraud or identity-theft incident you experienced with dates and amounts (the evidence a documented-loss claim requires), place the credit freeze, watch your medical billing for care you did not receive, and treat follow-up calls and texts about “settlement registration” as phishing until a court-appointed administrator’s site exists.

How Much Money Will I Get From the Conduent Settlement?

Two components, with different rules. Documented losses: claimants in both subclasses can claim up to $3,500 against evidence of fraud or identity theft connected to the incident. Pro-rata cash: Subclass B members can elect a payment whose amount depends on what remains of the fund after the proposed 34% fee request, monitoring, administration and service awards, the amount is not announced and will be set only after final approval. California residents at the time of the breach add a 20% supplement to their pro-rata payment under the proposed terms. Anyone quoting a specific payout figure today is guessing; the claim documentation, not the estimate, is what the settlement pays on.

Financial Disclaimer

This article provides general consumer-protection information and does not constitute legal, financial, or professional advice. Settlement terms remain proposed and subject to court approval and may change; verify against the official court filings, notices from a court-appointed settlement administrator, Conduent’s own SEC disclosures, and licensed legal or financial advisers before acting. The author and publisher disclaim any liability for actions taken based on this information.

@online{agron2026conduentdata,
  author       = {Agron, Edmon},
  title        = {{Conduent Data Breach Settlement: the \$80M Fund, the \$3,500 Claims and the Court Dates That Matter}},
  year         = {2026},
  date         = {2026-11-08},
  organization = {WorldNgayon},
  url          = {https://worldngayon.com/conduent-data-breach/},
  urldate      = {}
}

TY  - ELEC
AU  - Agron, Edmon
TI  - Conduent Data Breach Settlement: the $80M Fund, the $3,500 Claims and the Court Dates That Matter
T2  - WorldNgayon
PY  - 2026
DA  - 2026/11/08/
UR  - https://worldngayon.com/conduent-data-breach/
Y2  - 
ER  -