People search Verizon data breach timeline because the brand sits on billions of accounts, credentials, and cloud workloads. BreachHistory indexes 12 Verizon-linked incidents, with headline counts up to 14M+ in catalog rows. This page maps every attested event through 2026 with internal links to canonical records.
Why Verizon breach history matters
Verizon operates in Technology (United States). Across indexed rows, recurring themes include ransomware and extortion, credential theft and social engineering, cloud and database misconfiguration, third-party and supply-chain exposure, 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
2024 — 63,000+ employees — SSN and sensitive data stolen
Cataloged incident. Verizon notified Maine AG of a breach on Sept 21; theft of sensitive information of over 63,000 employees including Social Security Numbers. No Verizon customers implicated. Exposed categories include Social Security numbers, Employee data. BreachHistory cites approximately 63K+ affected records in this row. See the tvz2402 and canonical BreachHistory entry.
2023 — 7.5M customer records on Breached Forums (vendor)
Cataloged incident. Records on over 7 million Verizon users posted to Breached Forums—contract info, device info, encrypted customer IDs. Verizon stated issue stemmed from an outside vendor, resolved January 2023. Exposed categories include Details not publicly disclosed. BreachHistory cites approximately 7.5M+ affected records in this row. See the tvz2303 and canonical BreachHistory entry.
2022 — 250 prepaid accounts compromised (Oct 6–10)
Cataloged incident. Third party accessed prepaid accounts; last four digits of payment cards exposed. Hackers could make unauthorized changes including SIM swaps. Verizon reset PINs and recommended safeguards. Exposed categories include Payment card details, Payment information. BreachHistory cites approximately 250 affected records in this row. See the tvz2210 and canonical BreachHistory entry.
2022 — Hacker ransoms employee database ($250k)
Cataloged incident. Hacker used social engineering to access internal systems and downloaded employee contact info (names, ID numbers, phones, emails). Requested $250k not to release. Verizon declined to engage. Exposed categories include Email addresses, Names, Phone numbers, Employee data, Internal documents. No attested victim count is published for this row yet. See the tvz2205 and canonical BreachHistory entry.
2017 — customer data exposed (NICE Systems)
Cataloged incident. Verizon customer data was exposed via a misconfigured cloud server operated by NICE Systems. Records included names, addresses, account details, and PINs. Exposed categories include Names, Addresses. BreachHistory cites approximately 14M+ affected records in this row. See the vznq and canonical BreachHistory entry.
2017 — 6M users leaked — cloud server misconfiguration
Cataloged incident. Misconfiguration on a cloud server made customer names, phone numbers, and account PINs viewable. Discovered by UpGuard; Verizon addressed quickly. Customers encouraged to update PINs. Exposed categories include Names, Addresses, Phone numbers. BreachHistory cites approximately 6M+ affected records in this row. See the tvz1707 and canonical BreachHistory entry.
2016 — 1.5M Verizon Enterprise customers — data for sale
Cataloged incident. Contact info of 1.5M+ Verizon Enterprise customers accessed via security vulnerability and leaked on cybercrime forum; offered for $10k–$100k. Enterprise portal vulnerability addressed. Exposed categories include Addresses. BreachHistory cites approximately 1.5M+ affected records in this row. See the tvz1603 and canonical BreachHistory entry.
2016 — — Verizon: Data breach reported, 100K records
Cataloged incident. Data breach reported. Reference: http://arstechnica.com/security/2016/03/after-verizon-breach-1-5-million-customer-records-put-up-for-sale/ BreachHistory cites approximately 100K+ affected records in this row. See the verizon2016 and canonical BreachHistory entry.
2014 — — Verizon: The security issue, uncovered by research from…
Cataloged incident. The security issue, uncovered by research from cybersecurity firm UpGuard, was caused by a misconfigured security setting on a cloud server due to human error. The error made customer phone numbers, names, and some PIN codes publicly available online. PIN codes are used to confirm the identity of people who call for customer service.No loss or theft of customer information occurred, Verizon told CNN Tech.UpGuard -- the same company that discovered leaked voter data in June -- initially said the Exposed categories include Personal information. BreachHistory cites approximately 6M+ affected records in this row. See the verizon2014 and canonical BreachHistory entry.
2008 — Employees improperly access Obama cell phone records
Cataloged incident. Verizon fired employees who breached cell phone records of then-President-Elect Obama. Support staff accessed records without authorization; call activity potentially viewable. FBI alerted. Exposed categories include Phone numbers, Employee data. No attested victim count is published for this row yet. See the tvz0811 and canonical BreachHistory entry.
2006 — — Verizon: Two laptops containing employees' personal…
Cataloged incident. Two laptops containing employees' personal information including Social Security numbers were stolen. Verizon is offering affected employees free use of a credit monitoring service. Exposed categories include Personal information. No attested victim count is published for this row yet. See the verizon2006 and canonical BreachHistory entry.
2005 — — Verizon: A website flaw allowed customers to check the…
Cataloged incident. A website flaw allowed customers to check the account details of other customers if they knew their phone numbers. Users' minutes and cell phone models could be viewed in this manner. This unintentional feature may have gone unnoticed for five years due to a glitch. Exposed categories include Personal information. No attested victim count is published for this row yet. See the verizon2005 and canonical BreachHistory entry.
Patterns and analysis
- Ransomware and extortion — appears across multiple Verizon catalog entries; prioritize controls that address this class of failure.
- Credential theft and social engineering — appears across multiple Verizon catalog entries; prioritize controls that address this class of failure.
- Cloud and database misconfiguration — appears across multiple Verizon catalog entries; prioritize controls that address this class of failure.
- Third-party and supply-chain exposure — appears across multiple Verizon catalog entries; prioritize controls that address this class of failure.
- Zero-day exploitation and malware — appears across multiple Verizon catalog entries; prioritize controls that address this class of failure.
- Unverified actor or scraping claims — appears across multiple Verizon 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 Verizon company page for new 2026+ disclosures.
Canonical BreachHistory hub
Explore every indexed row: breachhistory.com/verizon · Latest: tvz2402.
Sources: BreachHistory catalog (12 rows for Verizon), company and regulator disclosures cited in individual breach records.