Conduent Data Breach May Be Largest in U.S. History; Texas AG Investigates

Conduent Data Breach Escalates, Affecting Over 25 Million and Prompting Texas AG Investigation

CRITICAL
February 25, 2026
February 26, 2026
6m read
Data BreachSupply Chain AttackRansomware

Impact Scope

People Affected

over 25 million

Affected Companies

Conduent Business Services, LLC

Industries Affected

GovernmentHealthcareFinance

Geographic Impact

United States (national)

Related Entities(initial)

Threat Actors

Safepay

Organizations

Texas Attorney General

Other

Conduent Business Services, LLC

Full Report(when first published)

Executive Summary

A data breach at Conduent Business Services, LLC, a major provider of back-office services for government and corporate clients, is now being reported as potentially the largest in U.S. history. Reports from February 24, 2026, indicate the breach, which occurred between October 2024 and January 2025, affects over 25 million Americans. The Safepay ransomware group has claimed responsibility, alleging the theft of over 8 terabytes of data containing a trove of sensitive Personally Identifiable Information (PII) and Protected Health Information (PHI). Due to the immense scale, with 15.4 million affected in Texas alone, the Texas Attorney General has launched an investigation into the incident, which is being called a catastrophic failure of third-party risk management.

Threat Overview

Conduent provides critical services like payment processing and healthcare claims management for numerous state government agencies. This position makes it a highly valuable target, as a single breach can expose the data of millions of citizens across multiple states. The Safepay ransomware group, which claimed the attack, followed a double-extortion model by exfiltrating the data before making its demands.

The stolen data is exceptionally sensitive and includes:

  • Full Names
  • Social Security Numbers (SSNs)
  • Physical Addresses
  • Medical Histories and Health Insurance Information

This is a supply chain attack with cascading consequences, where the compromise of a single contractor leads to a nationwide data security crisis.

Technical Analysis

While the specific intrusion vector has not been disclosed by Conduent, the attack pattern is characteristic of a large-scale data theft operation:

  1. Initial Access: The attackers likely gained access through a common vector such as a vulnerability in a public-facing system (T1190 - Exploit Public-Facing Application) or a successful phishing campaign against a privileged employee (T1566 - Phishing).
  2. Privilege Escalation and Lateral Movement: Once inside, the attackers would have escalated their privileges to gain administrative control over servers and databases, moving laterally across the network to locate the most valuable data repositories.
  3. Collection & Exfiltration (T1537 - Transfer Data to Cloud Account): The core of the attack was the exfiltration of a massive volume of data (8 TB). This would have required a sustained, high-bandwidth transfer over a prolonged period (October to January), suggesting the attackers maintained persistent access and were able to evade detection for months. The data was likely siphoned to attacker-controlled cloud storage.

Impact Assessment

This is a data breach of historic proportions. The impact on the 25+ million affected individuals is catastrophic, exposing them to a lifetime risk of identity theft, sophisticated financial fraud, and medical identity theft. The sheer volume of data, combining PII and PHI, makes it a goldmine for cybercriminals. For Conduent, the consequences are severe: massive regulatory fines (e.g., under HIPAA), costly litigation, loss of government contracts, and irreparable reputational damage. For the various state governments that entrusted their citizens' data to Conduent, this is a major crisis of public trust and a failure of vendor oversight.

Detection & Response

Detecting a slow, long-term data exfiltration of this magnitude is extremely challenging but not impossible.

  1. Egress Traffic Analysis: The most critical detective control is monitoring outbound network traffic. A sustained, large data flow of 8 TB over several months should have triggered alerts. Organizations must baseline normal egress traffic volumes and patterns and alert on significant deviations, especially to unknown or suspicious destinations. This is the primary goal of D3FEND's D3-UDTA - User Data Transfer Analysis.
  2. Data Loss Prevention (DLP): DLP solutions configured to identify and block transfers containing PII/PHI patterns (like SSN or medical record formats) could have detected and potentially blocked the exfiltration.
  3. Database Activity Monitoring (DAM): DAM tools can monitor for and alert on unusual database access, such as a single account querying and exporting millions of records over time.

Mitigation

Preventing such a catastrophic supply chain breach requires rigorous security fundamentals and vendor management.

  1. Third-Party Risk Management: Government agencies and corporations must conduct thorough and continuous security assessments of their critical vendors like Conduent. This includes audits, penetration tests, and validation of their security controls.
  2. Network Segmentation and Zero Trust: Implement a Zero Trust architecture where access to sensitive data repositories is strictly controlled and continuously verified. Data should be segmented, and access granted on a need-to-know basis, preventing a single compromised account from accessing everything. This is a form of D3FEND's D3-NI - Network Isolation.
  3. Data Encryption: Sensitive data like SSNs and PHI must be encrypted at rest and in transit. While this doesn't prevent theft, strong encryption can render the stolen data useless to the attackers if the keys are properly managed.
  4. Incident Response Planning: Have a well-defined and tested incident response plan specifically for large-scale data breaches, including pre-drafted communication plans for customers, regulators, and the public.

Timeline of Events

1
October 1, 2024
The period during which the Conduent data breach began.
2
January 31, 2025
The period during which the Conduent data breach ended.
3
February 24, 2026
The escalating scale of the breach and the Texas AG investigation are publicly reported.
4
February 25, 2026
This article was published

Article Updates

February 26, 2026

New figures confirm over 25 million victims nationwide, with specific impacts in Oregon (10.5M) and a precise attack dwell time from Oct 2024 to Jan 2025.

MITRE ATT&CK Mitigations

Implement DLP solutions to detect and block the unauthorized transfer of massive amounts of PII and PHI.

Segment networks to prevent attackers from moving from a less secure entry point to the crown jewel databases.

Audit

M1047enterprise

Implement comprehensive logging and auditing of network traffic and database access to detect anomalous activity.

This is a vendor management failure. Rigorous auditing of third-party suppliers like Conduent is required.

D3FEND Defensive Countermeasures

To detect a massive, slow-burn data exfiltration like the one at Conduent, User Data Transfer Analysis is the most critical detective control. Security teams must use tools like Netflow analyzers, DLP, or cloud access security brokers (CASBs) to baseline normal data transfer volumes and patterns for all systems. The exfiltration of 8 terabytes, even over four months, represents an average of over 65 gigabytes per day. This is a significant anomaly that should have triggered alerts. A UEBA platform could correlate this data transfer with the compromised account, flagging that a single user was responsible for an impossibly large amount of data egress. This is the primary method for catching large-scale data theft in progress.

A breach of this magnitude is often enabled by a flat, unsegmented network. Conduent should have implemented strict network isolation based on Zero Trust principles. The databases containing sensitive PHI and PII for millions of citizens should have been housed in a highly secured data enclave. Access to this enclave should be denied by default, with firewall rules only allowing connections from a small, specific set of application servers. Furthermore, those application servers should not have direct internet access. This containment strategy ensures that even if an attacker compromises a system on the corporate network, they cannot pivot to the sensitive data repositories, effectively containing the breach at the perimeter.

To gain access to and exfiltrate such a large dataset, the attackers would have needed highly privileged accounts. Continuous monitoring of domain accounts is essential. This includes alerting on any privilege escalation, such as an account being added to a Domain Admins group. It also involves using Database Activity Monitoring (DAM) tools to watch for anomalous queries. A DAM solution could have alerted on a single account performing SELECT * queries against entire patient or citizen tables, or an account that normally only performs reads suddenly attempting to export large datasets. This provides a crucial internal detection layer focused on the attacker's actions against the data itself.

Sources & References(when first published)

4 Data Security Incidents to Know About (February 2026)
Security Magazine (securitymagazine.com) February 24, 2026

Article Author

Jason Gomes

Jason Gomes

• Cybersecurity Practitioner

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.

Threat Intelligence & AnalysisSecurity Orchestration (SOAR/XSOAR)Incident Response & Digital ForensicsSecurity Operations Center (SOC)SIEM & Security AnalyticsCyber Fusion & Threat SharingSecurity Automation & IntegrationManaged Detection & Response (MDR)

Tags

ConduentData BreachSupply Chain AttackRansomwareSafepayPIIPHIHealthcare

📢 Share This Article

Help others stay informed about cybersecurity threats