Over 25 million
The data breach at Conduent Business Services, a major technology contractor for U.S. government agencies, has escalated into one of the largest public sector breaches on record. New information released by state regulators in February 2026 confirms that the incident has impacted over 25 million people nationwide. The breach, which took place between October 2024 and January 2025, resulted in the theft of a massive trove of sensitive data, including Social Security numbers, addresses, and medical and health insurance information. The Safepay ransomware group has claimed responsibility, boasting of stealing 8 terabytes of data. The fallout has affected millions of residents in states like Texas and Oregon and has triggered an investigation by the Texas Attorney General into Conduent and its client, Blue Cross Blue Shield of Texas.
The incident was a large-scale data theft and extortion campaign, allegedly carried out by the Safepay ransomware group. The attackers maintained access to Conduent's network for nearly three months, from October 21, 2024, to January 13, 2025, allowing for a prolonged and extensive data exfiltration operation. Conduent provides critical back-office services for government programs, and the compromised data relates to functions like Medicaid claims, child support payments, and unemployment insurance. The attackers listed Conduent on their dark web leak site, a common tactic used to pressure victims into paying a ransom to prevent the public release of stolen data.
This was a ransomware and data exfiltration attack. While the initial access vector has not been disclosed, the long dwell time suggests the attackers were ableto operate undetected for a significant period. Key TTPs include:
T1567 - Exfiltration Over Web Service: The exfiltration of 8 terabytes of data is a massive undertaking and would require sustained, high-bandwidth C2 channels to transfer the data out of the network.T1078 - Valid Accounts: Long-term persistence is often achieved by compromising and using legitimate credentials, allowing attackers to blend in with normal network traffic.T1486 - Data Encrypted for Impact: Although the primary focus has been on data theft, the involvement of a group named 'Safepay ransomware' implies that data encryption was also likely part of the attack to disrupt operations and increase pressure.The impact of this breach is catastrophic due to the scale and sensitivity of the data involved.
No specific technical Indicators of Compromise have been publicly released.
File Encryption (D3-FE).Update reveals additional affected clients like Humana and Volvo, alongside detailed MITRE ATT&CK techniques and cyber observables for detection.
Implementing strict egress filtering and monitoring can help detect and block large-scale data exfiltration attempts.
Mapped D3FEND Techniques:
Encrypting sensitive data at rest makes it unusable to an attacker even if they successfully exfiltrate it.
Mapped D3FEND Techniques:
Continuous auditing of data access logs can help identify anomalous behavior indicative of a breach in progress.
Mapped D3FEND Techniques:
Segmenting the network can prevent an attacker from moving from a less secure part of the network to the databases containing sensitive PII/PHI.
Mapped D3FEND Techniques:
To detect a massive data theft like the 8 TB exfiltration from Conduent, organizations must employ User Data Transfer Analysis, typically through a Data Loss Prevention (DLP) or UEBA platform. Security teams should configure policies to monitor and alert on high-volume data transfers originating from sensitive data repositories. A baseline of normal data flow should be established, and any transfer that exceeds this baseline by a significant margin (e.g., gigabytes or terabytes of data being moved to an external destination) should trigger an immediate, high-priority alert. This allows security operations to investigate and potentially block the exfiltration in real-time, which is crucial for mitigating the impact of a data breach.
While preventing exfiltration is ideal, organizations handling vast amounts of PII/PHI must plan for a scenario where data is stolen. Encrypting sensitive data at rest is a critical last line of defense. By encrypting the databases and file stores containing the 25 million individuals' records, the data remains unintelligible and useless to the Safepay group even after being exfiltrated. This requires implementing robust encryption with strong key management practices, ensuring that the encryption keys are stored separately and securely, away from the data they protect. This countermeasure renders the stolen data worthless, neutralizing the threat of public leaks and extortion.
A three-month dwell time indicates a failure to detect persistent threat actor activity. Session Duration Analysis can help detect this. Security teams should monitor the duration of user and system account sessions, particularly for privileged accounts. An attacker maintaining persistence will often have sessions that are unusually long or occur at abnormal hours. By baselining normal session lengths and times for different user roles, a UEBA or SIEM can flag a remote access session that has been active for weeks or months as a high-risk anomaly, prompting an investigation that could uncover the long-term compromise.

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.
Help others stay informed about cybersecurity threats