APT73 is a recently emerged ransomware group that began operations in April 2024, with financial motivation as their primary driver based on their targeting patterns across multiple high-value sectors. The group has demonstrated rapid growth in their operational tempo, accumulating 78 documented victims within their first months of activity. Their targeting methodology shows a preference for English-speaking markets and major economies, with the United Kingdom and United States representing their primary focus areas, followed by significant activity in India, Brazil, and France. The group exhibits a clear preference for high-value sectors including business services, technology, financial services, and healthcare organizations, suggesting a calculated approach to victim selection based on potential payment capability and operational impact. Given the group's recent emergence and limited public documentation from major threat intelligence sources, specific details regarding their initial access vectors, tooling, encryption methods, or organizational structure remain largely unconfirmed by authoritative sources such as CISA, FBI, or established security research firms. The group's current operational status appears active based on the timeline of their emergence, though comprehensive analysis of their capabilities and infrastructure requires additional intelligence gathering and documentation by security researchers. The group has been linked to 161 public disclosures across our corpus. First observed on a leak site on April 22, 2024; most recent post July 6, 2026. The operation is currently inactive.
Also tracked as: Eraleign.
Sector and geography
This disclosure adds to ransomware activity in the Technology sector, which has 3,549 disclosures indexed across all operators we track. Geographically, rao.hr is reported in Austria, a country with 84 ransomware disclosures in our corpus.
If your organisation is affected
A listing by Apt73 means rao.hr appeared on a ransomware extortion site and data attributed to it has been published. If this is your organisation, or a supplier you depend on, the priority is to confirm the intrusion and contain it before the window to act closes.
- Engage your incident-response team and preserve forensic evidence before remediating — do not wipe affected systems first.
- Force a password reset and revoke active sessions for exposed accounts; rotate any credentials, API keys or certificates that may have been in the stolen data.
- Assess regulatory notification duties (GDPR, NIS2, sector regulators) — many carry a 72-hour reporting clock from awareness.
- Report the incident to your national CERT, CERT.at (Austria), as required for your jurisdiction.
- Monitor for the data appearing on Apt73's leak site and across paste and breach channels, and brief downstream partners who may be exposed through you.
How we know this. Darkfield monitors public ransomware leak sites continuously, archiving every new disclosure and the data later released against the victim. Each entry on this page is sourced from the operator's own publication and cross-checked against complementary OSINT feeds (RansomLook, ransomware.live, RansomWatch). We do not collect or host stolen data — only the metadata, timestamps and screenshots needed to make the public disclosure searchable and accountable. Records here are corrected when the original post is edited, retracted, or merged with another disclosure.
