Acadia Healthcare Company, Inc. Data Breach Notice (Washington Attorney General): What Was Exposed & What To Do
The Acadia Healthcare Company, Inc. Data Breach Notice (Washington Attorney General) (reported November 13, 2026) exposed Name, Social Security Number, Driver's License or Washington ID Card Number and Health Insurance Policy or ID Number belonging to roughly 1093 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.
Healthcare providers remain frequent targets for cyber incidents because the records they hold combine identity details with clinical and insurance data. Against that backdrop, Acadia Healthcare Company, Inc. has notified regulators of a data breach affecting residents in multiple states, including a formal notice to Washington authorities.
According to a filing reported to the Washington State Attorney General on November 13, 2026, Acadia Healthcare Company, Inc. informed Washington residents that a data breach occurred, with the incident itself dated March 21, 2026. The Washington notice lists 1,093 people affected and identifies exposed information that includes names, Social Security numbers, driver’s license or Washington ID card numbers, health insurance policy or ID numbers, and medical information. Parallel notices were filed the same day in other states. The episode matters because the data types named support identity theft, insurance fraud, and misuse of sensitive health details.
Inside the incident
Public detail in the Washington Attorney General filing is limited to the essentials. Acadia Healthcare Company, Inc. notified Washington residents of a data breach in a filing reported on November 13, 2026. That notice places the incident on March 21, 2026 and states that 1,093 people were affected. The information described as exposed includes name, Social Security number, driver’s license or Washington ID card number, health insurance policy or ID number, and medical information.
How the intrusion occurred, what systems were involved, how long unauthorized access lasted, and whether data was exfiltrated in bulk or accessed in place are not described in the provided facts. No threat actor is attributed in those materials.
Separate breach-notice filings by an organisation of the same name appear on the same reporting date and should be read as distinct notices, not combined totals. A California Attorney General breach notification was filed November 13, 2026, with the count not stated in that filing. An Oregon Department of Justice breach notification was filed November 13, 2026, with the count not stated in that filing. A South Carolina Department of Consumer Affairs breach notification was filed November 13, 2026 and lists 12,813 people affected. A Vermont Attorney General breach notification was filed November 13, 2026 and lists 73 people affected. Counts from these filings must not be added together; each reflects its own notice.
How a breach like this happens
Incidents that lead to notices naming identity and medical data often follow familiar patterns, though none of the following should be read as a confirmed method for this case. Attackers commonly gain an initial foothold through stolen or guessed remote-access credentials, phishing that harvests employee logins, exposed remote services, or unpatched software. Once inside, they may move laterally to systems that store patient registration, billing, or electronic health information.
From there, data can be copied, encrypted for ransom, or both. Discovery sometimes comes from unusual outbound traffic, endpoint alerts, or later evidence that records appear in criminal markets. Organisations then investigate, determine what categories of data were involved, and issue state notices when statutory thresholds are met. The gap between an incident date and public filing can reflect the time needed for forensics, legal review, and coordinated multi-state notification. None of that sequence is spelled out for this event beyond the dates and data categories in the filings.
Who is Acadia Healthcare Company, Inc.?
Acadia Healthcare Company, Inc. is a large U.S. behavioural health and healthcare services organisation. Companies in this sector typically operate or manage treatment facilities, outpatient programs, and related clinical services. In the ordinary course of care they collect and retain demographic identifiers, government ID numbers for eligibility and compliance, insurance policy details for billing, and clinical or treatment-related medical information.
A breach affecting such an organisation is consequential because the same files that support legitimate care also enable impersonation, fraudulent claims, and exposure of private health matters. Patients, former patients, and sometimes employees or guarantors may all appear in the same ecosystems of registration, billing, and clinical systems.
What was likely exposed
For the Washington notice, the filing explicitly names the following as among the information exposed: name, Social Security number, driver’s license or Washington ID card number, health insurance policy or ID number, and medical information. Those categories are stated in the disclosure and should be treated as the confirmed list for that notice.
Exact field-level contents beyond those labels—such as full clinical narratives, specific diagnoses, or the precise format of insurance identifiers—are not further detailed in the facts provided. Other state filings referenced above do not, in the materials given, repeat a full data-type inventory; where counts are given they are separate (South Carolina 12,813; Vermont 73; California and Oregon counts not stated). Readers should rely on any individual notice they receive rather than assuming every state’s population saw identical data elements.
Why it matters
Social Security numbers and driver’s license or state ID numbers are durable identity keys. Combined with a real name, they can support new-account fraud, tax-related identity theft, and synthetic identity schemes. Health insurance policy or ID numbers can be misused for fraudulent billing or to obtain services in someone else’s name, which may surface later as incorrect claims history or coverage disputes. Medical information, even at a summary level, is sensitive: its exposure can cause privacy harm, stigma, or targeted scams that reference real treatment details to appear legitimate.
For the organisation, multi-state notification on a single reporting day indicates a broad compliance response and potential follow-on costs in investigation, patient support, and regulatory scrutiny. For affected people, the practical risk is long-lived: identity and insurance identifiers cannot be “changed” as easily as a password, so monitoring and documentation become ongoing tasks rather than a one-time fix.
What to do if you're exposed
If you receive a notice from Acadia Healthcare Company, Inc., or if you were a patient or guarantor in the relevant period, treat the named data types as potentially compromised. Keep the notice. Consider placing a fraud alert or credit freeze with the major credit bureaus, and monitor credit reports and insurance explanations of benefits for accounts or claims you do not recognize. If a Social Security number was involved, review IRS and Social Security account activity where you have access. Be wary of unsolicited calls or messages that reference your care or the breach and ask for passwords, payments, or further identifiers.
Use only official channels listed on a notice you received, and document dates of any suspicious activity. As a further check, you can run a free exposure scan of your email address to see whether that address has already appeared in known breach datasets, which may help you prioritise password changes and monitoring on related accounts.
AICompiled with AI assistance from public sources and published under our editorial standards.
How this breach connects
More recent breaches
Prism Medical Products, LLC Data Breach Notice (Washington Attorney General)Dexcom, Inc. Data Breach Notice (Washington Attorney General)Levin Data Breach Notice (Washington Attorney General)PCH Digital, LLC Data Breach Notice (Washington Attorney General)Latest breaches
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.