DataBreaches.Net

Menu
  • About
  • Breach Notification Laws
  • Privacy Policy
  • Transparency Report
Menu

Guardant notifies patients of unintended information exposure going back to October 2020

Posted on May 6, 2024 by Dissent

A notification by Guardant Health, Inc. in California (“Guardant”) caught DataBreaches’ eye yesterday.

Guardant is a laboratory that performs cancer screening tests on samples received from its physician and hospital partners. Patient information that they received may have been inadvertently exposed between October 5, 2020 and February 29, 2024.

They explain:

Guardant recently determined that a file containing certain personal information related to samples collected in late 2019 and 2020 was inadvertently made available in a publicly accessible online platform. Guardant promptly removed the file from the online platform and initiated an investigation. The investigation revealed that a Guardant employee inadvertently transferred the file to the platform. The file was believed to have been transferred in October 2020, and on March 4, 2024, we were able to determine, based on a review of available records of activity, that the file was copied by unidentified third parties between September 8, 2023 and February 28, 2024.

They do not explain whether their access logs went back to October 2020 or if they were unable to determine if there was any access prior to September 8, 2023. Nor do they explain why it took them almost six months to discover that the file was being accessed by unidentified parties.

The information contained in the file varied per individual but may have included some or all of the following: names, ages, medical record and identification numbers, and medical information such as treatment information and dates, and test results. Significantly, no financial information or Social Security numbers were contained in the file.

They add:

As general good practice, it is recommended that you regularly monitor statements from your medical providers for any irregularities.

It’s also generally good practice to monitor and audit your system and files. How did this error go undetected for more than three years?

Their notification, submitted to the California Attorney General’s Office, does not disclose how many patients had data accessed by unidentified third parties. The incident has not yet appeared on HHS’s public breach tool.

DataBreaches contacted Guardant yesterday seeking additional details and an explanation of why the error went undetected for more than three years. No reply has been received by publication.

 

No related posts.

Category: Commentaries and AnalysesExposureHealth DataU.S.

Post navigation

← More than 380,000 additional NYC students had info breached in 2022 Illuminate Education hack
Will feds reveal anything exciting about LockBit and LockBitSupp? (YES!) →

Now more than ever

"Stand with Ukraine:" above raised hands. The illustration is in blue and yellow, the colors of Ukraine's flag.

Search

Browse by Categories

Recent Posts

  • Chinese hackers suspected in breach of powerful DC law firm
  • Qilin Emerged as The Most Active Group, Exploiting Unpatched Fortinet Vulnerabilities
  • CISA tags Citrix Bleed 2 as exploited, gives agencies a day to patch
  • McDonald’s McHire leak involving ‘123456’ admin password exposes 64 million applicant chat records
  • Qilin claims attack on Accu Reference Medical Laboratory. It wasn’t the lab’s first data breach.
  • Louis Vuitton hit by data breach in Türkiye, over 140,000 users exposed; UK customers also affected (1)
  • Infosys McCamish Systems Enters Consent Order with Vermont DFR Over Cyber Incident
  • Obligations under Canada’s data breach notification law
  • German court offers EUR 5000 compensation for data breaches caused by Meta
  • Air Force Employee Pleads Guilty to Conspiracy to Disclose Unlawfully Classified National Defense Information

No, You Can’t Buy a Post or an Interview

This site does not accept sponsored posts or link-back arrangements. Inquiries about either are ignored.

And despite what some trolls may try to claim: DataBreaches has never accepted even one dime to interview or report on anyone. Nor will DataBreaches ever pay anyone for data or to interview them.

Want to Get Our RSS Feed?

Grab it here:

https://databreaches.net/feed/

RSS Recent Posts on PogoWasRight.org

  • DeleteMyInfo Wins 2025 Digital Privacy Excellence Award from Internet Safety Council
  • TikTok Loses First Appeal Against £12.7M ICO Fine, Faces Second Investigation by DPC
  • German court offers EUR 5000 compensation for data breaches caused by Meta
  • How to Build on Washington’s “My Health, My Data” Act
  • Department of Justice Subpoenas Doctors and Clinics Involved in Performing Transgender Medical Procedures on Children
  • Google Settles Privacy Class Action Over Period Tracking App
  • ICE Is Searching a Massive Insurance and Medical Bill Database to Find Deportation Targets

Have a News Tip?

Email: Tips[at]DataBreaches.net

Signal: +1 516-776-7756

Contact Me

Email: info[at]databreaches.net

Mastodon: Infosec.Exchange/@PogoWasRight

Signal: +1 516-776-7756

DMCA Concern: dmca[at]databreaches.net
© 2009 – 2025 DataBreaches.net and DataBreaches LLC. All rights reserved.