Skip to main content

Ransomware victim disclosure

All victims

Meducar: Telemedicine and Patient Management System

Claimed by Kazu · listed 16 hours ago

Today
Age
since listed · data leaked

Status timeline

  1. ListedAug 23, 2026
  2. Data leakeddate unknown

At a glance

Group
Kazu
Status
Data leaked
Country
Brazil
Listed on leak site
Aug 23, 2026

About the victim

AI dossier — public-source company profile

Meducar is a Latin American healthtech platform offering software for doctors and clinics to manage medical appointments, electronic health records, patient communication, and telemedicine services. It serves healthcare professionals across Argentina and the broader region with tools for scheduling, clinical history management, digital prescriptions, and patient engagement via WhatsApp and email.

Industry
Healthcare IT / Telemedicine

Attack summary

Severity: critical — Meducar stores regulated healthcare data at scale—electronic health records, patient PII, medical histories, and prescriptions—across multiple healthcare providers in Latin America. Confirmed data publication of such regulated information triggers critical severity regardless of whether encryption occurred.

The kazu group claims to have accessed Meducar's systems and published data. The leak post does not specify whether data was encrypted, exfiltrated, or both, nor does it detail what categories of data are at stake.

critical

Data the group says was taken

AI dossier — extracted from the leak post
  • Electronic health records
  • Patient personal data
  • Medical appointment records
  • Clinical histories
  • Digital prescriptions
  • Doctor and clinic contact information

What the group claims

Meducar is a Latin American healthtech platform that provides software for doctors and clinics to manage medical appointments, electronic health records, and patient communication in one system. It helps healthcare professionals organize their daily practice by offering tools such as online scheduling, clinical history management, electronic prescriptions, and telemedicine services.

Sources

Source

Indexed 16 hours ago

This page surfaces a public ransomware disclosure indexed by Darkfield. Original posts come from the operator's own leak site; we cross-check against ransomware.live, RansomLook and RansomWatch where applicable. Share this URL freely.

Is this your supplier? Your competitor? You?

Pro plans monitor your domain, corporate emails, and crypto wallets across every new ransomware leak-site post, breach dump and Telegram callout — alerts within 5 minutes.

Disclosure context

About kazu

The Kazu ransomware group is a relatively new threat actor that emerged in November 2025, operating with apparent financial motivations based on their targeting patterns across multiple sectors and geographic regions. Given their recent emergence and limited public documentation, details about their country of origin and potential affiliations remain unclear, though their targeting of diverse international victims suggests either a ransomware-as-a-service model or an independent operation with broad reach capabilities. With only nine documented victims to date, specific details about Kazu's attack methodology, initial access vectors, and encryption techniques have not been extensively documented by major threat intelligence organizations, though their targeting spans healthcare, public sector, financial services, and technology organizations across the United States, Colombia, South Africa, Nigeria, and Great Britain. The group's recent emergence means there are no widely reported major campaigns or high-profile incidents documented by established security research organizations like Mandiant, CISA, or the FBI. As of the latest available intelligence, Kazu appears to remain active given their very recent first observation date, though their limited victim count and recent emergence make definitive assessments of their operational status preliminary. The group has been linked to 23 public disclosures across our corpus. First observed on a leak site on November 11, 2025; most recent post August 23, 2026. The operation is currently active.

Timeline of this disclosure

  • August 23, 2026Meducar: Telemedicine and Patient Management System listed by kazuon the group's public leak site

Sector and geography

This disclosure adds to ransomware activity in the Healthcare sector, which has 2,608 disclosures indexed across all operators we track. Geographically, Meducar: Telemedicine and Patient Management System is reported in Brazil, a country with 207 ransomware disclosures in our corpus.

If your organisation is affected

A listing by kazu means Meducar: Telemedicine and Patient Management System 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.br (Brazil), as required for your jurisdiction.
  • Monitor for the data appearing on kazu'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.