All Breaches
February 9, 2025 Verified Sensitive Record Insurance

Groupe Zéphir Data Breach

The 2025 Groupe Zéphir data breach occurred in February 2025 when the policyholder and broker database of Groupe Zéphir (groupe-zephir.fr), a prominent French wholesale insurance brokerage network operating since 1989, was compromised and published on cybercrime forums.

45.4 Thousand
Reported Records
7
Data Types
Medium
Severity
Oct 10, 2026
Last updated

Protect Yourself

Check whether you were affected by this breach

Check my email

Exposed Data Types

7
  • Email addresses
  • Names
  • Phone numbers
  • Physical addresses
  • Bank account numbers
  • Genders
  • Purchases

About This Breach

What information was affected in the Groupe Zéphir incident?

The structured JSON export (groupe-zephir_fr.json) contained sensitive personal, policy, and banking profiles. Compromised records for 45,366 unique clients and brokers encompass:

  • Personal & Identity Information: Full customer names, broker designations, and corporate titles.
  • Financial & Banking Identifiers: Bank account IBAN numbers, national BBAN identifiers, and account holder titles (titulaireRib).
  • Contact Credentials: Canonical email addresses and telephone numbers.
  • Physical Location Data: Residential street addresses, postal codes, and French department identifiers.
  • Insurance Policy Records: Contract models (contratModels), claims notification logs (sinistre), and brokerage relationships.

How many accounts were affected?

Rigorous RFC canonical parsing and deduplication across 67,294 client dossier records confirmed 45,366 unique valid email addresses.

Technical analysis and security risks

The exposure of verified SEPA IBAN banking coordinates coupled with policy details and home addresses facilitates unauthorized direct debit attempts, fraudulent policy renewal calls, and targeted spear-phishing schemes.

Recommended actions for affected users

Policyholders and broker partners associated with Groupe Zéphir should:

  • Monitor bank statements for unauthorized SEPA debit orders.
  • Exercise vigilance regarding unsolicited insurance adjustment calls or claims demands.

Verification and editorial method

LeakData compares the incident name, date, affected-record count, and exposed data types with accessible sources. Unverified fields are not presented as facts, and records are updated when new evidence becomes available.

Report missing or incorrect information