Skip to content
AI Protection
Free
Start with what’s already out there

We’ll show you your exposure before you pay anything.

Run a free scan

Run free scans

Data broker scan See which data brokers list your personal info All free tools
Family Safe Phrase

The card families use to shut down voice-clone calls.

Get the card

Breaches we’re tracking

What was exposed in each one, and what to do next.

All tracked breaches
No letter, but worried?

Enter your email and we’ll tell you which breaches include you.

Check my email
Scams in your state

The local patterns, the agencies to call, and printable posters.

Pick your state
Data Breach / Mountrail County Medical Center · Updated October 26, 2026 Independent coverage, not a communication from Mountrail County Medical Center

Mountrail County Medical Center Data Breach: What Happened and What You Should Do

Mountrail County Medical Center disclosed a data breach affecting 24,447 people, as reported by Mountrail County Medical Center to the Texas Attorney General. Here's what is currently known about the incident, what information may have been exposed, and steps you can consider taking.

Notification underway Sources listed below
Breach snapshotUpdated October 26, 2026
Company
Mountrail County Medical Center
People affected
24,447

Mountrail County Medical Center reported 24,447 people affected in total, including 456 Texas residents, in its report to the Texas Attorney General (published October 16, 2026).

Incident date
December 2 – December 18, 2025
Discovered
On or about December 18, 2025
Disclosed
October 2026
Information exposed
Possibly: Name, Social Security number, Health information, Date of birth
Status
Notification underway

Texas AG report published October 16, 2026; Massachusetts letter 2026-1782; Aesto says it has no evidence the information has been misused.

What happened in the Mountrail County Medical Center breach?

How the attacker got in

Unauthorized access to a limited portion of vendor Aesto, LLC's Amazon Web Services environment; the threat actor compromised accounts and altered AWS Lambda functions, according to Aesto's attestation.

Timeline of what is known

  1. 01December 2 – December 18, 2025Unauthorized access
  2. 02On or about December 18, 2025Breach discovered
  3. 03October 2026Breach disclosed publicly
  4. 04By U.S. mail (date not stated in public filings); Aesto notified covered entities June 26, 2026Affected individuals notified

Dates come from the sources listed at the bottom of this page. Separate events are kept separate; where a date has not been disclosed, it says so.

What information was exposed?

The categories below come from Mountrail County Medical Center's disclosure and the sources listed on this page. Each is labeled by what the evidence supports. Categories not mentioned in any source are not listed, even if they are common in similar breaches.

Exposed May have been exposed Access not confirmed

Name

Names (Texas AG report).

May have been exposed

Social Security number

Social Security numbers (Texas AG report).

May have been exposed

Health information

Medical information (Texas AG report).

May have been exposed

Date of birth

Dates of birth (Texas AG report).

May have been exposed

Why this information matters

The risks below are the ones associated with the categories of information involved in this breach. This describes how exposed information can be used in general. It does not state that any of this has happened with data from this incident.

Information from one breach can sometimes be combined with information from other breaches or public sources. A name and email address on their own are limited. Paired with a date of birth from one leak and an address from a people-search site, they become enough to answer a security question or make a scam call sound informed.

Whether the data from this breach has been sold, shared, or used is not known unless a source on this page says so. Where that is documented, it appears in the "What happened" section above.

If you were affected, consider doing these things now

Practical steps for this breach, in rough order of priority. None of these require buying anything. Monitoring services, including ours, are one option among several.

  1. 01Consider a free credit freeze with Equifax, Experian, and TransUnion; it blocks new accounts in your name and is free to place and lift.
  2. 02Request an IRS Identity Protection PIN to help stop someone else from filing a tax return with your Social Security number.
  3. 03Review medical bills, explanation-of-benefits statements and credit reports for activity you do not recognize.
  4. 04Treat calls, texts, or emails that mention this incident with suspicion; call back only on a number from the written notice or the organization's official website.

AI Protection

Monitoring, alerts, and recovery help for what comes after a breach.

A breach puts information you can't take back into circulation. AI Protection watches for it being misused, alerts you when something changes, and helps you recover if something goes wrong. It cannot undo the breach or retrieve data an attacker already holds.

Get AI Protection Plans from $7 per month. Cancel anytime.

How one breach can contribute to a larger exposure footprint

A possible risk pattern, not a description of this incident. Each step is something that can happen after a breach. Nothing here states that it has happened with data from this incident.

Illustrative pattern
  1. Step 1

    One breach

    A single company's records are accessed without authorization.

  2. Step 2

    Personal information is exposed

    Some categories can be changed afterward. Others, like a name or date of birth, can't.

  3. Step 3

    It may remain accessible

    Copies of breached data can persist well beyond the original incident.

  4. Step 4

    Sources can be combined

    Fragments from different breaches and public sources may be assembled into a fuller profile.

  5. Step 5

    More targeted attempts

    A fuller profile can make fraud, impersonation, phishing, or social engineering attempts more convincing.

A breach is an event. Exposure can last longer.

A password can be reset and a card reissued. Some information can't be replaced, and that is the part that stays useful to someone attempting fraud later. This does not mean fraud will occur. It means the risk does not close when the news cycle does.

Involved in this breach and hard to change

NameMay have been exposed
Social Security numberMay have been exposed
Health informationMay have been exposed
Date of birthMay have been exposed

What Mountrail County Medical Center has done so far

Only actions the company has announced or that are documented in the sources below. If something you'd expect to see isn't here, it hasn't been announced as of the last update.

Sources

Primary sources first: company disclosures, regulator and attorney general filings, SEC filings, court documents. News reporting is listed as secondary. Where reports conflict, the conflict is noted in the "What happened" section rather than resolved silently.

Primary 01
Mountrail County Medical Center · October 2026
Secondary 02
Massachusetts Office of Consumer Affairs and Business Regulation · October 2026
Secondary 03
Office of the Texas Attorney General · October 16, 2026

Last updated October 26, 2026 · First published October 26, 2026

Questions about the Mountrail County Medical Center breach

Mountrail County Medical Center patient information was involved in a security incident at Aesto, LLC, a vendor to HIPAA covered entities. Aesto says it experienced a network security incident on or about December 18, 2025 affecting a limited portion of its Amazon Web Services (AWS) environment, and after a forensic investigation and manual document review it confirmed on May 26, 2026 that information stored on its network may have been accessed or acquired by an unauthorized actor between on or about December 2 and December 18, 2025. Aesto notified affected covered entities on June 26, 2026.

According to the sources on this page, 24,447 people, as reported by Mountrail County Medical Center to the Texas Attorney General. Mountrail County Medical Center reported 24,447 people affected in total, including 456 Texas residents, in its report to the Texas Attorney General (published October 16, 2026).

Unauthorized access is reported to have occurred December 2 – December 18, 2025.

The company says it discovered the breach on On or about December 18, 2025. It disclosed the incident publicly on October 2026.

The company has not confirmed which categories were exposed. May have been exposed: Name, Social Security number, Health information, Date of birth. See the full list with status labels above.

The most reliable way is a notice from Mountrail County Medical Center itself. Aesto notified covered entities on June 26, 2026; individual notices were sent by U.S. mail. Be cautious of unsolicited messages claiming to confirm you were affected; verify through a contact method you already have.

Start with the checklist above: follow the company's instructions, watch for phishing that references the breach, monitor the affected accounts, and consider a credit freeze if identifiers like a Social Security number are confirmed involved.

Aesto notified covered entities on June 26, 2026; individual notices were sent by U.S. mail.

Yes. Information that can't be changed, such as a name, date of birth, or Social Security number, can remain useful for fraud attempts long after the incident. That is a general risk, not a statement that data from this breach has been used.

AI Protection is an identity protection service that includes identity monitoring, removal of exposed information, restoration support, up to $5m in identity theft insurance per person, social media monitoring. It is independent of Mountrail County Medical Center and cannot reverse a breach.

Take control of what happens next.

Monitoring for misuse of your information, alerts when something changes, and a real person to call if something goes wrong. Plans from $7 per month. Cancel anytime.