DataBreaches.Net

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

No need to hack when it’s leaking, Thursday edition: DM Clinical Research

Posted on February 20, 2025 by Dissent

Another day, another massive leak.

Researcher Jeremiah Fowler reports that he found unsecured data with 1,674,218 records belonging to DM Clinical Research. DM Clinical Research is a Texas-based network of more than 24 multi-therapeutic clinical trial sites involved in research on vaccines, internal medicine, pediatrics, gastroenterology, psychiatry, neurology, women’s health, and more. DM Clinical Research’s site claims that they have tens of thousands of patients enrolled. Whether that is a lifetime total or current is not clear.

Fowler’s findings were reported by Website Planet:

I saw a trove of potentially sensitive personal and medical information, such as names, dates of birth, phone numbers, email addresses, vaccination statuses (including specific vaccines received), current medications, and other health conditions that the survey recipients may have.

Some surveys also contained notes that included adverse reactions to COVID-19 vaccines, other health problems, doctor’s name, whether the individual was on birth control or pregnant, and the name of the person conducting the survey.

On inquiry, Fowler clarified that some records were questionnaires, some were screening tools, and some appeared to be surveys.  DataBreaches notes that although Fowler refers to the data being a “database,” it was actually an Azure blob.

But is DM Clinical Research covered by HIPAA or are they a business associate, or neither?

DataBreaches.net has sent three requests to DM Clinical Research asking them to state whether they are covered by HIPAA or not. They did not reply at all.

As the NIH website explains with respect to researchers and HIPAA:

Covered entities are health plans, health care clearinghouses, and health care providers that transmit health information electronically in connection with certain defined HIPAA transactions, such as claims or eligibility inquiries. Researchers are not themselves covered entities, unless they are also health care providers and engage in any of the covered electronic transactions. If, however, researchers are employees or other workforce members of a covered entity (e.g., a hospital or health insurer), they may have to comply with that entity’s HIPAA privacy policies and procedures. Researchers who are not themselves covered entities, or who are not workforce members of covered entities, may be indirectly affected by the Privacy Rule if covered entities supply their data. In addition, it should be noted that the HHS and FDA’s Protection of Human Subjects Regulations (45 CFR part 46 and 21 CFR parts 50 and 56, respectively) may also apply to clinical research.

DM Clinical Research’s website states, in part:

Every clinical trial we conduct is overseen by one of our own physicians — otherwise known as a Principal Investigator (PI). They believe in the importance of high-quality trials done with care in order to advance life science technologies. They work within their specialty therapeutic areas and ensure each participant is treated with compassion, safety, and professionalism.

DM Clinical Research’s failure to answer a simple question suggests that we should wonder whether they intend to notify any state attorneys general, HHS, or research participants of this leak.  Hopefully, they have adequate access logs that can prove whether the data was accessed by unauthorized individuals and their IP addresses.

 

 

 

Related posts:

  • HIPAA Security Rule Facility Access Controls – What are they and how do you implement them?
Category: Health DataU.S.

Post navigation

← Meet NailaoLocker: a ransomware distributed in Europe by ShadowPad and PlugX backdoors
Hackers Claim Data Breach at Bulgaria’s Supreme Administrative Court →

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

  • Kentfield Hospital victim of cyberattack by World Leaks, patient data involved
  • India’s Max Financial says hacker accessed customer data from its insurance unit
  • Brazil’s central bank service provider hacked, $140M stolen
  • Iranian and Pro-Regime Cyberattacks Against Americans (2011-Present)
  • Nigerian National Pleads Guilty to International Fraud Scheme that Defrauded Elderly U.S. Victims
  • Nova Scotia Power Data Breach Exposed Information of 280,000 Customers
  • No need to hack when it’s leaking: Brandt Kettwick Defense edition
  • SK Telecom to be fined for late data breach report, ordered to waive cancellation fees, criminal investigation into them launched
  • Louis Vuitton Korea suffers cyberattack as customer data leaked
  • Hunters International to provide free decryptors for all victims as they shut down (2)

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

  • German court awards Facebook user €5,000 for data protection violations
  • Record-Breaking $1.55M CCPA Settlement Against Health Information Website Publisher
  • Ninth Circuit Reviews Website Tracking Class Actions and the Reach of California’s Privacy Law
  • US healthcare offshoring: Navigating patient data privacy laws and regulations
  • Data breach reveals Catwatchful ‘stalkerware’ is spying on thousands of phones
  • Google Trackers: What You Can Actually Escape And What You Can’t
  • Oregon Amends Its Comprehensive Privacy Statute

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.