Based on publicly available information, satanlockv2 is a newly emerged ransomware group first observed in July 2025 with limited documented activity, having claimed only four known victims to date, suggesting either early-stage operations or a small-scale operation with financial motivations typical of ransomware actors. The group's origin and potential affiliations remain unclear due to insufficient public documentation by major cybersecurity firms or law enforcement agencies, though their recent emergence and naming convention following the "v2" pattern suggests they may be either a rebrand of a previous operation or an evolution of earlier ransomware variants. Their attack methodology and specific technical capabilities have not been extensively documented by reputable security researchers, though their targeting pattern shows a geographic focus on Indonesia, Thailand, and Italy, with victim organizations spanning healthcare and education sectors alongside other unspecified industries. No notable high-profile campaigns, significant ransom demands, or law enforcement actions have been publicly reported against this group by CISA, FBI, or major security firms like Mandiant. Given the limited intelligence available and their recent emergence in July 2025, satanlockv2 appears to currently remain active but operates at a relatively low profile compared to established ransomware groups. The group has been linked to 4 public disclosures across our corpus. First observed on a leak site on July 4, 2025; most recent post July 7, 2025. The operation is currently inactive.
Sector and geography
This disclosure adds to ransomware activity in the Healthcare sector, which has 2,600 disclosures indexed across all operators we track. Geographically, https://klinikdrindrajana.com/ is reported in Indonesia, a country with 37 ransomware disclosures in our corpus.
If your organisation is affected
A listing by satanlockv2 means https://klinikdrindrajana.com/ 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.
- Monitor for the data appearing on satanlockv2'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.
