Alaxione

CriticalConfirmedHealthcareAugust 20, 2026

An individual claims, on a specialized forum, to have exfiltrated around 6.8 million user profiles and over 10.1 million appointments from Alaxione, a French medical appointment management platform, by exploiting access to a pre-production environment. The claimed dataset includes identities, contact details, dates of birth, national ID (social security) numbers, healthcare professional data and banking details. Alaxione confirmed an intrusion occurred but states it only affected a test server without real patient data, which screenshots published by the claimant appear to contradict. The exact scope of the compromise remains disputed between the parties.

The combination of identity data, national ID numbers and health information exposes affected individuals to a heightened risk of identity theft and targeted phishing.

Disclosed on: August 20, 2026
Accounts affected: 6.8M
Sector: Healthcare
Country: France
Cause: Misconfigured database

Exposed data

Full name
Email address
Phone number
Postal address
Date of birth
Customer ID
Employment data
Social security number
Health data
Banking data (IBAN, card)

You are only affected if you had an account or an order with this organisation.

What you can do

Expect phishing attempts quoting your name and this company. A message that knows your details is not legitimate for that reason.
Watch your statements. On any unknown debit, block the card and request a refund — French law (art. L133-18) entitles you to it.
These documents enable identity theft, and cannot be reissued at will. Keep the notification letter: it proves where the leak came from if an account is opened in your name.
Health data is “special category” data under the GDPR: a leak opens a right to compensation, and the organisation must notify the DPA within 72 hours.
You can ask the organisation exactly what was exposed about you (right of access), and complain to the DPA if no answer comes within a month.

Sources

Entry built from the cited sources after a corroboration check, then reviewed before publication. Spotted an error, or have a correction? Write to us and the entry will be fixed. Contact