TriZetto Provider Solutions Data Exfiltration Affecting Healthcare Client Insurance Data
TriZetto Provider Solutions (a Cognizant business unit providing revenue cycle management and claims clearinghouse services) is notifying more than 3.4 million individuals after investigators determined threat actors accessed and exfiltrated healthcare clients’ insurance-related data. The activity reportedly began in November 2024 but was not detected until October 2025, indicating a prolonged period of unauthorized access before discovery.
The incident was reported to the U.S. Department of Health and Human Services via the HIPAA Breach Reporting Tool as impacting approximately 3.43 million people, while TriZetto has not publicly specified how many healthcare customers were affected. Multiple healthcare organizations have publicly stated they were impacted and have issued their own patient notifications, underscoring downstream exposure risk for providers relying on TriZetto’s billing and claims processing services.

Get ahead of threats like this
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
How this story unfolded
6 events from the most recent confirmed update back to the earliest known activity.
Class action lawsuits follow breach disclosures
By early March 2026, TriZetto and parent company Cognizant were facing nearly two dozen proposed federal class action lawsuits over the breach. The suits allege negligence and seek damages and security improvements.
TriZetto begins notifying affected individuals
TriZetto started consumer notifications in early February 2026, offering 12 months of Kroll credit monitoring and identity protection. Notices said exposed data could include personal identifiers, insurance details, and some health information.
TriZetto files HIPAA and Maine breach notices
On February 6, 2026, TriZetto reported the incident to the U.S. HHS HIPAA Breach Reporting Tool and filed notice with the Maine Attorney General. The filings said 3,433,965 individuals were affected, including 1,128 Maine residents.
TriZetto notifies affected healthcare providers
TriZetto alerted providers about the breach on December 9, 2025, after investigating the incident. Multiple healthcare organizations later disclosed that their patients' information was affected.
TriZetto detects suspicious activity in client web portal
TriZetto said it discovered suspicious activity in a web portal used by some healthcare clients on October 2, 2025. The discovery led to an investigation into a long-running data exfiltration incident.
Attackers begin accessing TriZetto transaction records
Investigators determined unauthorized access to TriZetto insurance eligibility verification transaction records began in November 2024, with one report specifying November 19, 2024. The access affected data used by healthcare providers to verify patient insurance coverage.
Related entities
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
Sources
5 references tracked. Mallory keeps watching after this page renders.
Cognizant TriZetto Data Breach Exposes Health Information of 3.4 Million Patients
cybersecuritynews.com
Open sourceTriZetto confirms 3.4M people's health and personal data was stolen during breach | TechCrunch
techcrunch.com
Open sourceCognizant TriZetto breach exposes health data of 3.4 million patients
bleepingcomputer.com
Open sourceTrizetto Notifying 3.4M of 2024 Hack Detected in 2025
govinfosecurity.com
Open sourceTrizetto Notifying 3.4M of 2024 Hack Detected in 2025
bankinfosecurity.com
Open sourceSee the full picture, correlated to your attack surface.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.


