People search Match Group (Tinder/Hinge) data breach timeline because the brand sits on billions of accounts, credentials, and cloud workloads. BreachHistory indexes 2 Match Group (Tinder/Hinge)-linked incidents, with headline counts up to 10M+ in catalog rows. This page maps every attested event through 2026 with internal links to canonical records.
Why Match Group (Tinder/Hinge) breach history matters
Match Group (Tinder/Hinge) operates in Technology (United States). Across indexed rows, recurring themes include ransomware and extortion, credential theft and social engineering, zero-day exploitation and malware, 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 — 10M+ records (Hinge, Tinder, OkCupid, Match)
Cataloged incident. ShinyHunters compromised Match Group via voice phishing targeting an Okta SSO account. Access to AppsFlyer, Google Drive, and Dropbox. Over 10M records from Hinge, Tinder, OkCupid, and Match exposed. User IDs, subscription data, IP addresses, location data, internal documents. Match Group stated credentials, financial info, and private messages were not accessed. Exposed categories include User IDs, Hinge subscription data, IP addresses, location data, internal corporate documents, account info. BreachHistory cites approximately 10M+ affected records in this row. See the match-group 2026 record and canonical BreachHistory entry.
2026 — 85k records
Cataloged incident. ShinyHunters exploited an API vulnerability to scrape user preferences from Tinder/Hinge. Exposed categories include User preferences, dating app data. BreachHistory cites approximately 85K+ affected records in this row. See the match 2026 record and canonical BreachHistory entry.
Patterns and analysis
- Ransomware and extortion — appears across multiple Match Group (Tinder/Hinge) catalog entries; prioritize controls that address this class of failure.
- Credential theft and social engineering — appears across multiple Match Group (Tinder/Hinge) catalog entries; prioritize controls that address this class of failure.
- Zero-day exploitation and malware — appears across multiple Match Group (Tinder/Hinge) catalog entries; prioritize controls that address this class of failure.
- Unverified actor or scraping claims — appears across multiple Match Group (Tinder/Hinge) 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 Match Group (Tinder/Hinge) company page for new 2026+ disclosures.
Canonical BreachHistory hub
Explore every indexed row: breachhistory.com/match-group · Latest: match-group2026.
Sources: BreachHistory catalog (2 rows for Match Group (Tinder/Hinge)), company and regulator disclosures cited in individual breach records.