New '0APT' Extortion Group Fakes Data Breach in Bluff Attack on Australian Hospital

Fake Ransomware Group '0APT' Targets Epworth HealthCare with Extortion Bluff

MEDIUM
February 9, 2026
5m read
RansomwareThreat ActorData Breach

Impact Scope

Affected Companies

Epworth HealthCare

Industries Affected

Healthcare

Geographic Impact

Australia (national)

Related Entities

Threat Actors

0APTGlobal ransomware group

Full Report

Executive Summary

In early February 2026, a new extortion group named 0APT targeted Epworth HealthCare, a major Australian private hospital network, with a public extortion attempt. The group claimed on its darknet leak site to have exfiltrated 920GB of sensitive data, including patient records and financial information, threatening to release it if a ransom was not paid. Following an immediate and thorough investigation, Epworth HealthCare found no evidence of a system compromise or data breach. Cybersecurity researchers have analyzed 0APT's activities and concluded the group is a "fake" ransomware operation. Instead of performing actual data theft, 0APT fabricates claims and uses psychological tactics and public pressure to coerce victims into paying, marking an evolution in extortion techniques that bypasses the need for sophisticated technical intrusions.

Threat Overview

  • Threat Actor: 0APT (a newly emerged group)
  • Target: Epworth HealthCare, Victoria's largest not-for-profit private hospital group.
  • Timeline:
    • Late January 2026: 0APT group first appears.
    • February 4, 2026: 0APT lists Epworth HealthCare on its leak site.
    • February 6, 2026: Deadline threatened by 0APT for data publication.
  • Claim: The attackers alleged the theft of 920GB of data, including patient databases, surgical records, clinical notes, and private billing details.
  • Attack Vector: This is not a traditional cyberattack involving network intrusion. The primary vector is psychological manipulation and public relations warfare. The group creates a public crisis for the target organization, hoping the fear of reputational damage and potential regulatory fines will be enough to secure a payment.

Technical Analysis

Unlike traditional ransomware gangs, 0APT does not appear to engage in network exploitation, deploying malware, or exfiltrating data. The technical analysis focuses on their disinformation tactics:

  • Leak Site Operations: The group maintains a darknet leak site, mimicking the infrastructure of legitimate ransomware groups like LockBit or ALPHV. This provides a veneer of credibility to their claims.
  • Lack of Proof: A key indicator of 0APT's fraudulent nature is the consistent failure to provide valid proof-of-compromise. When legitimate groups list a victim, they typically provide a small sample of stolen data to substantiate their claims. Researchers analyzing 0APT's supposed leaks found them to be empty files or infinite streams of random, meaningless data.
  • High Volume, Low Quality: The group posts a large number of victims in a short period, a pattern inconsistent with the time and effort required for actual network intrusions and large-scale data exfiltration.

The 0APT operation represents a low-cost, high-leverage extortion model. It bypasses the significant technical hurdles of breaching a secure network and instead weaponizes fear, uncertainty, and doubt (FUD) as its primary tool.

MITRE ATT&CK Techniques (Observed/Attempted)

While no technical intrusion occurred, the group's actions align with the objectives of several ATT&CK techniques:

Impact Assessment

Even though no data was stolen, the impact on a targeted organization can be significant:

  • Incident Response Costs: Epworth HealthCare had to activate its incident response plan, consuming valuable time and resources from its IT and security teams. They also engaged independent cybersecurity specialists, incurring direct financial costs.
  • Reputational Damage: The public claim of a breach, even if false, can erode trust among patients, partners, and the public. News of the alleged attack was reported by multiple outlets, requiring the hospital to manage a public relations response.
  • Business Disruption: While patient care was not impacted, internal teams were diverted to investigate the claim, causing a temporary disruption to normal business operations.
  • Psychological Toll: The incident creates significant stress and uncertainty for employees, leadership, and stakeholders.

Detection & Response

Detecting a bluff attack is challenging as there are no technical indicators of compromise (IOCs) on the network. Response must focus on verification and communication.

Detection Strategies

  • Threat Intelligence Monitoring: Continuously monitor the dark web, criminal forums, and threat actor leak sites for mentions of your organization's name or assets. This provides the earliest possible warning of such a claim.
  • Internal Verification: Upon receiving a threat or seeing a public claim, immediately initiate an internal investigation to look for evidence of a breach. This includes reviewing logs from firewalls, EDR, SIEM, and data loss prevention (DLP) systems for any signs of anomalous activity, such as large data egress or unauthorized access.

Response Actions

  1. Do Not Panic: Treat the claim as potentially credible but unverified. Avoid making immediate public statements until an initial internal assessment is complete.
  2. Activate Incident Response: Immediately convene the IR team to begin a formal investigation.
  3. Preserve Evidence: Secure all relevant logs and system images, even if no breach is found. This data is crucial for proving a negative (i.e., that no breach occurred).
  4. Engage Experts: Bring in third-party digital forensics and incident response (DFIR) specialists to conduct an independent investigation. This adds credibility to your findings.
  5. Communicate Clearly: Once the investigation confirms no evidence of a breach, issue a clear, confident, and transparent statement to all stakeholders, including employees, customers, and the media. As Epworth did, state plainly that "no verified evidence of any impact" was found.

Mitigation

Mitigation against bluff attacks is primarily about preparedness and resilience.

  • Strong Security Posture: The best defense is being able to quickly and confidently determine that a breach has not occurred. This requires having a mature security program with comprehensive logging, monitoring, and detection capabilities. If you can prove you are secure, you can call the bluff.
  • Incident Response Plan: Have a well-defined IR plan that specifically includes a playbook for handling public data breach claims and extortion attempts, including those that may be fake.
  • Public Relations Strategy: Develop a crisis communication plan in advance. Know who is authorized to speak to the media and have template statements ready for various scenarios.
  • Backup and Recovery: While not directly applicable to a bluff, having robust, tested backups is a critical control for genuine ransomware attacks and allows an organization to resist paying a ransom.

Timeline of Events

1
February 4, 2026
0APT lists Epworth HealthCare on its darknet leak site, claiming a 920GB data breach.
2
February 6, 2026
The deadline set by 0APT for data publication passes.
3
February 8, 2026
Epworth HealthCare and security researchers conclude the attack was a bluff with no evidence of a breach.
4
February 9, 2026
This article was published

MITRE ATT&CK Mitigations

Audit

M1047enterprise

Comprehensive auditing and logging of network traffic, data access, and endpoint activity are crucial to quickly verify or disprove breach claims.

Mapped D3FEND Techniques:

Training for leadership and communications teams on how to handle extortion and public breach claims is critical to managing the reputational impact of a bluff attack.

Proactive threat intelligence monitoring for mentions of the organization on dark web forums is a pre-compromise activity that can provide early warning.

Mapped D3FEND Techniques:

D3FEND Defensive Countermeasures

To effectively counter a bluff extortion attempt like the one from 0APT, an organization must be able to prove a negative: that no data exfiltration occurred. Implementing comprehensive Network Traffic Analysis (NTA) is key. Security teams should use NTA tools and Data Loss Prevention (DLP) solutions to establish a clear baseline of normal outbound traffic patterns from critical data repositories. When a breach is claimed, analysts can quickly query historical network flow data (e.g., NetFlow, sFlow) for any anomalous spikes in data egress to external IP addresses, especially around the time of the alleged incident. For a claim of a 920GB theft, the network signature would be massive and unmistakable. Having this visibility allows the organization to state with high confidence that no such event took place, effectively neutralizing the attacker's leverage. This capability turns the investigation from a frantic search into a quick verification process.

Deploying decoy objects, or honeytokens, within sensitive data stores provides a high-fidelity alerting mechanism for actual data breaches. In the context of the Epworth HealthCare scenario, the IT team could seed their patient database with fake patient records containing unique, non-public identifiers (e.g., a specific email address, a fake patient ID). These honeytokens should be configured to trigger an immediate alert if accessed or used anywhere outside the secure environment. If a threat actor like 0APT were to make a claim and provide a data sample containing one of these honeytokens, the organization would have instant, undeniable proof of a breach. Conversely, if an attacker provides samples and none of them contain honeytokens, it increases the likelihood that the claim is a bluff. This D3FEND technique provides a definitive tripwire that helps distinguish real intrusions from fake ones.

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

0APTRansomwareExtortionBluff AttackHealthcareAustraliaCybercrime

📢 Share This Article

Help others stay informed about cybersecurity threats

Continue Reading