← Blog

JD.com Data Breaches: Full Timeline Through 2026

Share on X

People search JD.com data breach timeline because millions of customers entrust payment and identity data to everyday transactions. BreachHistory indexes 1 JD.com-linked incident, with headline counts up to 77.4M+ in catalog rows. This page maps every attested event through 2026 with internal links to canonical records.

Why JD.com breach history matters

JD.com operates in Retail (China). 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

2013 — Have I Been Pwned verified incident: JD

Cataloged incident. In 2013 (exact date unknown), the Chinese e-commerce service JD suffered a data breach that exposed 13GB of data containing 77 million unique email addresses. The data also included usernames, phone numbers and passwords stored as SHA-1 hashes. BreachHistory indexes the Have I Been Pwned (HIBP) corpus for third-party breach disclosure and victim notification context; treat record counts and fields as disclosed in that source at time of indexing. Exposed categories include Email addresses, Passwords, Phone numbers, Usernames. BreachHistory cites approximately 77.4M+ affected records in this row. See the jd2013hibp-jd and canonical BreachHistory entry.

Patterns and analysis

  • Mixed intrusion and disclosure events — appears across multiple JD.com 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 JD.com company page for new 2026+ disclosures.

Canonical BreachHistory hub

Explore every indexed row: breachhistory.com/jd · Latest: jd2013hibp-jd.

Sources: BreachHistory catalog (1 row for JD.com), company and regulator disclosures cited in individual breach records.