← Blog

Mailchimp Data Breaches: Full Timeline Through 2026

Share on X

People search Mailchimp data breach timeline because the brand sits on billions of accounts, credentials, and cloud workloads. BreachHistory indexes 2 Mailchimp-linked incidents, with headline counts up to 107K+ in catalog rows. This page maps every attested event through 2026 with internal links to canonical records.

Why Mailchimp breach history matters

Mailchimp operates in Technology (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

2022 — — Customer data

Cataloged incident. Hacked. Customer data. Exposed categories include Names, emails, addresses, and other PII. No attested victim count is published for this row yet. See the mailchimp2022 and canonical BreachHistory entry.

2022 — — Mailchimp: Hacking, 106,586 records

Cataloged incident. Hackers gained access to internal customer support and account management tools of the email marketing company to steal audience data and conduct phishing attacks. Exposed categories include Personal and demographic data. BreachHistory cites approximately 107K+ affected records in this row. See the mailchimp2022-iib and canonical BreachHistory entry.

Patterns and analysis

  • Mixed intrusion and disclosure events — appears across multiple Mailchimp 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

  1. Step 1: Enable phishing-resistant MFA on every account tied to this brand.
  2. Step 2: Use unique passwords and a password manager—breach rows often involve credential reuse.
  3. Step 3: Monitor official company breach notices and regulator filings, not dark-web downloads.
  4. Step 4: Review OAuth app permissions and revoke unused third-party integrations.
  5. Step 5: Bookmark the Mailchimp company page for new 2026+ disclosures.

Canonical BreachHistory hub

Explore every indexed row: breachhistory.com/mailchimp · Latest: mailchimp2022.

Sources: BreachHistory catalog (2 rows for Mailchimp), company and regulator disclosures cited in individual breach records.