LiveBreach Intelligence: data breaches, leaks & ransomware, tracked as they surfaceOngoing protection: GalaxyWarden →
Recent BreachesData breach tracker
AnalysisInside the ARTEX toolkit, and the US outage weekTimeline

Recent Breaches › Dorsata, Inc. (Metabase) Data Breach Notice (Washington Attorney General)

CRITICAL severityConfirmedHow we verify

Dorsata, Inc. (Metabase) Data Breach Notice (Washington Attorney General): What Was Exposed & What To Do

The Dorsata, Inc. (Metabase) Data Breach Notice (Washington Attorney General) (reported October 21, 2026) exposed Name, Health Insurance Policy or ID Number, Medical Information and Protected Health Information owned or licensed by a HIPAA covered entity belonging to roughly 3713 people. If you have an account with them, your information may now be circulating on the open web and with data brokers. Here’s exactly what happened, how to check if you were affected, and what to do next.

Dorsata, Inc. (Metabase) Data Breach Notice (Washington Attorney General)

Occurred August 10, 2026 · publicly disclosed October 21, 2026. Approximately 3713 people affected.

CRITICAL
Severity
3713
People affected
4
Data types exposed
October 21, 2026
Disclosed
Severity & verification
CRITICAL severityConfirmed
Exposes medical data.
Corroborated by an official disclosure or a verified breach feed.
Check your exposure
3713 accounts were exposed here. We can’t confirm any single incident against the sources we search — but we can show you every leak and listing tied to your email. 15-sec check, no card.

By running your scan you agree to the Terms and Conditions and the Privacy Policy, and to GalaxyWarden emailing you the results of this scan.

Healthcare and health-technology firms remain frequent targets in today’s breach landscape because the records they hold combine identity data with clinical and insurance details that retain value long after an incident. Against that backdrop, a notice filed with the Washington State Attorney General shows that Dorsata, Inc. (Metabase) experienced a data security incident that reached thousands of individuals and involved protected health information.

According to the filing reported on October 21, 2026, the company notified Washington residents that information including names, health-insurance policy or ID numbers, medical information, and protected health information owned or licensed by a HIPAA-covered entity was exposed. The same notice places the incident itself on August 10, 2026, and states that 3,713 people were affected. The disclosure supplies the core public facts; further technical detail remains limited.

What happened

Dorsata, Inc. (Metabase) submitted a data-breach notice to the Washington State Attorney General that was reported on October 21, 2026. The filing states that the incident occurred on August 10, 2026, and that 3,713 individuals were affected. The notice lists the exposed data categories as name, health insurance policy or ID number, medical information, and protected health information owned or licensed by a HIPAA-covered entity.

Public detail beyond those points is limited. The filing does not describe the attack method, the systems involved, how long unauthorized access lasted, or whether data were exfiltrated, viewed, or otherwise misused. No threat actor is named in the disclosed record.

How a breach like this happens

Incidents that expose health-related records commonly begin with one of several well-understood paths. Attackers may obtain valid credentials through phishing or credential-stuffing, exploit an unpatched remote-access or application vulnerability, or abuse a misconfigured cloud storage or analytics platform. Once inside, they often move laterally to locate databases or exports that contain patient, member, or customer files.

In environments that support clinical or insurance workflows, those files frequently include identifiers linked to medical or policy data. Even when encryption or access controls exist, a compromised account with sufficient privileges can defeat them. Organizations typically discover such events through internal monitoring, law-enforcement notification, or external reports; the precise discovery path in any single case is often not stated in regulatory notices. No specific group is attributed in the Dorsata filing, so the general patterns above are background only and do not describe the method used here.

Dorsata, Inc. (Metabase) and its sector

Dorsata, Inc., associated in the notice with Metabase, operates in the health-technology and data-analytics space that supports clinical or administrative decision-making. Firms of this type commonly process or host information on behalf of healthcare providers, payers, or other HIPAA-covered entities. That role places them inside the broader healthcare data ecosystem, where records routinely include demographic identifiers, insurance details, and clinical notes or codes.

A breach affecting such an organization is consequential because the data are both sensitive and reusable. Health-insurance identifiers and medical information can facilitate insurance fraud, targeted social engineering, or long-term privacy harm. When the records are owned or licensed by a HIPAA-covered entity, regulatory notification duties and potential downstream effects on patients and members also come into play. The Washington filing confirms that protected health information of that character was among the categories listed as exposed.

What was likely exposed

The notice explicitly names the following categories: name, health insurance policy or ID number, medical information, and protected health information owned or licensed by a HIPAA-covered entity. These are the only data types confirmed by the public filing.

Organizations that handle analytics or clinical-support data for healthcare clients typically also maintain related fields such as dates of service, provider identifiers, or contact details; however, the Dorsata notice does not confirm whether any additional elements were involved. Exact contents beyond the listed categories therefore remain unconfirmed. Readers should treat only the named types as established by the disclosure.

What's at stake

For the 3,713 people reflected in the filing, the practical risks center on misuse of identity and health-related data. A name combined with a health-insurance policy or ID number can support fraudulent claims or account takeovers. Medical information and other protected health information can be used for highly targeted phishing or can cause lasting privacy injury if circulated. Because health data do not expire in the same way as a password, the exposure window can extend for years.

For the organization, consequences include regulatory scrutiny under state breach-notification law and, where HIPAA-covered data are involved, potential federal attention, contractual obligations to covered-entity clients, and the cost of investigation, notification, and remediation. Reputational harm and loss of partner trust are additional, non-quantified effects that commonly follow such events. None of these outcomes are asserted as proven facts beyond the notice itself; they are the ordinary stakes when the listed data types leave authorized control.

What to do if you're exposed

If you believe you are among those affected, begin by reading any notice you receive from Dorsata or from a healthcare provider or insurer that uses its services; that letter should confirm what data applied to you and any services offered. Place a fraud alert or credit freeze with the major credit bureaus if insurance or identity details were involved, and monitor explanation-of-benefits statements and insurance portals for unfamiliar claims. Consider changing passwords on related health and financial accounts and enabling multi-factor authentication where available.

Keep records of any suspicious contact that references your medical or insurance information. You can also run a free exposure scan of your email address to check whether it has already appeared in known breach datasets, which may help you judge whether additional monitoring is warranted. Public detail on this incident remains limited to the Washington Attorney General filing; further updates, if any, would come from the company or regulators.

AICompiled with AI assistance from public sources and published under our editorial standards.

Editorial & sourcing policy
Recent Breaches is a breach-monitoring service and news aggregator. We do not exfiltrate, host, purchase, or redistribute stolen data, and we do not hold the data claimed in leak-site listings. Incidents are compiled from publicly accessible sources and threat-intelligence platforms and are reported as claims attributed to their source. We promptly correct or remove material shown to be inaccurate — write to support@galaxywarden.com or press@recentbreaches.com.

How this breach connects

CompanyDorsata, Inc. (Metabase) security record
52/100
DoxxScan™ · Elevated doxx risk
D+ 56Weak record

1 reported incident on record.

See Dorsata, Inc. (Metabase)’s full breach history →

More recent breaches

Prism Medical Products, LLC Data Breach Notice (Washington Attorney General)November 14, 2026Acadia Healthcare Company, Inc. Data Breach Notice (Washington Attorney General)November 13, 2026Dexcom, Inc. Data Breach Notice (Washington Attorney General)November 13, 2026Levin Data Breach Notice (Washington Attorney General)November 12, 2026

Latest breaches

Read GalaxyWarden’s full analysis of the Dorsata, Inc. (Metabase) Data Breach Notice (Washington Attorney General) →

Source: Washington State Attorney General breach notification

Verified breach

Breach listings — particularly those originating from ransomware or leak sites — are third-party claims that may be unverified, incomplete, or inaccurate. A listing does not by itself confirm that a breach occurred or that any specific data was exposed. Severity is an automated assessment, not a definitive rating. Verification status is shown where available.

Attributions to threat groups and methods reflect public reporting and, in some cases, unverified claims made by the groups themselves; they may be incomplete or later revised. Recent Breaches and GalaxyWarden are independent and are not affiliated with, and do not endorse, any company or group named on this page. This information is aggregated from public sources for awareness only and is not legal, security, or investment advice.

ShareXLinkedInFacebookRedditWhatsAppTelegram