People search Temu data breach timeline because millions of customers entrust payment and identity data to everyday transactions. BreachHistory indexes 2 Temu-linked incidents, with headline counts up to 310M+ in catalog rows. This page maps every attested event through 2026 with internal links to canonical records.
Why Temu breach history matters
Temu operates in Retail (China). Across indexed rows, recurring themes include ransomware and extortion, 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
2026 — forum sale claim (unverified); 310M user records alleged
Unverified claim — treat actor counts cautiously. Unverified forum sale claim — reported June 30, 2026. Cybernews documented a cybercrime-forum listing advertising approximately 310 million alleged Temu user records from the Chinese e-commerce marketplace (PDD Holdings). The seller published 99 sample records; Cybernews researchers confirmed the samples contain names, email addresses, phone numbers, user identifiers, bcrypt password hashes, Android/iOS device metadata, app package/version fields, sign-up and last-login IP addresses, locale settings, geographic fie Exposed categories include Seller-claimed account data: names, emails, phone numbers, bcrypt password hashes, device/app metadata, sign-up and login IP addresses, locales, and account timestamps; Cybernews r. BreachHistory cites approximately 310M+ affected records in this row. See the temu-forum310m 2026 record and canonical BreachHistory entry.
2026 — NDPC investigation (~12.7M data subjects cited; alleged NDP Act issues)
Unverified claim — treat actor counts cautiously. In February 2026, Nigeria’s National Data Protection Commission (NDPC) launched a regulatory investigation into Temu’s processing of personal data in Nigeria, with Nigerian press reporting figures on the order of ~12.7 million Nigerian data subjects and concerns spanning transparency, cross-border data transfers, accountability, and surveillance-style data practices. This is a regulatory enforcement matter rather than a single confirmed hacker exfiltration; outcomes and any formal findings remained pending in early Exposed categories include Scope under investigation; press cited national-scale user data processing. BreachHistory cites approximately 12.7M+ affected records in this row. See the temu-nigeria 2026 record and canonical BreachHistory entry.
Patterns and analysis
- Ransomware and extortion — appears across multiple Temu catalog entries; prioritize controls that address this class of failure.
- Unverified actor or scraping claims — appears across multiple Temu 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: Use virtual card numbers for online checkout where your bank supports it.
- Step 5: Bookmark the Temu company page for new 2026+ disclosures.
Canonical BreachHistory hub
Explore every indexed row: breachhistory.com/temu · Latest: temu-forum310m2026.
Sources: BreachHistory catalog (2 rows for Temu), company and regulator disclosures cited in individual breach records.