Baltimore Medical System Data Breach (2025)
Community healthcare provider delivering primary and preventive care.
Could reach Severe if more of this data surfaces.
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. Childhood minimum is an observed minimum on data that includes children; read it as a low floor, because the rating does not yet count how long a child carries the exposure. 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 →
Includes data that cannot be reissued or taken back. A changed password does not reach it.
- Circulating
- 637,627 rows
- Field types
- 5 seen · 12 in the notice
- Breach date
- Jul 2, 2025
- Observed as of
- Oct 27, 2026
- Attributed
- Brain Cipher
- Vector
- Ransomware / Extortion
Breach12 months laterListed in breach cataloguesObserved · scored
What data was exposed
How this data can be used against you
Physical targeting
Links a named person to where they live or go.
Identity
No usable identity package in what circulates.
Social engineering
Contact details only, with too little context for a convincing approach.
Account access
No usable login material in what circulates.
Financial
No usable financial detail in what circulates.
Coercion
Nothing in what circulates is sensitive enough for leverage.
Health
No medical detail in what circulates.
Crypto
Nothing in what circulates is tied to crypto assets.
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 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.
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 →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
How this breach happened
Baltimore Medical System, the largest Federally Qualified Health Center in Maryland, suffered a ransomware attack between July 2 and July 20, 2025. The Brain Cipher ransomware group claimed responsibility on September 16, 2025 by listing BMS on its dark-web leak site and posting data samples reportedly exceeding 800 GB, including what appeared to be database and file-system backups from BMS servers. BMS publicly disclosed the incident on September 26, 2025 and began notifying affected individuals.
The breach affected about 638,000 records across the BMS network. The data included names, contact details, birth dates, Social Security numbers, medical record and patient identification numbers, medical and treatment information, lab results, Medicare and Medicaid identifiers, health insurance and claims details, and financial account information.
What has happened since the breach
Baltimore Medical System discovered suspicious network activity in late summer 2025 and engaged third-party cybersecurity specialists to investigate. The forensic review concluded that an unauthorized actor accessed and copied files between July 2 and July 20, 2025. BMS issued an initial public notice on September 26, 2025 and began an extended file-review process to identify affected individuals. Notification letters were mailed in two waves, with the second beginning on or around April 2, 2026. The Brain Cipher ransomware group publicly claimed responsibility on September 16, 2025 by listing BMS on its dark-web leak site and posting samples reportedly exceeding 800 GB.
What was reported vs. what is circulating
Reported
- Status
- Count confirmed by a regulator
- Affected
- 501 people, approximately
- Fields named
- 12Social Security number, phone number, full name, home address, date of birth, medical diagnosis, treatment information, lab results, medical record number, health insurance information, insurance claims history, financial account
Circulating
- Observed as of
- Oct 27, 2026
- Breach date
- Jul 2, 2025
- Volume
- 637,627 rows
- Fields seen
- 5Social Security number, email address, phone number, full name, home address
1 field: email address.
8 fields: date of birth, medical diagnosis, treatment information, lab results, medical record number, health insurance information, insurance claims history, financial account.
If the fields named only in the notice surface, this record would be rated Severe.
Counts are not compared: the notice counts people, approximately, the dataset counts rows. The score is built only on what is seen circulating.
Every exposed field, and how long it stays useful
| Field | Shelf life | In notice | Circulating |
|---|---|---|---|
| Social Security Number | Lasts for years | Yes | Yes |
| Email Address | Lasts for years | No | Yes |
| Phone Number | Fades over a few years | Yes | Yes |
| Full Name | Lasts for years | Yes | Yes |
| Home address | Lasts for years | Yes | Yes |
| Date of Birth | Lasts for years | Yes | Not seen |
| Medical Diagnosis | Lasts for years | Yes | Not seen |
| Treatment information | Lasts for years | Yes | Not seen |
| Lab results | Fades over a few years | Yes | Not seen |
| Medical Record Number | Lasts for years | Yes | Not seen |
| Health insurance information | Lasts for years | Yes | Not seen |
| Insurance Claims History | Lasts for years | Yes | Not seen |
| Financial account | Lasts for years | Yes | Not seen |
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.
How attackers can use this data
Severe risk. Combines identity theft, insurance fraud, and medical privacy exposure. Community-health settings may also affect vulnerable populations who are easier to target with convincing scams.
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.
Who is behind this breach
Attributed to Brain Cipher.
Profile of Brain Cipher and the other breaches in our records tied to it →
About the company
Baltimore Medical System (BMS) is the largest Federally Qualified Health Center (FQHC) in the state of Maryland, headquartered in Baltimore. The nonprofit healthcare provider operates a network of community-based health centers across Baltimore City and Baltimore County, providing comprehensive primary care, pediatrics, women's health, dental services, and behavioral health to underserved and low-income residents. As an FQHC, BMS receives federal funding to deliver care regardless of patients' ability to pay, and serves approximately 90,000 patients across its facilities. The organization handles substantial volumes of protected health information including patient identity, insurance, billing, and treatment records, alongside Medicare and Medicaid identifiers used for federal-program billing.
Why the company holds this data
Community clinic networks collect patient identity, contact, insurance, billing, and treatment records across primary and specialty care services.
About this record
The reported figure, 501 people, approximately, is what the company or a regulator disclosed. The circulating figure, 637,627 rows, is what has been observed in the published data; the two measure different things and are not compared as equals. Circulation was last verified on Oct 27, 2026. The rating was last computed on Oct 27, 2026. 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.