People search Automatic Data Processing data breach timeline because the brand sits on billions of accounts, credentials, and cloud workloads. BreachHistory indexes 5 Automatic Data Processing-linked incidents, with headline counts up to 125K+ in catalog rows. This page maps every attested event through 2026 with internal links to canonical records.
Why Automatic Data Processing breach history matters
Automatic Data Processing operates in Professional Services (United States). Across indexed rows, recurring themes include mixed intrusion and disclosure events. Understanding the chronological pattern helps security teams, customers, and regulators separate confirmed disclosures from forum marketing.
Full timeline through 2026
2016 — — Automatic Data Processing: Identity thieves have their hands on a new batch of…
Unverified claim — treat actor counts cautiously. Identity thieves have their hands on a new batch of personal and tax data after hacking the payroll outsourcing company ADP.The information is from W-2 forms, the documents workers get from their employers in late January or early February so they can file their annual tax returns with the Internal Revenue Service and state tax departments.Now crooks have all they need to beat those filers to the punch and submit fake 1040s claiming fraudulent tax refunds. Exposed categories include Personal information. No attested victim count is published for this row yet. See the adp2016 and canonical BreachHistory entry.
2013 — — Automatic Data Processing: A software code error caused W-2 information to be…
Cataloged incident. A software code error caused W-2 information to be exposed. Approximately 1,300 classified Houston Police Department employees and 5,000 other local government workers were affected. Names and Social Security numbers were exposed. Exposed categories include Personal information. BreachHistory cites approximately 6K+ affected records in this row. See the adp2013 and canonical BreachHistory entry.
2010 — — Automatic Data Processing: Poor security, 125K records
Cataloged incident. Data breach reported to Have I Been Pwned or similar sources. Further technical details not publicly disclosed. BreachHistory cites approximately 125K+ affected records in this row. See the adpu and canonical BreachHistory entry.
2006 — — Automatic Data Processing: Automatic Data Processing, one of the world's…
Cataloged incident. Jul 2006. Automatic Data Processing, one of the world's largest payroll service companies, confirmed that it was swindled by a data thief looking for information on hundreds of thousands of American investors. BreachHistory cites approximately 125K+ affected records in this row. See the adp2006 and canonical BreachHistory entry.
2005 — — Automatic Data Processing: Business outsourcing, payrolls, benefits, 125K records
Cataloged incident. Business outsourcing, payrolls, benefits BreachHistory cites approximately 125K+ affected records in this row. See the adp2005 and canonical BreachHistory entry.
Patterns and analysis
- Mixed intrusion and disclosure events — appears across multiple Automatic Data Processing 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 Automatic Data Processing company page for new 2026+ disclosures.
Canonical BreachHistory hub
Explore every indexed row: breachhistory.com/adp · Latest: adp2016.
Sources: BreachHistory catalog (5 rows for Automatic Data Processing), company and regulator disclosures cited in individual breach records.