security

One Medical Breach: The Hidden Risk in Third-Party File Storage

The 2026 One Medical breach exposed 153,000 patients via archived third-party file storage. Here's what this silent risk means for your personal documents.

In June 2026, Amazon-owned One Medical disclosed a data breach affecting 153,174 individuals. The breach did not come from their primary electronic medical records system. It came from a third-party file storage platform used to retain archived records — a legacy system from a company One Medical had acquired years earlier.

The extortion group ShinyHunters claimed to have exfiltrated approximately 8.8 terabytes of data and threatened to publish it publicly unless One Medical responded by June 22, 2026.

Most coverage focused on the scale and the drama of the ransomware threat. The more instructive story is the mechanism: a storage system that nobody was paying much attention to, holding data nobody thought was immediately active, became the point of failure.

What “Third-Party File Storage” Actually Means

When companies acquire other companies, they absorb their infrastructure. Iora Health, the predecessor to One Medical Seniors, had its own patient records platform. When One Medical acquired it, that legacy system continued running — holding demographic information and clinical records for patients in cities like Atlanta, Denver, Houston, and Seattle.

Third-party file storage in this context means records were not in One Medical’s primary system. They were in a contracted file repository managed or partially managed by an outside vendor. The breach was limited to this legacy archive, which is why the company could truthfully say it did not affect “other One Medical clinics, services, or the One Medical electronic medical record system.”

That separation is small comfort to the 153,000 people whose names, home addresses, telephone numbers, email addresses, and clinical records were exposed.

The Archive Problem

There is a pattern across large data breaches that does not get enough attention: the data that gets exposed is often data that nobody thought was at risk because nobody thought about it much at all.

Active systems get security reviews. Active systems get patched. Active systems are watched by people whose job it is to watch them.

Archived systems accumulate.

They were spun up to hold data that needed to be retained for legal or compliance reasons. They were integrated into a larger organization during an acquisition. They continued running on older infrastructure because migrating them was expensive and low priority. Nobody had a clear owner. The credentials were shared. The access controls reflected a threat model that was years out of date.

This is the archive problem. The data is stale in the sense that it is not being actively used. It is not stale in the sense that it is any less sensitive. A patient’s home address and diagnosis from 2019 is just as identifying and just as valuable to an extortionist as that same data today.

Why This Matters Beyond Healthcare

Healthcare is a high-visibility target because of HIPAA and the obvious sensitivity of medical records. But the dynamic here is not specific to healthcare.

Any organization that stores files — documents, scans, records, receipts, photos — accumulates archive risk over time. The same pattern plays out with:

  • Legal firms that digitize old case files and store them in document management systems that predate current security standards
  • Accountants and financial advisors whose client files live in systems acquired when the practice merged with another firm
  • Schools and universities with student records in legacy systems from before cloud migration
  • Individuals who have scattered their personal files across services they set up years ago and do not regularly audit

The last category is the one that applies to most people reading this.

Your Personal Archive Risk

Think about where your personal files are stored right now. Not just the places you actively use — the places you used to use, or set up once and forgot about.

Some common sources of personal archive risk:

Old cloud storage accounts: Google Drive, Dropbox, Box, and OneDrive all hold files from accounts people set up years ago. Some of those accounts are still active with old credentials. Some have had their free storage tier quietly changed, with files now sitting in reduced-access storage. Many contain scans of documents — passports, insurance cards, tax returns, lease agreements — uploaded once and never removed.

Old email attachments: email services are cloud file storage by another name. The tax return your accountant sent in 2017 is still there as an attachment. So are the scans of your driver’s license you sent to a landlord. So are the medical records you forwarded once to a specialist.

Shared family drives: photos and documents uploaded to shared folders for a family event, a move, or a medical situation — still accessible, often to more people than you remember sharing them with.

Old phones synced to old accounts: when you replaced your phone, your photos may have been backed up to an account that is still active, still holding data, and still accessible through credentials you have not reviewed in years.

Acquired and rebranded services: the cloud service you used in 2016 may have been acquired twice since then. Your data is still there, under whatever data policies the current owner has set.

What Auditing Your Personal Archive Actually Looks Like

Reducing your exposure to archive risk does not require technical skill. It requires a deliberate audit of where your data lives.

Step 1: List every account you have used for file storage

Go through your email history and search for account confirmation emails for storage services. Check your password manager if you use one. Think about services you used during major life events — a move, a medical procedure, a job change, a divorce — when you may have uploaded and shared sensitive documents.

Step 2: Check what each account still holds

Log in to each account you can still access. What files are there? Are they files you still need? Are they files that contain sensitive information — financial records, government ID scans, medical documents, photographs of things you would not want publicly visible?

Step 3: Remove what you do not need to keep

Delete files you do not need. Then empty the trash. Some services retain deleted files for 30 days before permanent erasure. Some retain them longer. Check the service’s policy and wait out the retention period if necessary.

For files you need to keep, consolidate them somewhere you actively maintain and review.

In Google Drive and Dropbox, audit shared links. Anything set to “anyone with the link” should be reviewed. If the share is no longer needed, revoke it. Check connected apps — services you granted access to your storage years ago may still technically have that access.

Step 5: Change credentials on old accounts

Old accounts often have old passwords. If you cannot or do not want to delete an account, update its password and check whether two-factor authentication is enabled.

The Governance Gap

The One Medical breach illustrates something that applies at every scale: security governance degrades when there is no clear owner.

One Medical inherited an archived storage system through an acquisition. That system did not have the same attention as One Medical’s primary infrastructure. When organizations grow through acquisition — as almost all large organizations eventually do — the inherited systems carry inherited risk.

For individuals, the equivalent dynamic is attention drift. You create an account, upload files, and move on. You never formally decommissioned the account. It keeps running. Its security posture reflects the defaults and the threat landscape of the year it was set up, not the current one.

The files you stored five years ago in a service you no longer use are as real as the files you uploaded last week. They are not less recoverable by someone with unauthorized access. And they are often less protected, because no one has been thinking about them.

Consolidation as Risk Reduction

One practical response to archive risk is consolidation: reducing the number of places your personal data lives.

Fewer storage locations means fewer attack surfaces, fewer credentials to maintain, fewer third-party systems handling your data, and — critically — fewer places you have to audit when something changes.

This does not mean putting everything in one service at the expense of having no backup. The principle is to have a deliberate architecture: an intentional set of places where your files live, each one chosen and maintained rather than accumulated by default.

The One Medical breach happened in a storage system that had accumulated through acquisition without being redesigned for the current threat environment. That is the failure mode to prevent in your own file storage: not active attack, but passive neglect of systems that outlive their original context.

Your personal files deserve the same review cycle that a responsible IT department would apply to any legacy system. The difference is that the files are yours, and the review is up to you.

Your memories deserve better than an ad platform.

Try daftei free →
← All posts