Plaid Inc. (株式会社プレイド), the Tokyo company behind the KARTE customer experience platform, has confirmed that an attacker exploited a vulnerability in its servers on 13 November 2026. The attacker stole connection credentials for its systems and databases and read data out of them. The company is listed on the Tokyo Stock Exchange Growth market under code 4165 and has no connection to the US financial-data firm of the same name. In a stock exchange disclosure filed on 16 November, Plaid said three kinds of information had leaked: 79,249 email addresses registered as KARTE accounts, the secret keys and access tokens customers used to connect KARTE to outside services, and part of the customer data that client companies had loaded into KARTE. The company is still counting the second and third categories. Two KARTE customers have already published their own breach notices. KARTE has been fully offline since 13 November, and Plaid has not given a date for restarting it.
What Happened
Plaid's 16 November disclosure, which TSN, Japan IR, Pulse Newswire and Security Measures Lab all report, says a third party exploited a server vulnerability "in the early hours" of 13 November. The attacker stole credentials used to connect to systems and databases and read data out of those databases. The attacker then used the same credentials to take over a company account and log into the KARTE administration console.
The company gives this timeline (Japan time):
- 08:59, 13 November: Unauthorised access detected. Plaid began cancelling the stolen credentials.
- About 14:27: Servers began shutting down and all KARTE services were switched to maintenance mode.
- 14:44: First public status notice about the unauthorised access and emergency maintenance, according to CyberSIXT.
- About 15:23: Containment finished, including cancelling the credentials used in the attack and blocking traffic from its source.
- 23:35, 13 November: Plaid said it had identified information that may have leaked and had emailed the customers concerned, according to CyberSIXT.
- 15 November: Plaid said the affected environment had been cut off from the network and that new unauthorised access and ongoing data loss had stopped. Reports give different times for this update: Security Measures Lab cites a 10:37 status post, while diff. reports a 16:01 update. Both outlets say Plaid again asked customers to cancel their integration keys.
- 19:00, 16 November: Stock exchange disclosure confirming the categories of leaked data.
Customer notices show the knock-on effect. Bellface, which uses KARTE, QANT and KARTE Datahub for its bellSalesAI support site, says the site went down at about 15:00 on 13 November. By about 16:00 it had blocked access to the database it links to KARTE, and on 15 November it received more details from Plaid.
Plaid says it has reported the incident to Japan's Personal Information Protection Commission, is consulting the police, and will bring in outside security investigators. It has not named an attacker, and no group has publicly claimed the attack. Plaid says it is still assessing the effect on its financial results.
What Was Taken
Plaid confirms three categories of leaked data:
- 79,249 email addresses registered as KARTE account logins. Every report gives the same figure. Japan IR's summary of the disclosure contains a garbled reference to a number "starting with 77", but the company's own text says 79,249. These addresses mostly belong to marketing, CX and engineering staff at client companies, not to the public.
- Integration credentials, including "secret keys, access tokens, etc.", for client companies that had set up links to outside services in the KARTE admin console. Plaid has not said how many.
- Part of the data client companies imported into KARTE through its "linked table" (紐付けテーブル) feature. What this contains depends on each client and may include personal information. Plaid has not said how many records.
The third category is where the general public is exposed. Two downstream companies have described their share:
- Bellface (bellSalesAI) says customer names, email addresses and in-product event data, such as button clicks, may have leaked. It says enquiry contents, the core bellSalesAI data and its Salesforce-linked data were not affected. Bellface says it will report to the Personal Information Protection Commission jointly with Plaid, and that Plaid is coordinating the filing.
- Interworks, a Confidence Interworks group company that runs the Kojo Works (工場ワークス) factory jobs site, says some members' names, email addresses, phone numbers, dates of birth and addresses may have leaked. It used KARTE for email and LINE messaging. It says passwords were never shared with KARTE and that its own systems were not accessed. It has not yet given a count.
Security Measures Lab also reports effects on RightTouch's QANT and on Trabox. Neither company's own statement has been reviewed for this brief, so their exposure is unconfirmed here.
Why It Matters
KARTE runs inside its customers' websites and apps. It tracks visitors, sends emails, LINE messages and on-site campaigns, and connects to other marketing and data systems. That makes it a supply chain risk. Plaid has cut its own environment off the network, but any customer integration key that is still valid can still open the connected system. diff. points out that by asking customers to revoke keys, Plaid is in effect admitting it cannot contain the damage inside its own systems. Pulse Newswire reports that Plaid's warning covers "secondary damage", including unintended writes to connected systems as well as data leaks. A stolen token that can write data could be used to push content or messages through a victim's own channels, not just to read data.
The leaked account emails are also a ready-made phishing list. They belong to the people who run marketing campaigns at KARTE client companies, which is useful to anyone trying to steal credentials. Plaid, Bellface and Interworks have all warned about phishing emails pretending to come from them.
The long outage also creates its own risk. Every day KARTE stays down, client teams are under pressure to switch it back on fast. If they skip a full key rotation to do that, the same exposure returns.
The Attack Technique
Plaid has described the attack only in general terms:
- Initial access: Exploitation of a vulnerability in Plaid's servers. The company has not named the vulnerable component, the software involved, or whether a CVE exists.
- Credential theft: The attacker took stored credentials used to connect to internal systems and databases.
- Data theft: Those credentials were used to read data directly out of databases to an outside location.
- Account takeover: The same stolen credentials were used to take over a company account and get into the KARTE admin console.
This is a familiar pattern. One server-side flaw exposed stored service credentials, and those credentials gave the attacker wide access to data and admin functions. About six hours passed between detection (08:59) and full containment (about 15:23). Plaid has not said when the intrusion began beyond "the early hours", how long the attacker was inside before detection, or whether the admin console access was used to change customer configurations. The outside forensic investigation should answer these questions. As of 16 November, Plaid has not disclosed the intrusion route in detail, the full amount of data taken, or a restart date.
What Organizations Should Do
- Revoke and reissue every KARTE integration credential now. Plaid is explicitly asking customers to do this. Cover secret keys, access tokens and service account credentials for every system linked to KARTE, including CRMs, data warehouses, messaging providers and ad platforms. Do not wait for KARTE to come back online.
- Check logs on the connected systems. Pull access logs for every system that accepted KARTE credentials, going back to before 13 November. Look for reads, writes, exports or configuration changes that did not come from KARTE's normal traffic. Preserve those logs before retention limits delete them.
- Work out what you loaded into linked tables. List which fields your organisation imported into KARTE, such as names, contact details, dates of birth or behavioural data. Use that list to decide your own notification duties under Japan's personal information protection law (APPI) and any other applicable law, as Bellface and Interworks have done.
- Prepare staff and customers for targeted phishing. Warn KARTE account holders that their work email addresses have leaked. Warn end customers about messages pretending to come from your brand, Plaid or KARTE. Make clear you will never ask for passwords or card details by email or SMS.
- Plan the restart carefully. Map which batch jobs, email campaigns and data flows will break when keys are rotated. Bring them back in a controlled order, and do not reconnect KARTE with old credentials when it returns.
- Review how you store third-party credentials more broadly. Give SaaS integrations the narrowest permissions possible (read-only where you can, limited to specific datasets), use short-lived tokens, and keep a list of which vendors hold which keys, so the next revocation takes hours instead of days.
Sources: Plaid Inc. Confirms KARTE Leak of 79,249 Emails TSN | PLAID,Inc. — Apology and Notice on Possible Data Leakage from Unaut... | Plaid Confirms Personal Data Leak via Unauthorized Access to KARTE... | 【11/16追記】当社が利用する「KARTE」への不正アクセスに伴う情報漏洩の可能性について ベルフェイス株式会社 | PLAID shuts down KARTE platform after unauthorised access | プレイド「KARTE」に不正アクセス、外部連携のシークレットキー・トークン無効化を要請 ネットワーク遮断完了も全面停止続くセキュリティ... | KARTE reports containment complete but no restart date, asks custom... | 【重要】外部委託先システムへの不正アクセスに伴う、会員情報漏洩に関するお知らせとお詫び(第一報) 株式会社コンフィデンス・インターワークス