CareCloud Breach Exposes 3.75 Million Patient Records, Including SSNs and Banking Data
Updated
Updated · Fox News · Aug 30
CareCloud Breach Exposes 3.75 Million Patient Records, Including SSNs and Banking Data
3 articles · Updated · Fox News · Aug 30
Summary
More than 3.75 million people were affected after hackers accessed a CareCloudAmazon Web Services environment between March 10 and March 16 and stole patient and personal data.
The exposed information varied by person but included names, addresses, Social Security numbers, medical records, driver's license or passport details, and banking information, making identity theft and medical fraud a major risk.
CareCloud said it discovered a network disruption on March 16, hired outside cybersecurity specialists, notified law enforcement, secured the affected environment, and found no evidence of continued unauthorized access after containment.
Federal health regulators now list the incident among the largest healthcare data breaches reported in 2026, sharply above the company's earlier disclosures that affected only hundreds of thousands of people.
What specific AWS security failures allowed hackers to silently siphon the personal medical records of 3.75 million people in just six days?
How can millions protect themselves when their medical data is stolen from a third-party cloud vendor they never even knew existed?
With healthcare cyberattacks surging in 2026, are centralized cloud databases becoming a dangerous liability rather than a technological advantage for medical providers?
CareCloud’s 3.75 Million-Patient Data Breach: Timeline, Technical Failures, and the Future of Health-Tech Security
Overview
In March 2026, a hacker quietly accessed CareCloud’s AWS cloud environment, going undetected for six days and stealing sensitive personal, financial, and medical data from 3.75 million patients. The breach was only discovered after a network disruption, leading to a delayed and complex notification process. Because CareCloud serves over 45,000 healthcare providers, the attack created a ripple effect, forcing clinics to manage the fallout and exposing the risks of centralized health-tech vendors. The incident highlights how weak cloud monitoring and security gaps can lead to devastating consequences, pushing the entire health-tech industry to rethink security and vendor risk management.