This is my security story of the day, and it's not one breach. It's one breach showing up in a dozen other companies' press releases.
PLAID, a Japanese company, runs KARTE, a customer analytics and engagement platform that a lot of big Japanese consumer brands plug their websites, apps and customer data into. On November 13 someone got into PLAID's systems. Since then the disclosures have been rolling in: JINS, Francfranc, Golf Digest Online, WOWOW, Nikkei, Morisawa and more. This week, cosmetics company DHC reported about 19.11 million customer records, per Global Cosmetics News.
What We Know
From PLAID's own notices, as summarized by SmartScope and Rescana (I couldn't read PLAID's pages directly):
- How: in the early hours of November 13, an attacker exploited a vulnerability in PLAID's servers (not named), stole credentials for systems and databases, read data out of databases, and used stolen credentials to take over PLAID accounts and reach an admin console.
- Response: PLAID detected it that morning, invalidated stolen credentials, put all of KARTE into maintenance mode that afternoon and says containment was complete the same day. No new unauthorized access confirmed since. Every KARTE component has been down, with no restore date as of November 18.
- What leaked, per PLAID: about 79,000 KARTE account email addresses; credentials KARTE used to connect to other services (secret keys, access tokens); and part of the customer data that client companies imported into KARTE. Counts for the last two are still under investigation.
And from the client companies:
- DHC: about 19.11 million records: names, dates of birth and email addresses. DHC says credit card information was not compromised. PLAID notified DHC on November 13. (Source: Global Cosmetics News, a secondary write-up.)
- JINS: up to about 18.29 million registered member accounts: member ID, email, family name, date of birth, age, gender, postal code and prefecture. JINS says that's a maximum count of accounts, not people, and that passwords and card data aren't included.
- Others, per SmartScope's tally: Francfranc (up to about 5.98 million member records), Golf Digest Online (up to about 6.97 million, including duplicates), Ain's and AYURA (up to about 2.6 million), plus smaller counts at Morisawa Fonts, subsclife and others. Several companies are still counting.
These numbers overlap across customers and include duplicates, so please don't add them up into one giant headline.
The Real Lesson: Your Analytics Tool Holds Your Keys
Two things about this one stand out.
First, the data. Marketing and analytics platforms get a lot of data because more data means better segmentation. Member lists, birthdays, purchase history. It's usually set up by a marketing team, approved once, and never reviewed by security again. Then it becomes the single place where an attacker can get your entire customer base without ever touching your systems.
Second, the keys. This is the part I'd lose sleep over. PLAID says integration credentials leaked: the secret keys and tokens KARTE used to talk to its customers' other systems. That turns "our analytics vendor got breached" into "someone may be able to write to our CRM, our messaging platform or our data warehouse." PLAID itself warned customers that stolen credentials could cause unintended writes or leaks in linked services.
Credit where it's due: PLAID pulled the plug on its entire platform the same day it detected the intrusion. That's a painful call for a SaaS company and the right one. The disclosures from its customers have also been fast and specific.
I work at Zscaler, and my usual bias applies: I think a lot about keeping data and access tightly scoped. But nothing in my product line fixes this one for you. This is a third-party data governance problem, and every company has it.
What To Do
If you're a KARTE customer:
- Revoke every integration credential KARTE held, at the system that issued it, not just inside KARTE. Rotating a key in one place while the old one still works in another doesn't count.
- Review logs in connected systems for API activity from around November 12 onward: writes, exports, new tokens, new users.
- Expect phishing pretending to be PLAID, sent to your KARTE account addresses.
If you're a customer of the affected brands:
- Expect targeted phishing. Attackers have your name, email and birthday, which is enough for a convincing "your order" or "your membership" email. Don't click; go to the site yourself.
- Use unique passwords and turn on passkeys or MFA where offered. Passwords weren't reported leaked, but credential stuffing follows breaches like this anyway.
If you run any SaaS analytics or engagement platform:
- Inventory what data you've sent to each vendor, and ask whether it needs to be there. If a segmentation tool doesn't need birthdays, don't send birthdays.
- Scope integration keys to the minimum (read-only where possible), set expirations, and know where they live.
- Make sure your vendor's incident contact reaches a human. PLAID emailed customers at their registered contact addresses. If yours goes to someone who left last year, you find out from the news.
Bottom Line
One vendor breach, a dozen breach notices, tens of millions of records, and a pile of API keys into other systems. Your attack surface includes every SaaS tool you've handed customer data and credentials to. Go find out which ones those are, before the next one finds out for you.
Sources: Global Cosmetics News on DHC, SmartScope on KARTE, SmartScope on JINS, Rescana, SBBIT (Japanese)