People search Snapchat data breach timeline because the brand sits on billions of accounts, credentials, and cloud workloads. BreachHistory indexes 11 Snapchat-linked incidents, with headline counts up to 4.7M+ in catalog rows. This page maps every attested event through 2026 with internal links to canonical records.
Why Snapchat breach history matters
Snapchat operates in Technology (United States). Across indexed rows, recurring themes include credential theft and social engineering, cloud and database misconfiguration, third-party and supply-chain exposure, zero-day exploitation and malware. Understanding the chronological pattern helps security teams, customers, and regulators separate confirmed disclosures from forum marketing.
Full timeline through 2026
2023 — full timeline
Cataloged incident. Snap Inc. has disclosed or been linked to several data breach and exposure events. Full timeline through 2023. Exposed categories include Details not publicly disclosed. No attested victim count is published for this row yet. See the snap and canonical BreachHistory entry.
2019 — SnapLion abuse — employees spy on users
Cataloged incident. SnapLion (law enforcement tool) used by employees to spy on users—messages, location, phone, email. Former employees said use went beyond legitimate requests. Exposed categories include Email addresses, Phone numbers, Employee data, Messages, Internal documents. No attested victim count is published for this row yet. See the tsnp1905 and canonical BreachHistory entry.
2018 — Phishing attack — 55k+ account credentials (Jul 2017)
Cataloged incident. Phishing in July 2017 collected passwords from 55k+ users via fake login; credentials later published. Mobile site and compromised account used to send link. Exposed categories include Passwords, Credentials. BreachHistory cites approximately 55K+ affected records in this row. See the tsnp1802 and canonical BreachHistory entry.
2017 — — Snapchat: Indian hackers apparently leaked data they stole…
Unverified claim — treat actor counts cautiously. Apr 2017. Indian hackers apparently leaked data they stole last year in response to Snapchat CEO allegedly stating they had no plans to expand to 'poor countries' like India. Snapchat have yet to confirm any leak. BreachHistory cites approximately 1.7M+ affected records in this row. See the snapchat2017 and canonical BreachHistory entry.
2016 — — Snapchat: Snapchat has notified current and former employes…
Cataloged incident. Snapchat has notified current and former employes of a phishing scam that targeted their payroll department that compromised employee information.The information compromised included names, Snapchat employee ID, Social Security numbers, state of residence and work, 2015 wages earned, including stock-option gains, costs of company paid benefits for life and health insurance, relocation reimbursements, employee contricutions to retirement, dependent care, and healthcare plans, additional required Exposed categories include Personal information. BreachHistory cites approximately 700 affected records in this row. See the snapchat2016 and canonical BreachHistory entry.
2016 — Phishing — payroll data of employees (CEO impersonation)
Cataloged incident. Attacker impersonated CEO and obtained payroll info from payroll employee. Isolated; no user data. Reported to FBI. Exposed categories include Employee data. No attested victim count is published for this row yet. See the tsnp1602 and canonical BreachHistory entry.
2014 — Third-party app hacked — 200k photos leaked
Cataloged incident. Third-party app storing 'disappearing' photos was hacked; explicit/racy images and usernames leaked. Snapchat said its systems were not compromised. Exposed categories include Usernames, Names. BreachHistory cites approximately 200K+ affected records in this row. See the tsnp1410 and canonical BreachHistory entry.
2014 — — Snapchat: The hacker or group known as Lightcontact is…
Unverified claim — treat actor counts cautiously. The hacker or group known as Lightcontact is claiming to have hacked Snapchat.com. Reportedly, the group published a database containing Snapchat user names and phone numbers and posted it to several public forums such as Reddit.com.UPDATE: Snapchat has announced a security update to their mobile image sharing services to include an opt out option to the Find Friends system. This update is said to prevent others from looking up their account information through address books. This update will a Exposed categories include Personal information. No attested victim count is published for this row yet. See the snapchat2014 and canonical BreachHistory entry.
2014 — 4.6M accounts — usernames and phone numbers exposed
Cataloged incident. API vulnerability allowed hackers to harvest usernames and phone numbers. Data posted on SnapchatDB.info. Researchers had disclosed issue; Snapchat said it made exploit 'more difficult' but attack followed. Exposed categories include Usernames, Names, Phone numbers. BreachHistory cites approximately 4.6M+ affected records in this row. See the tsnp1401 and canonical BreachHistory entry.
2013 — — Snapchat: 31st Dec 2013, 4.7M records
Cataloged incident. 31st Dec 2013. Hackers abused an exploit to syphon 4.7m user details, including phone numbers. Check here to see if your account was compromised: http://lookup.gibsonsec.org/ BreachHistory cites approximately 4.7M+ affected records in this row. See the snapchatu and canonical BreachHistory entry.
2010 — — Snapchat: Apr, 1.7M records
Unverified claim — treat actor counts cautiously. Apr. Indian hackers apparently leaked data they stole last year in response to Snapchat CEO allegedly stating they had no plans to expand to 'poor countries' like India. Snapchat have yet to confirm any leak. BreachHistory cites approximately 1.7M+ affected records in this row. See the snapchatu1 and canonical BreachHistory entry.
Patterns and analysis
- Credential theft and social engineering — appears across multiple Snapchat catalog entries; prioritize controls that address this class of failure.
- Cloud and database misconfiguration — appears across multiple Snapchat catalog entries; prioritize controls that address this class of failure.
- Third-party and supply-chain exposure — appears across multiple Snapchat catalog entries; prioritize controls that address this class of failure.
- Zero-day exploitation and malware — appears across multiple Snapchat 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 Snapchat company page for new 2026+ disclosures.
Canonical BreachHistory hub
Explore every indexed row: breachhistory.com/snapchat · Latest: snap.
Sources: BreachHistory catalog (11 rows for Snapchat), company and regulator disclosures cited in individual breach records.