Cyber & AI intelligence
Briefs indexed3981
Issues37
Published Mondays07:30 CT
▣ Breach PHOEBE-PUTNEY-MEDC 2026-11-22

Phoebe Putney Health System: Patient Data Stolen in Breach at Former Billing Vendor MedCom

"Phoebe Putney Health System, the hospital network in Albany, Georgia, has confirmed that the breach letters some of its patients are now getting are real and not a scam. The letters come from MedCom Solutions, Inc., a…"

Phoebe Putney Health System, the hospital network in Albany, Georgia, has confirmed that the breach letters some of its patients are now getting are real and not a scam. The letters come from MedCom Solutions, Inc., a Pittsburgh company that used to do billing work for Phoebe. MedCom says files containing protected health information were taken from servers run for it by its former managed services provider, Expedient Data Center, between September 18 and September 22, 2025. The stolen data includes names, Social Security numbers, dates of birth, insurance details and diagnosis information. MedCom only began mailing letters to individuals on November 13, 2026, about 14 months after the theft. Neither MedCom nor Phoebe has said how many people were affected. State regulator filings show only small numbers so far: 22 Massachusetts residents according to ClaimDepot, and 2 Vermont residents according to law firm Strauss Borrelli.

What Happened

MedCom's notice, dated November 13, 2026, says the company noticed suspicious activity in September 2025 on systems hosted and managed by its former managed services provider. Strauss Borrelli and ClaimDepot both name that provider in full as Continental Broadband Pennsylvania, which does business as Expedient Data Center. Reports disagree on when MedCom found the activity. ClaimDepot gives a discovery date of September 22, 2025, the last day of the theft window. Strauss Borrelli says the exact discovery date was not disclosed. Every account agrees that the theft ran from September 18 to September 22, 2025.

MedCom says it brought in outside cybersecurity and digital forensics specialists, reported the incident to federal law enforcement and the U.S. Department of Health and Human Services (HHS), and hired a data review vendor to work out whose records were in the stolen files. ClaimDepot gives this timeline for what followed:

Phoebe put out a statement on November 20 after patients called to ask whether the letters were real. The health system stresses that it had stopped working with MedCom before the breach, but MedCom still held some Phoebe patient data from their earlier relationship. "The breach had nothing to do with Phoebe," a spokesperson told WALB. Law firm Emery Reddy reports that MedCom's own notice says this was not a breach of MedCom's own network, because the servers involved were hosted and managed by Expedient.

The breach is not limited to Phoebe. Phoebe and WALB both say MedCom served other hospitals and healthcare organizations across southwest Georgia, and Phoebe warns that people who were treated at more than one of them may get several letters about the same incident. Emery Reddy notes that MedCom's public notice does not name the providers involved. ClaimDepot says MedCom has also reported the breach to the attorneys general of New Hampshire and Vermont, and Emery Reddy cites a Massachusetts filing (number 2026-2005).

What Was Taken

WALB's summary of MedCom's November 13 statement lists these stolen data types:

Strauss Borrelli and Wisevoter report much the same list. ClaimDepot's list from the regulator filings leaves out Social Security numbers, dates of birth and insurance information, and focuses on account numbers, diagnosis, treatment, prescription, clinical and provider details. Most likely the exposed fields differ from person to person, so not every letter will list the same items. Each recipient should check which data types their own letter names.

Scale: No total has been published. MedCom has not given one, Phoebe has not said how many of its patients were affected, and no figure from the HHS breach portal has been reported. State filings show 22 Massachusetts residents (ClaimDepot) and 2 Vermont residents (Strauss Borrelli). Those numbers are small because MedCom's clients cluster in specific regions. They say nothing about the true total, which is probably concentrated in Georgia and other states where MedCom's hospital clients operate.

Medical identity theft is harder to undo than card fraud. A stolen card can be cancelled, but a Social Security number paired with a diagnosis, insurance details and a medical record number cannot be changed. That combination can be used for insurance fraud, fake prescriptions, targeted phishing and extortion for years.

Why It Matters

Risk from former vendors lasts after the contract ends. Phoebe's main defence is that it was not working with MedCom when the breach happened, and that is true. It is also the lesson. MedCom still held Phoebe patient records after the relationship was over, and those records were stolen. Under HIPAA, a business associate agreement should require the vendor to return or destroy protected health information when the contract ends, unless that is not feasible. Whether MedCom was allowed to keep this data, and why, has not been explained publicly.

This is a breach at a fourth party. The data moved from patient to hospital, from hospital to billing vendor, and from billing vendor to that vendor's hosting provider, and it was taken at the last step. Patients never chose MedCom, and they had no way of knowing about Expedient. Most hospital vendor risk programmes do not examine their vendors' infrastructure providers, and many do not look at their own data held by former vendors either.

Notification took 14 months. By ClaimDepot's timeline, MedCom took almost 11 months to finish the file review and then almost two more months to start telling individuals. HIPAA requires notice without unreasonable delay and no later than 60 days after discovery. A data review can sometimes justify a longer wait, but 14 months is still a long time for people whose Social Security numbers were taken. At least three law firms (Strauss Borrelli, Emery Reddy and attorneys working with ClassAction.org) are already looking into possible class actions, and the delay will probably be a central point in any lawsuit.

Scammers will copy the letters. The fact that Phoebe needed to confirm the letters are real shows a problem every healthcare breach creates. A letter from a company patients have never heard of looks exactly like a phishing attempt, and criminals will send fake versions with harmful enrollment links or callback numbers.

The Attack Technique

The method is unknown. No one has said publicly how the attackers got into the Expedient-hosted servers. MedCom has not named a threat actor, no ransomware group has claimed the attack in any reporting, and neither MedCom nor Expedient has released technical details or indicators of compromise. Expedient has not commented in any of the coverage.

What has been confirmed is limited. MedCom describes the incident as file exfiltration over a five-day window from servers that a third party hosted and managed. It does not mention encryption or any disruption to systems. Taking data without encrypting it fits the extortion model now common in healthcare attacks, but no source says a ransom was demanded, so that remains a guess. Because MedCom says Expedient managed the systems, the way in may have been the provider's administrative access, remote management tools or shared infrastructure rather than MedCom's own network. That has not been confirmed either.

What Organizations Should Do

  1. Check what your former vendors still hold. Make a list of every business associate you have stopped working with in the past five to seven years. Get written proof that each one returned or destroyed your protected health information, as the agreement required. If a vendor says it cannot destroy the data, write down why and keep checking.
  2. Find out who hosts your vendors' systems. Business associate due diligence should identify the vendor's hosting and managed services providers, require those providers to be covered by downstream business associate agreements, and require the vendor to tell you when its hosting arrangements change.
  3. Put notification deadlines in your contracts. Require vendors to report a suspected incident within a set number of days, and to hand over affected-patient lists as they are confirmed rather than at the end of a review lasting most of a year. Under HIPAA, you are still responsible for your patients' data while it sits with a vendor.
  4. Send vendors only the data they need. Charge capture and billing analysis rarely require full Social Security numbers. Tokenise or remove the fields the vendor does not actually need before the data leaves your network.
  5. Prepare your patient communications early. As Phoebe did, publish a page confirming that the vendor's letters are real, list the official enrollment site (Epiq, for MedCom's 12 months of monitoring, according to ClaimDepot) and the official callback numbers, and warn patients about fake versions.
  6. Watch for misuse of patient records. Health systems served by MedCom should alert their fraud and revenue-cycle teams to watch for signs of medical identity theft. These include unusual claims, prescription requests or insurance changes tied to the medical record numbers of affected patients.

Sources: Phoebe confirms patient information leaked in former third-party ve... | Phoebe Confirms Legitimacy of Data Breach Notification Letters Issu... | MedCom Solutions Data Breach Emery Reddy | MedCom Solutions Data Breach Investigation | South Georgia News & Weekend Briefing — November 21, 2026 FIRST -... | MedCom Solutions Data Breach Exposes SSNs; Lawsuit Possible | MedCom Solutions Data Breach Exposes Health Records | Phoebe Putney Discloses Patient Data Leak Wisevoter