People search Meducar data breach timeline because regulated data and trust are existential—one incident triggers class actions and regulator exams. BreachHistory indexes 1 Meducar-linked incident, with headline counts up to 3.2M+ in catalog rows. This page maps every attested event through 2026 with internal links to canonical records.
Why Meducar breach history matters
Meducar operates in Healthcare (Argentina). Across indexed rows, recurring themes include ransomware and extortion, unverified actor or scraping claims. Understanding the chronological pattern helps security teams, customers, and regulators separate confirmed disclosures from forum marketing.
Full timeline through 2026
2026 — unverified Kazu extortion; 3.2M Argentine telemedicine patient records claimed
Unverified claim — treat actor counts cautiously. Unverified extortion claim — June 23, 2026. Threat-intelligence reporting (Dark Web Informer) documents actor Kazu extorting Meducar (meducar.com), an Argentine telemedicine and patient-management platform owned by Grupo Cormos, claiming 3,197,677 users' PII stolen with a $150,000 ransom and July 9, 2026 deadline threatening public sale. Claimed fields include identity, contact, health-insurance, and religion data from a platform handling appointments, EHR, prescriptions, and telemedicine. Kazu posted similar healt Exposed categories include Actor-claimed 3,197,677 user records: names, emails, DOB, gender, nationality, marital status, addresses, phone/WhatsApp numbers, profession, health-insurance (obra social) coverag. BreachHistory cites approximately 3.2M+ affected records in this row. See the meducar-kazu-extortion 2026 record and canonical BreachHistory entry.
Patterns and analysis
- Ransomware and extortion — appears across multiple Meducar catalog entries; prioritize controls that address this class of failure.
- Unverified actor or scraping claims — appears across multiple Meducar catalog entries; prioritize controls that address this class of failure.
- Record-count hygiene — BreachHistory indexes actor-cited figures separately from company-confirmed totals; read each row's technicalWriteup before treating counts as fact.
- 2026 monitoring — New disclosures roll into this timeline as they are verified or labeled unverified per catalog policy.
What to do if you may be affected
- Step 1: Enable phishing-resistant MFA on every account tied to this brand.
- Step 2: Use unique passwords and a password manager—breach rows often involve credential reuse.
- Step 3: Monitor official company breach notices and regulator filings, not dark-web downloads.
- Step 4: Watch for medical-ID theft and billing fraud after health-data incidents.
- Step 5: Bookmark the Meducar company page for new 2026+ disclosures.
Canonical BreachHistory hub
Explore every indexed row: breachhistory.com/meducar · Latest: meducar-kazu-extortion2026.
Sources: BreachHistory catalog (1 row for Meducar), company and regulator disclosures cited in individual breach records.