Free 2024 Data Breach and Email Check

Free confirmed that its information systems were accessed without authorization and customer information was taken in October 2024. A public breach source’s structured record assigns 17 October 2024, classifies the incident as verified, and reports 13,926,173 unique email addresses. CNIL separately describes access to personal data associated with 24 million subscriber contracts across FREE MOBILE and FREE. That regulatory scope is not a count of unique people or unique emails.

The reviewed archive’s main data member contains 19,192,947 physical rows and 24,252,995 valid email occurrences. Current validation and deduplication produced 14,244,784 unique email relations; the live index, completed import job, and source canonical have the same cardinality and match exactly. Seven valid emails in the archive’s Info.txt member were examined by two independent parsers, and all seven were already present in the main canonical. No additive or corrective email import was therefore required.

13,926,173 is a public breach source’s published unique-email scope for the incident; 14,244,784 is the unique-email coverage searchable from the reviewed archive; 19,192,947 is the main file’s physical row count; and 24 million is CNIL’s subscriber-contract scope across two companies. BleepingComputer also reported the threat actor’s claim of 19.2 million customers and more than 5.11 million IBANs. Those external claims were not used to expand the source set or fit it to a target count.

Sources report email addresses, names, physical addresses, phone numbers, genders, dates of birth, and IBAN data for some records. Only validated email relations were imported into LeakData’s local search; IBANs, names, addresses, phone numbers, dates of birth, and all other fields were excluded. A match indicates only that the email address occurs in this source set.

Users who receive a match should avoid links and attachments in unexpected messages impersonating Free or a bank and should visit official sites by typing the address directly. Reused passwords should be replaced, multi-factor authentication should be enabled on the email account, and suspicious sessions should be closed. Treat convincing messages that reference banking or identity details with caution, and verify suspicious payment instructions directly with the bank.