Japanese cosmetics and supplements maker DHC says about 19.11 million customer records were leaked after an outsider broke into KARTE. KARTE is a customer analytics and marketing platform run by Tokyo-based PLAID, Inc., which is unrelated to the US fintech company Plaid. DHC announced the leak on November 18, 2026, in a notice titled "Apology and Notice Regarding Customer Information Leakage Due to Unauthorized Access to External Service 'KARTE'". Nikkei and NHK both reported the 19.11 million figure. Every account seen so far gives the same number. The leaked data includes names, email addresses and dates of birth. DHC says payment card data and online shop passwords were not part of it. DHC is one of several Japanese companies to report data loss from the same KARTE intrusion, and so far it has published the largest number.
What Happened
DHC says PLAID told it on November 13 that KARTE had been accessed without authorisation. DHC later heard from PLAID that its customer data had been confirmed as leaked. Moreta, a Japanese breach tracker, notes that DHC went public five days after learning of the incident. That matches Moreta's median for incidents disclosed in Japan in 2026.
DHC used KARTE for marketing, including email newsletters and direct mail, according to Nikkei and Codingholic. Customer data from DHC's systems was fed into the platform, and that data is what leaked. Frame points out that DHC's wording is firmer than some other PLAID clients'. DHC says it has "confirmed" the information leaked, not just that it may have.
According to its notice, DHC has done or plans to do the following: - It has disabled the credentials that connected KARTE to outside services. - It will contact affected customers individually, using the contact details it holds. - It will report to Japan's Personal Information Protection Commission jointly with PLAID. - It has asked PLAID for more detail on the full scope of the breach, Nikkei reports.
DHC says it has not seen any secondary harm, such as misuse of the leaked data.
What Was Taken
Based on DHC's notice, as summarised by Frame, SmartScope, Moreta and Codingholic, the leaked fields are:
- Customer name
- Email address
- Date of birth and age
- Gender
- Member ID
- Newsletter (mail magazine) settings
Shorter reports from Nikkei and Global Cosmetics News list only names, email addresses and dates of birth. They don't conflict with the full list. They just leave fields out.
DHC says the following were not exposed: credit card numbers, expiry dates, security codes, and passwords for its online shop. SmartScope notes a caveat in DHC's wording. Card data was not among the information "confirmed at this time." So DHC is describing what it has found so far, and the final scope could change.
The 19.11 million figure counts records, not people. Frame and Codingholic both stress this point: one customer can have more than one record. The number of individuals affected is probably lower, and DHC has not given a figure for it.
Why It Matters
This is a supply chain breach that hit many companies at once. Other companies have reported KARTE-related losses:
- JINS Holdings (eyewear retailer): up to 18.29 million member accounts, reported by Frame, Global Cosmetics News and News Minimalist.
- J.League (football league): 2,383,073 ticketing records plus 543 fantasy card records, reported by diff. These include internal user IDs, dates of birth, gender and home municipality.
- RIZAP Group: 4.32 million email addresses, according to News Minimalist, which cites a Chinese-language World Journal report.
- Shimamura (apparel retailer): 7 million records, from the same News Minimalist report.
The RIZAP and Shimamura figures come from that one report, and their own disclosures were not reviewed for this brief. News Minimalist puts the combined total above 40 million entries but notes that customers may appear in more than one company's data. Moreta counts 27 other organisations that have reported a leak, or a possible leak, from the same cause. Frame says more companies are still coming forward.
The leaked fields don't include passwords or cards, but they are well suited to phishing. A name, email address, birth date and confirmed DHC customer status are enough to write convincing fake "apology" or "compensation" emails. Moreta and Codingholic both warn customers about this. Birth dates also don't change, so they stay useful for identity checks and social engineering long after the breach.
For defenders, the main point is that this marketing tool held a near-complete copy of DHC's customer base. Breaking into one analytics vendor exposed tens of millions of records across retail, cosmetics, fitness and sports ticketing.
The Attack Technique
There are few details so far. Frame reports that PLAID's own disclosure, dated November 16, says an outsider exploited a vulnerability early on November 13. Neither PLAID's disclosure nor other public reporting has named the affected component, the attacker or how the data was taken out. No group has publicly claimed the attack.
Clients' responses suggest the attackers got access to customer data stored in KARTE and to the integrations around it: - DHC disabled the credentials that linked KARTE to outside services. - J.League changed its integration credentials and suspended its data link to KARTE. According to diff, J.League found no suspicious access before or after the change.
Both companies stress that passwords and card data were never sent to KARTE. That means the exposure was limited to what each client had chosen to sync into the platform. No public report has confirmed whether the stolen integration credentials could have been used to reach clients' own systems.
What Organizations Should Do
- Check what you send to marketing and analytics vendors. List every customer field you sync to CX, CRM and analytics platforms, and remove any the tool doesn't need. As diff notes, J.League's limited exposure came from not sending passwords or card data. Apply the same discipline to birth dates and contact details.
- Scope and rotate integration credentials. Give each vendor integration its own credentials with the fewest permissions possible, rotate them on a schedule, and make sure you can revoke them within hours when a vendor reports a breach.
- Plan for a breach at a vendor. Write a playbook for when a SaaS provider is compromised. It should cover suspending data flows, rotating credentials, getting record-level detail from the vendor, and meeting regulator deadlines such as Japan's Personal Information Protection Commission reporting.
- Prepare for phishing that follows the breach. If your customers' data is in the KARTE incident, expect fake apology or refund emails using your brand. Publish an official notice, tell customers which channels you will use to contact them, and watch for lookalike domains.
- Remove records you no longer need. J.League's leaked data included records of users who had cancelled their accounts. Delete former customers' records from vendor platforms when the business reason to keep them ends.
- Count people, not just records. Remove duplicates from affected datasets early so your notifications, regulator filings and customer messages give an accurate count of the individuals affected.
Sources: DHC Reports Data Breach Affecting 19.11 Million Customer Records in... | DHC says about 19.11 million customer records leaked in the Plaid K... | DHC data breach exposes 19.11 million records; JINS, Shimamura also... | DHC: Approximately 19.11 Million Customer Records Leaked via Unauth... | KARTE breach: DHC reports about 19.11 million records, J.League 2.3... | DHC、委託先プレイドの「KARTE」への不正アクセスで顧客情報約1,911万件が漏えい モレタ | DHC、KARTE経由で顧客情報約1,911万件の漏えいを確認 AI SECURITY NOTE | DHC、約1911万件の顧客情報漏洩 プレイドへの不正アクセスで - 日本経済新聞