People search Swisscom data breach timeline because the brand sits on billions of accounts, credentials, and cloud workloads. BreachHistory indexes 1 Swisscom-linked incident, with headline counts up to 800K+ in catalog rows. This page maps every attested event through 2026 with internal links to canonical records.
Why Swisscom breach history matters
Swisscom operates in Technology. Across indexed rows, recurring themes include credential theft and social engineering, third-party and supply-chain exposure. Understanding the chronological pattern helps security teams, customers, and regulators separate confirmed disclosures from forum marketing.
Full timeline through 2026
2017 — ~800k subscribers’ contact data via abused sales-partner credentials
Cataloged incident. Swisscom disclosed that criminals misused access belonging to an authorized external sales partner to pull contract‑metadata-style records for roughly 800,000 customers—chiefly mobile subscribers—including names, addresses, phone numbers, and birthdates. Swisscom argued core telecom assets were not “hacked” in the sense of a core-network intrusion and that password, payment, and traffic classes stayed out of scope, but the case remains a textbook third-party privileged-account abuse story that still surfaces in Eur Exposed categories include Contact and demographic fields Swisscom associates with subscription onboarding—not payment-card or call-content classes per the company. BreachHistory cites approximately 800K+ affected records in this row. See the swisscom2017 and canonical BreachHistory entry.
Patterns and analysis
- Credential theft and social engineering — appears across multiple Swisscom catalog entries; prioritize controls that address this class of failure.
- Third-party and supply-chain exposure — appears across multiple Swisscom 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: Review OAuth app permissions and revoke unused third-party integrations.
- Step 5: Bookmark the Swisscom company page for new 2026+ disclosures.
Canonical BreachHistory hub
Explore every indexed row: breachhistory.com/swisscom · Latest: swisscom2017.
Sources: BreachHistory catalog (1 row for Swisscom), company and regulator disclosures cited in individual breach records.