An unnamed U.S. healthcare organization was targeted with ransomware by the Iran-linked Pay2Key group in late February 2026. The attack's timing, which coincided with heightened military tensions between the U.S. and Iran, suggests a motive that may extend beyond financial gain. Incident response firm Beazley Security, assisted by the Halcyon Ransomware Research Center, discovered that while an enhanced version of the Pay2Key ransomware was used to encrypt systems, no data was exfiltrated. This is a significant departure from typical ransomware attacks and previous Pay2Key campaigns, indicating a potential focus on disruption or a state-directed objective. The incident highlights the growing trend of nation-state actors using ransomware as a tool for geopolitical purposes, blurring the lines between cybercrime and state-sponsored attacks.
Threat Actor: Pay2Key (Iran-linked) Target: Unnamed U.S. healthcare organization Timeline: Late February 2026 Malware: An evolved strain of Pay2Key ransomware Key Finding: Data was encrypted for impact, but no data was exfiltrated.
The lack of data theft is a crucial detail. While financially motivated ransomware groups rely on the threat of leaking stolen data (double extortion) to pressure victims into paying, this attack focused purely on encryption and disruption. This TTP is more aligned with state-sponsored destructive attacks, where the goal is to cause chaos, disrupt critical services, or send a political message. Cynthia Kaiser, a former FBI official now at Halcyon, noted this behavior is "consistent with more of an Iranian government operation that's also making money on the side."
This incident follows a pattern of Iranian cyber activity targeting U.S. critical infrastructure, including a recent destructive attack on medical device company Stryker by another Iranian group named Handala.
Forensic analysis revealed the attackers' methodology:
T1078 - Valid Accounts).T1486 - Data Encrypted for Impact).T1070.001 - Clear Windows Event Logs).Despite internal turmoil and even attempts to sell the operation in 2025, Pay2Key has remained an active and evolving threat, demonstrating resilience and continued development.
For disruptive-only ransomware attacks where no data is stolen, having tested and isolated backups is the only path to recovery.
Since an admin account was compromised, implementing PAM and JIT access would limit the attacker's ability to persist and move laterally.
Mapped D3FEND Techniques:
In a scenario like the Pay2Key attack where the primary goal is destruction via encryption, the single most important countermeasure is the ability to restore data from clean backups. Healthcare organizations must adhere to the 3-2-1 backup rule: three copies of data, on two different media types, with one copy stored offline and/or immutable. The 'offline' component is critical to defend against attackers who actively target and delete backups. This could be achieved with physical tape backups, air-gapped systems, or cloud storage with object lock/immutability enabled. The restoration process must be tested regularly to ensure its viability. This allows the organization to recover its systems and data without any reliance on the attacker, effectively neutralizing the impact of the ransomware.
The Pay2Key attackers compromised an administrative account and used it to deploy ransomware. To detect this, organizations must implement robust monitoring of all privileged accounts. This involves using a Privileged Access Management (PAM) solution to vault credentials and a SIEM to analyze activity logs. For the targeted healthcare provider, this would mean creating alerts for any privileged account activity that deviates from the norm, such as logging in at 3 AM, accessing systems outside of their responsibility, or running unusual scripts (e.g., PowerShell download cradles). This User and Entity Behavior Analytics (UEBA) approach can identify a compromised admin account during the reconnaissance or staging phase, providing a crucial window to respond before the final payload is deployed.
The attackers' attempt to clear event logs is a key behavior that can be detected. To counter this, organizations must ensure that all critical event logs (e.g., Windows Security, System, Application) are forwarded in real-time to a central, secure log repository like a SIEM. This repository should be write-only for log forwarders, making it impossible for an attacker on a compromised endpoint to delete or modify the logs that have already been sent. Furthermore, the SIEM should be configured with a specific rule to generate a high-priority alert if a host suddenly stops sending logs (a 'log source silent' alert) or if an event indicating a log clear (Event ID 1102) is received. This ensures that the forensic trail is preserved and provides a clear indicator of compromise.

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.
Help others stay informed about cybersecurity threats