People search Grindr data breach timeline because the brand sits on billions of accounts, credentials, and cloud workloads. BreachHistory indexes 4 Grindr-linked incidents, with headline counts up to 3M+ in catalog rows. This page maps every attested event through 2026 with internal links to canonical records.
Why Grindr breach history matters
Grindr operates in Technology. Across indexed rows, recurring themes include cloud and database misconfiguration, third-party and supply-chain exposure, 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 — dark-web claim of 15M+ profiles (June; unverified; distinct from Cybernews sample)
Unverified claim — treat actor counts cautiously. Alongside a June 2, 2026 Cybernews report on a small-sample Grindr forum listing (see grindr-forum-listing2026), early June dark-web monitors circulated separate marketing claiming fifteen million or more sensitive LGBTQ+ dating profiles. Grindr had not confirmed a mass breach at catalog time; researchers warned that large-count Grindr claims often recycle older combo lists. BreachHistory adds this row for the 15M+ marketing narrative without merging it into the verified small-sample listing. Exposed categories include Alleged profile, message, and sensitive attribute data per actor marketing. No attested victim count is published for this row yet. See the grindr-forum-15m-claim 2026 record and canonical BreachHistory entry.
2026 — forum listing of alleged user records (June 2; count unspecified)
Unverified claim — treat actor counts cautiously. On June 2, 2026, Cybernews reported a criminal-forum seller marketing alleged Grindr user records with 18 sample rows including usernames, bcrypt password hashes, email addresses, device identifiers, and precise GPS coordinates—with some sample timestamps as recent as May 2026. The seller priced the listing around $400, suggesting a small dataset; Grindr had not confirmed a breach at catalog time. BreachHistory classifies the row as an unverified forum claim. Exposed categories include Alleged usernames, bcrypt hashes, emails, device IDs, and GPS coordinates per forum samples. No attested victim count is published for this row yet. See the grindr-forum-listing 2026 record and canonical BreachHistory entry.
2018 — — Grindr: A third-party tool that allows users to see who…
Cataloged incident. Mar 2018. A third-party tool that allows users to see who blocked them on Grindr was able to access non-public personal info, including exact locations of users who had opted out of location sharing. BreachHistory cites approximately 3M+ affected records in this row. See the grindr2018 and canonical BreachHistory entry.
2018 — — Grindr: Poor security / misconfiguration, 300,000 records
Cataloged incident. A third-party tool that allows users to see who had blocked them was able to access non-public personal info, including locations of users who had opted out of location sharing. Exposed categories include Personal and demographic data. BreachHistory cites approximately 300K+ affected records in this row. See the grindr2018-iib and canonical BreachHistory entry.
Patterns and analysis
- Cloud and database misconfiguration — appears across multiple Grindr catalog entries; prioritize controls that address this class of failure.
- Third-party and supply-chain exposure — appears across multiple Grindr catalog entries; prioritize controls that address this class of failure.
- Unverified actor or scraping claims — appears across multiple Grindr 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 Grindr company page for new 2026+ disclosures.
Canonical BreachHistory hub
Explore every indexed row: breachhistory.com/grindr · Latest: grindr-forum-15m-claim2026.
Sources: BreachHistory catalog (4 rows for Grindr), company and regulator disclosures cited in individual breach records.