CareCloud Breach Expands to 3.75 Million: AWS Cloud EHR Dump Leaks SSN/Medical Records/Payment Data; Concurrent CEVA Logistics Supply-Chain Incident Hits Pokémon Center/Valve
On 19 August, US healthcare IT vendor CareCloud updated the HHS portal: a 10–16 March AWS cloud intrusion jumped from 350,000 to 3,756,469 affected individuals. Leaked fields include SSN/driver license/medical records/payment data. Same day: CEVA Logistics supply-chain incident, 29 July–1 August, hit Pokémon Center, Valve, ING, Bol customer order data.
Between 18–19 August, CareCloud filed two supplemental disclosures with the U.S. Department of Health and Human Services (HHS) breach-tracking portal: an intrusion into its AWS cloud environment from 10–16 March jumped from ~350,000 affected individuals to 3,756,469. Leaked fields cover name, postal address, Social Security number (SSN), driver license number, date of birth, health insurance information, clinical records, and for a subset, full payment-card and bank-account data. Same-day rollup also covers a 29 July–1 August cyberattack on logistics vendor CEVA Logistics: eight European warehouses halted; order data of retail customers including Pokémon Center, Valve, ING, De Bijenkorf, and Bol was affected. Both incidents put the supply-chain trust line back on the table.
Incident Overview
CareCloud is a U.S.-listed healthcare IT vendor. Mid-March saw an EHR environment outage, followed by an SEC disclosure of an 8-hour network interruption; initial affected count was ~350,000. On 18 August CareCloud first posted the detailed figure 3,371,508 on the HHS portal; on 19 August an HHS update revised it to 3,756,469. HHS confirmed the figure and it is the fifth-largest U.S. healthcare data breach of 2026.
The HHS form also discloses that CareCloud is providing 12–24 months of IDX identity-protection services to affected individuals, coverage cutoff 17 December 2026. Most affected individuals had never dealt with CareCloud directly; the incident is read as a signal to reshape healthcare SaaS trust chains. CEVA Logistics is a contract logistics and fulfillment vendor under France's CMA CGM group. The incident originated in an intrusion starting 29 July; eight European warehouses halted. Multiple retail customers learned their own customers' data had been accessed only after CEVA notices on 1 August. Pokémon Center UK and Germany customers first received fulfillment-anomaly notices in mid-August; the company later disclosed in a second notice that upstream CEVA intrusion was the cause.
Technical Details
- CareCloud intrusion path: between 10–16 March the attacker accessed one of CareCloud's AWS cloud environments, then exported data from associated databases in that environment. Sample notice letters do not list a full field inventory; TechCrunch reported SSN, passport/driver license numbers, bank and clinical records.
- CEVA intrusion path: CEVA servers were compromised 29 July–1 August. Affected customers include Valve's Steam hardware business, Bol, De Bijenkorf, Ace Tate, ING, and AFC Ajax Amsterdam. CEVA does not hold Pokémon Center customer payment-card data, so payment-card fields are not in this leak.
- Leaked fields: CareCloud—name, SSN, passport/driver license number, date of birth, health insurance, clinical records, bank/financial information, full payment cards for a subset. CEVA—name, shipping address, phone, email, purchased-item contents (no payment cards).
- Detection and disclosure lag: CareCloud occurred in March → notices began 25 July → HHS posted the final count 19 August. CEVA intrusion 29 July–1 August → customers notified 1 August.
- Attribution and claims: as of 19 August, no ransomware crew or data-extortion group has publicly claimed the CareCloud attack. CEVA likewise has no public attribution.
- Supply-chain structure: CareCloud—HHS/healthcare supply chain; CEVA—retail/e-commerce logistics chain. Both show third parties the customer never contracted amplifying enterprise data risk.
Impact Assessment
CareCloud flattening a jump from 350,000 to 3.7 million into official paperwork looks bland; it is the typical large-SaaS pattern of ETL-path inference error plus slow two-layer forensic recheck. The first coarse estimate covered only the subset counted by state AG offices by state-resident numbers; the HHS federal count covers patients nationwide. CareCloud CEO Stephen Snyder has not responded to any questions on whether a ransom was paid, whether a CISO was ever appointed, or future org changes.
CEVA's impact is a different supply-chain curve: the logistics vendor does not face consumers directly, but holds the brand's full order flow (name, address, phone, SKU/qty/price, shipping node). Combined with slower retailer-to-customer notice (Pokémon Center's first email called it a fulfillment anomaly, not a cyberattack), this is a flagship 2026 case of 3PL/fulfillment-side information leak. Purple Shield Security's 19 August recap called both incidents third-party-risk lessons, warning that board comms, regulatory disclosure, and media strategy should reserve revision room beyond the first number—or repeated revisions burn trust.
Remediation
- CareCloud patients and downstream orgs: affected individuals should immediately enroll in the IDX 12–24 month identity-protection service; enable SSN monitoring, health-plan account access, and bank-account alerts together. Downstream clinics and billing orgs should broadcast to billed patients a notice to watch for anomalous consults/charges.
- Healthcare SaaS audit: every healthcare SaaS provider hosting EHR/EMR on AWS/third-party cloud should immediately audit IAM and S3/RDS public-access policies. Enable IMDSv2, least-privilege roles, full-field encryption at rest and in transit, and cross-account access-log aggregation.
- CEVA/fulfillment-side IR: downstream brands should treat customer name/address/order data on non-owned systems as a probable leak set. Two-step customer notice: one-shot notification + extended monitoring window. Force secondary identity verification on internal RMA/returns and customer-support flows.
- Contracts and third-party governance: procurement and service contracts should set a notice-latency ceiling (recommend 72 hours), customer public-comms obligations, and data-retention/reconciliation mechanics. Write IDX/Experian-class identity-protection terms into the IR SLA.
- Board and media comms: first-notice wording should be data categories + preliminary estimate + commitment to later revision, not a specific headcount. Pre-load the supply-chain map and key control points into the board-reporting template so technical detail can ship the same day as regulatory disclosure.
References
- Purple Shield Security: CareCloud and CEVA third-party risk recap
- Yahoo/TechCrunch: CareCloud 3.7M patient data leak confirmed
- FreightWaves: CEVA Logistics intrusion hits European retailers
- ZeroDay News: CareCloud 3.7M patient data leak tracker