Healthcare provider · Obstetrics and gynecology services · Specialty clinic · USA

Glendale OBGYN Data Breach (2025)

Obstetrics and gynecology practice.

Pilot record · BRI 2.0
Breach Risk Index
LowGuardedElevatedHighSevere
Elevated
Third of five bands on the Breach Risk Index
Observed minimumAt least this much was seen. Read it as a floor · as of October 28, 2026
What this rating measures

The Index rates how dangerous a breach is right now rather than how large it was. It values each exposed field on its own, ages each one according to what that field is, and models what the assembled set lets an attacker do.

It is read against what is observed circulating, not what was announced. Five bands run from Low through Guarded, Elevated and High to Severe.

Every rating carries a status. Observed means it rests on fields seen circulating. Observed minimum means at least that much was seen, so read it as a floor. Provisional means the field list comes from breach catalogues and is not yet verified. How sure we are of the evidence is shown separately, and it never lowers the rating. How the Index works →

Data sensitivity
Restricted

Includes data that cannot be reissued or taken back. A changed password does not reach it.

Circulating
34,211 rows
Field types
4 seen
Breach date
2025-11-13
Observed as of
2026-10-28
Attributed
SafePay
Vector
Ransomware / Extortion
How it unfolded38 days from breach to listing
  1. Breach
  2. Listed in breach catalogues
  3. 10 months laterNotice filed · HHS OCR breach portal
  4. Observed · scored
What came out

What data was exposed

Social Security NumberCannot be reissued
Home addressWhere you sleep
Email AddressContact
Phone NumberContact
Red cannot be reissued or taken back · Blue is the residence · Black is movement, where you go rather than where you live · Grey is high-signal data that is not standard breach material
What it enables

How this data can be used against you

Not enabled

Identity

No usable identity package in what circulates.

Not enabled

Physical targeting

No usable location detail in what circulates.

Not enabled

Social engineering

Nothing in what circulates to build an approach on.

Not enabled

Account access

No usable login material in what circulates.

Not enabled

Financial

No usable financial detail in what circulates.

Not enabled

Coercion

Nothing in what circulates is sensitive enough for leverage.

Not enabled

Health

No medical detail in what circulates.

Not enabled

Crypto

Nothing in what circulates is tied to crypto assets.

Enabled: the set on its own is enough · Partial: part of what is needed, or weakened · Not enabled: nothing usable in what circulates
What you should do

Three key actions to take

Assume your home address is findable

Be wary of unexpected visitors, deliveries or messages that mention where you live. Ask people-search sites to remove your address, and check again every few months, because listings come back.

Freeze your credit, or confirm your freeze is in place

If you have not already, place a free freeze at Equifax, Experian and TransUnion. If you have, sign in to each and confirm it is still on.

Get an IRS Identity Protection PIN

It stops anyone else from filing a tax return under your Social Security number.

Check it yourself

Check whether you were affected

Most people in a breach like this do not need an engagement. They need to know whether their address is in it, and when it turns up somewhere new. HackNotice does both, free: an Instant Check now, alerts after.

HackNoticeRuns on HackNotice · ObscureIQ never sees the address you check
Run the Instant Check →
If this matters to you

Talk to us about your exposure

If you are exposed in a way that cannot be rotated away, or you are responsible for someone who is, a call establishes what is actually reachable about you and what is worth doing first. No charge for the conversation.

Request a confidential call →
Full record · 9 sections

The full breach analysis

What happened, what the company reported against what is circulating, the field-by-field record, the actor and the advisory.

  • What happened
  • Recent developments
  • Reported and circulating
  • Data points exposed
  • Downstream risk
  • Principal risk advisory
  • Threat actor
  • Background
  • Data context
No sign-in · nothing is recorded
What happened

How this breach happened

Glendale Obstetrics and Gynecology, PC, an all-female women's health practice based in Glendale, Arizona, identified a network disruption on October 25, 2025 affecting a portion of its digital environment. The practice engaged outside cybersecurity specialists and confirmed that certain files were acquired by an unauthorized individual. The SafePay ransomware group claimed responsibility on November 11, 2025 by listing the clinic on its Tor-based dark-web leak site and threatening to release patient data unless ransom negotiations were initiated. Glendale OBGYN reported the breach to the U.S. Department of Health and Human Services on December 24, 2025.

The breach affected approximately 34,000 individuals based on records indexed by breach-tracking services. Compromised fields included names, addresses, dates of birth, driver's license information, Social Security numbers, medical information, and health insurance information. As an obstetrics and gynecology practice, the underlying records exfiltrated by the attackers also include reproductive-health treatment records, prenatal care histories, gynecological diagnoses, and ultrasound and imaging records typical of an OBGYN operation, beyond the more limited field set surfaced publicly.

For affected patients, the practical risk profile is unusually severe and durable because of the combination of identity-fraud exposure with reproductive-health-specific sensitivity. The combination of name, date of birth, address, and Social Security number is a strong base for synthetic identity fraud and fraudulent credit applications. Inclusion in the dataset confirms a women's-health care relationship and may reference pregnancy status, gynecological diagnoses, or reproductive-health decisions, which can support targeted scams referencing real care episodes. The sensitivity of reproductive-health information also raises concerns about coercive abuse, employer or partner targeting, and discrimination, particularly for patients who may not have shared their care history with family members or employers. Affected patients should freeze credit at all three U.S. bureaus, monitor health-insurance statements, and treat unsolicited contact referencing Glendale OBGYN, prenatal care, or related services with caution.

Recent developments

What has happened since the breach

Glendale OBGYN identified a network disruption on October 25, 2025 affecting a portion of its digital environment. The practice took immediate steps to secure the environment and engaged outside cybersecurity specialists. The SafePay ransomware group publicly claimed responsibility on November 11, 2025 by listing Glendale OBGYN on its Tor-based dark-web leak site and threatening to release stolen patient data unless ransom negotiations were initiated. Glendale OBGYN reported the breach to the U.S. Department of Health and Human Services on December 24, 2025 and began identifying contact information for direct notification of affected individuals. Class-action investigations by U.S. plaintiff law firms began organizing in late December 2025.

Reported and circulating

What was reported vs. what is circulating

The company's notice

Reported

Status
Confirmed by the company and a regulator
Filed with
HHS OCR breach portalHHS OCR breach portal, 2025-12-24
Affected
Not disclosed
Fields named
Not listed in the notice
Observed by ObscureIQ

Circulating

Observed as of
2026-10-28
Breach date
2025-11-13
Volume
34,211 rows
Fields seen
4Social Security number, email address, phone number, home address

The score is built only on what is seen circulating.

Data points exposed

Every exposed field, and how long it stays useful

FieldShelf lifeIn noticeCirculating
Social Security NumberLasts for yearsNoYes
Email AddressLasts for yearsNoYes
Phone NumberFades over a few yearsNoYes
Home addressLasts for yearsNoYes

Shelf life is how long a field stays useful to someone holding it. A password expires fast. A government ID number or a date of birth lasts for years. An address stays useful long after it stops being current.

Downstream risk

How attackers can use this data

Extremely sensitive. Exposure can enable identity theft, medical fraud, and serious privacy harm tied to reproductive and gynecological care, including targeted scams or coercive abuse.

Principal risk advisory

Risks for executives and other high-profile people

A healthcare-linked breach: exposure ties a named individual to a provider relationship and, where clinical or insurance data is present, to conditions and treatment. For a high-profile principal this is targeting-grade, not merely identity-theft-grade: the combination lets an adversary locate, impersonate, or pressure the principal with little additional work.

Threat actor

Who is behind this breach

Attributed to SafePay.

Profile of SafePay and the other breaches in our records tied to it →

Background

About the company

Glendale Obstetrics and Gynecology, PC (Glendale OBGYN) is an all-female obstetrics and gynecology practice with several locations in Arizona, headquartered in Glendale. The practice provides comprehensive women's health services including obstetrics, gynecology, prenatal care, ultrasounds, well-woman exams, and related reproductive-health services. As a HIPAA-regulated specialty medical practice focused on women's health, Glendale OBGYN maintains highly sensitive patient identity, contact, insurance, billing, appointment, and reproductive-health treatment records, alongside diagnostic imaging, prenatal care histories, and gynecological diagnoses typical of an obstetrics and gynecology operation.

Data context

Why the company holds this data

OBGYN practices collect highly sensitive patient identity, contact, insurance, billing, appointment, and reproductive-health treatment records across specialty care workflows.

SafePay →Ransomware / ExtortionHealthcarePhysician Practice & ClinicPrivate company2025

About this record

The company has confirmed the breach but has not disclosed how many people are affected. The circulating figure, 34,211 rows, is what has been observed in the published data. Circulation was last verified on 2026-10-28. The score was last computed on 2026-10-28. Scores come from the Breach Risk Index, which rates what the exposed fields still let an attacker do, not how large the breach was. Breach records change as evidence does. If you hold a notice, a filing or a dataset observation this page does not reflect, report a correction.

ObscureIQ · Circulating breach record How the Index works · Contact MMXXVI