Data Breach
N0n Ransomware Group Claims Attack on Azurity Pharmaceuticals, Exposing Patient-Level Medical and Pharmacy Claims for 2.6 Million Patients
TL;DR
A ransomware group called N0n has listed Azurity Pharmaceuticals on its leak site and claims to have already released stolen data covering roughly 2.6 million patients, including diagnosis codes, procedure codes, provider identifiers, and charged amounts. This is a reported breach, not an OCR enforcement action, and no fine has been announced.
The N0n ransomware group claims to have stolen and released 136.6 GB of patient-level medical and pharmacy claims data from Azurity Pharmaceuticals, reportedly covering 2.6 million distinct patients. Here is what compliance officers need to know now.
Reported at roughly 2.6 million distinct patients, the alleged theft of medical and pharmacy claims data from Azurity Pharmaceuticals by the N0n ransomware group is one of the larger specialty pharma breach claims of 2026, and according to the threat actor's own leak site, the data has already been released.
Warning
This is a reported breach based on a ransomware group's public claim, not a confirmed disclosure by Azurity or a regulatory finding. No OCR enforcement action or fine has been announced. However, the 'NOT PAID — EXPOSED' status on the leak site means that if the claim is accurate, affected data is already in the wild.
What the Threat Actor Claims
On November 16, 2026, the N0n ransomware group posted Azurity Pharmaceuticals to its dark web leak site and marked the listing as "NOT PAID — EXPOSED." That designation indicates the group proceeded to release the stolen data after a ransom demand went unmet, rather than holding it as ongoing leverage.
According to reporting by HookPhish and data aggregated by ransomware.live, the claimed dataset includes:
- Patient-level medical and pharmacy claims covering roughly 2.6 million distinct patients
- Diagnosis and procedure codes
- Provider identifiers
- Charged amounts
- Physician-targeting databases
- Diagnosis data warehouse extracts reportedly totaling 136.6 GB
- Commercial sales data
These figures come from the threat actor's own statements. MedComply has not independently verified the contents or authenticity of the alleged exfiltration.
Why This Matters Under HIPAA
Azurity Pharmaceuticals is a specialty pharmaceutical company. Its business model involves handling medical and pharmacy claims data, which means it routinely processes protected health information (PHI) on behalf of health plans, pharmacy benefit managers, and other covered entities. That relationship classifies Azurity as a business associate under HIPAA.
Business associates carry direct HIPAA obligations. Under 45 CFR §164.502(e), covered entities must obtain satisfactory assurances from business associates that PHI will be appropriately safeguarded. When a business associate experiences a breach, the notification chain flows in both directions.
Specifically, 45 CFR §164.410 requires a business associate to notify the covered entity of a breach of unsecured PHI without unreasonable delay and no later than 60 days after discovery. The covered entity then bears the downstream obligation to notify affected individuals under 45 CFR §164.404 and, depending on scale, to notify HHS and potentially the media under 45 CFR §164.408.
If the N0n group's claims are accurate and Azurity confirms the breach, covered entities that transmitted claims data to Azurity could be on the clock for their own notification timelines.
The Scale Problem
The reported figure of 2.6 million distinct patients is significant for two reasons.
First, any breach affecting 500 or more individuals in a single state triggers media notification requirements under 45 CFR §164.408(a). A breach at the scale claimed here would trigger that threshold many times over across multiple jurisdictions.
Second, HHS requires covered entities to report breaches affecting 500 or more individuals to the Secretary within 60 days of discovery, rather than waiting until the end of the calendar year. The diagnosis warehouse extracts alone, reportedly 136.6 GB, suggest a dataset large enough that a thorough scope analysis will take time and resources.
What Compliance Officers Should Do Now
If your organization shares claims data with Azurity Pharmaceuticals, or if you work with any business associate that processes specialty pharmacy or medical claims on your behalf, the following steps are appropriate given the current information:
Review your business associate agreement. Confirm that your BAA with Azurity includes the required breach notification provisions under 45 CFR §164.314(a). Verify the notification timelines your BAA specifies and whether they meet or exceed the regulatory floor.
Identify data flows. Determine whether your organization's patient records were included in any claims data transmitted to or processed by Azurity. This may require coordination with your pharmacy benefit manager, health plan administrator, or revenue cycle team.
Monitor for official disclosure. Azurity has not, as of this article's publish date, issued a public breach notification. Watch for a formal notification, which would start the clock on your own obligations if your patients are included.
Document your risk assessment. Under 45 CFR §164.530(j), covered entities must maintain documentation of policies, procedures, and actions taken. Even if Azurity ultimately determines that the breach does not affect your patients, documenting your assessment process is good practice and protects you in an audit.
Preserve your BAA. If Azurity does confirm a breach, your BAA is the primary document establishing each party's obligations. Ensure it is accessible and complete.
A Note on Ransomware Group Claims
It is worth stating plainly: ransomware groups are not neutral reporters of fact. Groups like N0n have financial incentives to exaggerate the scope and sensitivity of stolen data to pressure victims into paying. The 2.6 million patient figure and the 136.6 GB volume are the threat actor's own claims, posted on a leak site designed to maximize pressure.
That said, compliance officers cannot simply wait for certainty before acting. The HIPAA breach notification framework does not require proof of harm or misuse. It requires a reasonable determination of whether PHI was accessed by an unauthorized person. If Azurity's internal investigation confirms that the exfiltrated files contained unsecured PHI, the notification obligations follow, regardless of whether the data has actually been misused.
The Broader Pattern
This incident follows a recognizable pattern in healthcare ransomware: a business associate or adjacent vendor is targeted, claims or clinical data is exfiltrated, and covered entities learn about it from threat intelligence feeds before they hear from the vendor. The Change Healthcare incident in 2024 established a precedent for how disruptive and complicated downstream notifications can become at scale.
Specialty pharmaceutical companies and pharmacy data intermediaries have become attractive targets precisely because they aggregate claims data across large patient populations without always having the security posture of a large health system. That asymmetry is a risk that covered entities should factor into their vendor risk management programs.
The N0n ransomware group's claim against Azurity Pharmaceuticals, if confirmed, would represent a material HIPAA breach affecting roughly 2.6 million patients through a business associate relationship. Covered entities should immediately review their BAAs with Azurity, map relevant data flows, and prepare for potential downstream notification obligations. This is a reported breach, not an OCR enforcement action, and no fine has been announced.
Sources & citations
- HookPhish: Ransomware Group N0n Hits Azurity Pharmaceuticals Inc.Open
All content verified against official HHS guidance and the Code of Federal Regulations.
Frequently asked questions
Is this an OCR enforcement action or a fine against Azurity Pharmaceuticals?▾
What types of data does N0n claim to have stolen from Azurity?▾
How many patients are reportedly affected?▾
Does HIPAA apply to Azurity Pharmaceuticals in this context?▾
What should covered entities do if they share claims data with Azurity?▾
Related intelligence
Data Breach
Access Dental Management Discloses Ransomware Breach Affecting Hundreds of Thousands; Class-Action Investigation Launched
6 min read
Data Breach
Geisinger Health System Notifies Nearly 2,000 Patients After Employee Email Account Hacked
5 min read
Data Breach
Amplifon Discloses February 2026 Cyberattack Affecting Patients' Hearing and Medical Records, Including Social Security Numbers
6 min read
Not legal advice. medcomply.ai provides compliance intelligence for educational and operational planning. Consult qualified counsel for legal interpretation.