People search Nametests data breach timeline because the brand sits on billions of accounts, credentials, and cloud workloads. BreachHistory indexes 4 Nametests-linked incidents, with headline counts up to 120M+ in catalog rows. This page maps every attested event through 2026 with internal links to canonical records.
Why Nametests breach history matters
Nametests operates in Software. Across indexed rows, recurring themes include cloud and database misconfiguration. Understanding the chronological pattern helps security teams, customers, and regulators separate confirmed disclosures from forum marketing.
Full timeline through 2026
2018 — — Nametests: A security failure in a popular quiz app on…
Cataloged incident. Jun 2018. A security failure in a popular quiz app on Facebook left millions of people’s data exposed for almost two years. The data exposed included pictures, status updates, friends lists etc. BreachHistory cites approximately 120M+ affected records in this row. See the nametests2018 and canonical BreachHistory entry.
2018 — — Nametests: Poor security / misconfiguration, 12,000,000 records
Cataloged incident. A security failure in a "personality test" app on Facebook left millions of people's data publicly exposed for almost two years – even after they had deleted the app. Exposed categories include Personal and demographic data. BreachHistory cites approximately 12M+ affected records in this row. See the nametests2018-iib and canonical BreachHistory entry.
2018 — 120M accounts
Cataloged incident. Facebook quiz app. Cambridge Analytica investigated. Exposed categories include Facebook IDs, names, birth dates. BreachHistory cites approximately 120M+ affected records in this row. See the nametests-quiz-2018 and canonical BreachHistory entry.
2017 — — Nametests: According to a post on Medium by the security…
Cataloged incident. According to a post on Medium by the security researcher that discovered the flaw, Inti De Ceukelaire, Nametests.com, the website behind the quizzes, recently fixed a flaw that publicly exposed information of their more than 120 million monthly users — even after they deleted the app. . . .Who was affected?According to Facebook, NameTests has more than 120 million active monthly users. I have no insights in how many users have given their data to the app since their launch early 2015. It is impo Exposed categories include Personal information. BreachHistory cites approximately 120M+ affected records in this row. See the nametests2017 and canonical BreachHistory entry.
Patterns and analysis
- Cloud and database misconfiguration — appears across multiple Nametests 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 Nametests company page for new 2026+ disclosures.
Canonical BreachHistory hub
Explore every indexed row: breachhistory.com/nametests · Latest: nametests2018.
Sources: BreachHistory catalog (4 rows for Nametests), company and regulator disclosures cited in individual breach records.