Eli Lilly Ransomware Claim by N0n (Nov 2026)
High-impact breach
Claim Risk Profile
N0n allegedly claims 16M prescription records from Eli Lilly. Unverified leak site post - see our analysis of the threat, exposure risks and next steps.
What to do
This claim is unverified. It comes from a post on a leak site or forum, and Yazoul has not confirmed it.
- If true, files taken from Eli Lilly and Company may be published, and staff, customers and partners could be targeted with phishing or fraud that uses them.
- If you deal with Eli Lilly and Company, wait for its own statement before acting, and treat unexpected messages that mention this incident with suspicion.
- The group behind the claim: N0n, 26 claims
Leak Site Screenshot
Screenshot captured at time of discovery. Image blurred to protect victim PII.
Claim Summary
The ransomware group tracked as N0n has allegedly listed Eli Lilly and Company, a US pharmaceutical and healthcare organization, on its dark web leak site. According to the threat actor, the listing was initially posted anonymously as “Company #202” on 2026-11-09 before being attributed to the victim. The group claims to have exfiltrated and published data after an alleged non-payment, tagging the entry as “[NOT PAID - EXPOSED]”.
The claimed attack date is 2026-11-09. No independent confirmation of a breach, data theft, or extortion negotiation exists at the time of writing. Everything below reflects the threat actor’s unverified assertions.
Threat Actor Profile
N0n is a low-profile ransomware and data extortion operation with no established public research footprint. Open-source intelligence provides no confirmed victim count, no documented tooling, and no published tactics, techniques, or procedures (TTPs) attributable to this group. Its use of an anonymous “Company #202” placeholder before naming a victim is a common pressure tactic among smaller or newer extortion crews seeking to build notoriety.
Because the group has no verifiable track record, its credibility should be treated as low to unknown. Groups with thin histories frequently exaggerate data volumes, inflate record counts, or recycle previously leaked datasets to appear more capable than they are. No YARA rules or detection signatures specific to N0n are publicly available; defenders should rely on generic ransomware and data exfiltration detections rather than actor-specific indicators.
Alleged Data Exposure
According to the threat actor, the purported dataset includes:
- Patient-level prescription fill claims for neurology, immunology, and inflammation products, claimed at 16,025,727 rows covering 1,243,661 distinct patients, with payer, copay, and diagnosis detail.
- Prescriber volumes and a prescriber master file, claimed to contain 7,625,229 distinct NPI numbers with names, addresses, and phone numbers.
These figures are unverified and internally inconsistent in scale relative to the patient count. Yazoul Security has not reviewed, validated, or reproduced any of this data, and we do not host, link to, or distribute leaked material.
Potential Impact
If the claim is accurate, the exposure would involve sensitive patient health information and prescriber identifiers, raising potential HIPAA and state privacy law implications. Affected individuals could face targeted phishing, medical identity fraud, or insurance fraud. Prescriber data could enable business email compromise or social engineering against healthcare providers.
However, ransomware groups routinely overstate scope to increase pressure. The true impact cannot be assessed until Eli Lilly or regulators confirm an incident.
What to Watch For
- Official statements from Eli Lilly or regulatory disclosures confirming or denying a breach.
- Breach notification filings with state attorneys general or HHS.
- Evidence of phishing or fraud campaigns referencing prescription or prescriber data.
- Updates to the N0n leak site, including data samples or deadline changes.
Organizations in healthcare and pharma should review third-party access controls, monitor for credential abuse, and validate backup integrity. See our advisory resources for guidance.
Disclaimer
This report is based solely on an unverified claim posted to a ransomware leak site. Nothing here is confirmed. Yazoul Security has not independently verified the breach, the data, or the threat actor’s assertions. The claim may be exaggerated, inaccurate, or fabricated. Treat all details as allegations pending official confirmation.