← Blog

BigCommerce Data Breaches: Full Timeline Through 2026

Share on X

People search BigCommerce data breach timeline because millions of customers entrust payment and identity data to everyday transactions. BreachHistory indexes 1 BigCommerce-linked incident. This page maps every attested event through 2026 with internal links to canonical records.

Why BigCommerce breach history matters

BigCommerce operates in Retail (United States). Across indexed rows, recurring themes include third-party and supply-chain exposure. Understanding the chronological pattern helps security teams, customers, and regulators separate confirmed disclosures from forum marketing.

Full timeline through 2026

2024 — FreshClick (third-party) compromise; checkout skimming

Cataloged incident. BigCommerce notified merchants after discovering that the third-party FreshClick checkout widget available through its ecosystem had been compromised so that malicious scripts could harvest payment and order PII during checkout. Trade and breach-notification reporting placed active malicious transaction windows roughly in late October–early November 2024, with merchants such as ZAGG and tobacco-pipe retailers filing state breach notices. BigCommerce stated core platform systems were not breached and removed or disa Exposed categories include Cardholder names, addresses, payment-card data, and related order fields for affected storefront sessions. No attested victim count is published for this row yet. See the bigcommerce-freshclick2024 and canonical BreachHistory entry.

Patterns and analysis

  • Third-party and supply-chain exposure — appears across multiple BigCommerce 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: Use virtual card numbers for online checkout where your bank supports it.
  5. Step 5: Bookmark the BigCommerce company page for new 2026+ disclosures.

Canonical BreachHistory hub

Explore every indexed row: breachhistory.com/bigcommerce · Latest: bigcommerce-freshclick2024.

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