Skip to content
Cyber Threat
CTI Academy Sponsor CTI Academy
Ransomware victim Healthcare

LEO Pharma A/S

Listed by N0n on · organisation based in Denmark

Disclosed
Nov 12, 2026
Leak-site listing date
Threat group
N0n
309 victims listed
Country
Denmark
#38 most targeted
Sector
Healthcare

ThreatAI analysis

Compiled from this incident record and the threat intelligence profile for N0n. Figures and technique mappings are quoted from the source data, not inferred.

About the N0n group

N0n has listed 116 victims since September 2026.

How N0n is documented to operate

Valid Accounts T1078 Stealth Persistence

Adversaries may obtain and abuse credentials of existing accounts as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion. Compromised credentials may be used to bypass access controls placed on various resources on systems within the network and may even be used for persistent access to remote systems and externally available services, such as VPNs, Outlook Web Access, network devices, and remote desktop. Compromised credentials may also grant an adversary increased privilege to specific systems or access to restricted areas of the network.

Mitigations: Password Policies, User Account Management, Privileged Account Management, Multi-factor Authentication, Application Developer Guidance, User Training

MITRE ATT&CK reference
Command and Scripting Interpreter T1059 Execution

Adversaries may abuse command and script interpreters to execute commands, scripts, or binaries. These interfaces and languages provide ways of interacting with computer systems and are a common feature across many different platforms. Most systems come with some built-in command-line interface and scripting capabilities, for example, macOS and Linux distributions include some flavor of Unix Shell while Windows installations include the Windows Command Shell and PowerShell. There are also cross-platform interpreters such as Python, as well as those commonly associated with client applications such as JavaScript and Visual Basic.

Mitigations: Limit Software Installation, Code Signing, Disable or Remove Feature or Program, Execution Prevention, Antivirus/Antimalware, Privileged Account Management

MITRE ATT&CK reference
Boot or Logon Autostart Execution T1547 Persistence Privilege Escalation

Adversaries may configure system settings to automatically execute a program during system boot or logon to maintain persistence or gain higher-level privileges on compromised systems. Operating systems may have mechanisms for automatically running a program on system boot or account logon. These mechanisms may include automatically executing programs that are placed in specially designated directories or are referenced by repositories that store configuration information, such as the Windows Registry. An adversary may achieve the same goal by modifying or extending features of the kernel.

MITRE ATT&CK reference
Obfuscated Files or Information T1027 Stealth

Adversaries may attempt to make an executable or file difficult to discover or analyze by encrypting, encoding, or otherwise obfuscating its contents on the system or in transit. This is common behavior that can be used across different platforms and the network to evade defenses. Payloads may be compressed, archived, or encrypted in order to avoid detection. These payloads may be used during Initial Access or later to mitigate detection. Sometimes a user's action may be required to open and Deobfuscate/Decode Files or Information for User Execution. The user may also be required to input a password to open a password protected compressed/encrypted file that was provided by the adversary.

Mitigations: Audit, Behavior Prevention on Endpoint, User Training, Antivirus/Antimalware

MITRE ATT&CK reference
Data Staged T1074 Collection

Adversaries may stage collected data in a central location or directory prior to Exfiltration. Data may be kept in separate files or combined into one file through techniques such as Archive Collected Data. Interactive command shells may be used, and common functionality within cmd and bash may be used to copy data into a staging location. In cloud environments, adversaries may stage data within a particular instance or virtual machine before exfiltration. An adversary may Create Cloud Instance and stage data in that instance.

MITRE ATT&CK reference

MITRE ATT&CK techniques attributed to N0n across its recorded activity, not a finding about how LEO Pharma A/S was reached.

Incident analysis

LEO Pharma A/S was listed by N0n ransomware, a group with 309 victims recorded in this database. The listing appeared on the group's leak site on November 12, 2026.

LEO Pharma A/S is based in Denmark and operates in the Healthcare sector. Denmark ranks #38 worldwide for ransomware disclosures, with 78 victims in this database.

Sector context. Healthcare organisations are high-value ransomware targets because patient data is extremely sensitive, regulatory penalties for breaches are severe, and operational downtime can threaten patient safety — all factors that increase ransom payment pressure.

N0n typically follows a double extortion model: data is exfiltrated from the victim's systems before files are encrypted, so the victim faces two demands at once — pay to restore access, and pay to keep stolen data unpublished. The leak site, where this listing appeared, is the lever for the second demand.

Source. Public leak-site disclosures aggregated via the ransomware.live API. The disclosure date is when the listing was published, which can differ from the date of compromise. This site does not publish or link to stolen data. Last updated .

Frequently asked questions

Was LEO Pharma A/S attacked by ransomware?

Yes. LEO Pharma A/S was listed as a victim of the N0n ransomware group on November 12, 2026. The organisation is based in Denmark and operates in the Healthcare sector. The disclosure appeared on the group's dark web leak site.

Which ransomware group attacked LEO Pharma A/S?

LEO Pharma A/S was attacked by N0n ransomware. N0n is one of the most active ransomware groups, having claimed 309 victims globally. The group typically employs a double-extortion model: encrypting the victim's files and threatening to publish stolen data.

When did the LEO Pharma A/S ransomware attack occur?

The ransomware attack on LEO Pharma A/S was disclosed on November 12, 2026. This date reflects when the victim was published on the threat group's leak site, which may differ from the actual date of initial compromise.

What data was stolen in the LEO Pharma A/S ransomware attack?

The specific data stolen from LEO Pharma A/S has not been independently verified by this platform. Ransomware groups typically exfiltrate data before encrypting systems and use the threat of publication to pressure victims. As a Healthcare organisation, LEO Pharma A/S likely held patient records, medical data, and personally identifiable information (PII).

How can organisations protect against N0n attacks?

To defend against N0n and similar threat actors, organisations should: maintain regular offline backups tested for restoration; implement network segmentation to limit lateral movement; deploy multi-factor authentication on all remote access; use endpoint detection and response (EDR) tools; conduct regular phishing and security awareness training; and monitor threat intelligence feeds for indicators of compromise (IOCs) associated with active groups.