Iran-Linked Pay2Key Ransomware Targeted US Healthcare Amidst Military Conflict

US Healthcare Organization Hit by Iran-Linked Pay2Key Ransomware During Geopolitical Tensions

HIGH
March 24, 2026
6m read
RansomwareThreat ActorCyberattack

Related Entities

Threat Actors

Handala

Organizations

Beazley SecurityHalcyonFBI

Other

Pay2Key Stryker

Full Report

Executive Summary

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 Overview

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.

Technical Analysis

Forensic analysis revealed the attackers' methodology:

  1. Initial Access & Persistence: The threat actors compromised an administrative account on the victim's network several days before the main attack. This long dwell time allowed them to perform reconnaissance and prepare for the ransomware deployment. (T1078 - Valid Accounts).
  2. Defense Evasion: The attackers used an updated version of the Pay2Key ransomware, likely with improved obfuscation and anti-analysis features to evade detection by security software.
  3. Impact: The group deployed the ransomware to encrypt systems across the network, causing significant operational disruption to the healthcare provider. (T1486 - Data Encrypted for Impact).
  4. Covering Tracks: After encryption, the attackers attempted to erase all event logs and other forensic evidence of their activity. This is a common technique used to hinder incident response and attribution efforts. (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.

Impact Assessment

  • Operational Disruption: The encryption of systems would have severely impacted the healthcare organization's ability to provide patient care, potentially leading to appointment cancellations, delayed treatments, and risks to patient safety.
  • Geopolitical Signaling: The attack serves as a clear message from Iran, demonstrating its capability and willingness to target U.S. critical infrastructure during times of conflict.
  • Blurred Lines: This incident further complicates the threat landscape by blending the tactics of cybercrime (ransomware) with the motives of nation-states (disruption, espionage). This makes attribution and response more challenging for defenders and governments.
  • Financial Costs: Even without a ransom payment or data exfiltration, the costs of remediation, system restoration, and business interruption are substantial.

Detection & Response

  1. Monitor for Log Tampering: Configure SIEM alerts for attempts to clear or stop the Windows Event Log service. This is a high-confidence indicator of malicious activity.
  2. Privileged Account Monitoring: Closely monitor the activity of all administrative accounts. Alert on unusual login times or locations, and any activity outside the scope of normal administrative duties.
  3. Behavioral-Based Ransomware Detection: Deploy EDR solutions that use behavioral analysis to detect ransomware. These tools can identify processes that are rapidly encrypting files, regardless of the specific malware signature, and can terminate them before significant damage is done.

Mitigation

  1. Offline Backups: The best defense against a purely destructive ransomware attack is having secure, offline, and immutable backups. This allows the organization to restore its systems without being reliant on the attacker for decryption keys.
  2. Privileged Access Management (PAM): Implement a PAM solution to vault and rotate administrative credentials. Use just-in-time (JIT) access to limit the window of opportunity for an attacker who has compromised a privileged account.
  3. Network Segmentation: Segment the network to contain a potential ransomware outbreak. Critical systems, like EHR databases, should be in a separate segment from user workstations to prevent rapid lateral spread.
  4. Threat Intelligence: Stay informed about the TTPs of nation-state actors known to target your industry. Intelligence from sources like CISA and the FBI can provide early warnings and specific indicators to look for.

Timeline of Events

1
March 24, 2026
This article was published

MITRE ATT&CK Mitigations

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:

Audit

M1047enterprise

Forwarding event logs to a remote, write-once syslog server can prevent attackers from successfully clearing logs on the local machine.

Mapped D3FEND Techniques:

D3FEND Defensive Countermeasures

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.

Sources & References

Article Author

Jason Gomes

Jason Gomes

• Cybersecurity Practitioner

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.

Threat Intelligence & AnalysisSecurity Orchestration (SOAR/XSOAR)Incident Response & Digital ForensicsSecurity Operations Center (SOC)SIEM & Security AnalyticsCyber Fusion & Threat SharingSecurity Automation & IntegrationManaged Detection & Response (MDR)

Tags

RansomwarePay2KeyIranHealthcareCyberattackNation-State

📢 Share This Article

Help others stay informed about cybersecurity threats