People search SFR data breach timeline because the brand sits on billions of accounts, credentials, and cloud workloads. BreachHistory indexes 1 SFR-linked incident, with headline counts up to 2.1M+ in catalog rows. This page maps every attested event through 2026 with internal links to canonical records.
Why SFR breach history matters
SFR operates in Telecommunications (France). Across indexed rows, recurring themes include 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 — NOVA portal forum leak claim; 2,104,093 rows (unverified)
Unverified claim — treat actor counts cautiously. Unverified leak-site / forum claim — observed July 17, 2026. FrenchBreaches and French threat monitors reported a cybercrime-forum listing alleging compromise of SFR's internal NOVA portal used for fixed-line subscriber and fibre equipment management, with initial access claimed around June 30, 2026. Actors advertised a partial extraction of more than 2,104,093 data rows before detection interrupted the dump, citing customer PII, subscription/raccordement fields, and technical equipment/network identifiers. SFR had Exposed categories include Actor-claimed / sample screenshots: ~2,104,093 rows allegedly including customer names, civility, postal addresses, landline/mobile phones, customer IDs, subscription/fibre provisi. BreachHistory cites approximately 2.1M+ affected records in this row. See the sfr-nova-forum 2026 record and canonical BreachHistory entry.
Patterns and analysis
- Unverified actor or scraping claims — appears across multiple SFR 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: Bookmark the SFR company page for new 2026+ disclosures.
Canonical BreachHistory hub
Explore every indexed row: breachhistory.com/sfr · Latest: sfr-nova-forum2026.
Sources: BreachHistory catalog (1 row for SFR), company and regulator disclosures cited in individual breach records.