For: current and former users of Kyash (a cashless wallet app and Kyash Visa card), and anyone who runs internal tools. This article is based on Kyash Inc.'s official notice and does not cover attack techniques.
Developing: this article will be updated as the organisation publishes more
- Who is affected
current and former users of Kyash (a cashless wallet app and Kyash Visa card), and anyone who runs internal tools.
- Confirmed so farSee the table ↓
- Date and time of unauthorized access
- Number of people
- Cause
Listed as possibly affected
- Unique ID
- Account status, some payment information
- Usage records, card restriction status, device identification number, IP address
- Not yet confirmed
- Status of individual notices
- Further findings (whether the scope changes)
- Details of the access-control deficiency and recurrence prevention
- What to do nowSee the steps ↓
- Wait for an individual contact from the company
- Check the sender and do not respond to fake contacts
- Look over your statements now and then
1 more
- Use the contact listed in the notice
- Where to verify (source)All sources ↓
- Kyash Inc., "Apology regarding unauthorized access to an internal web tool" (November 19, 2026, Japanese)
- Last checked
- As of November 21, 2026
Follow-up plans and what we checked
The company says it will contact affected people individually at the email address registered with Kyash. As of November 21, we could not find any follow-up or second report beyond this notice.
What current and former Kyash users should do today
Wait for an individual contact from the company
The company says it will contact affected people individually at the email address registered with Kyash. The notice says people who have already withdrawn are also covered.
The notice does not ask anything of people who are not affected. Until a contact arrives, the three points below are enough.
Check the sender and do not respond to fake contacts
The sender of the company's individual emails is "cs@kyash.co". The company says it does not ask for passwords, card numbers or PINs by email or text message.
After this announcement, fake emails or text messages posing as an apology or a request to confirm details are plausible. Do not open links; open the app yourself to check (how to spot them: What is phishing?).
Look over your statements now and then
The company says the data included cannot be used to identify whose it is, and cannot be used to log in to Kyash or to pay or transfer, so it considers the risk of secondary damage low. As a precaution, check the usage history in the app for transactions you do not recognise, and contact Kyash customer support if you find any.
Use the contact listed in the notice
The contact for this incident in the notice is Kyash customer support (cs@kyash.co). You never need to send a password or card number by email.
What happened (from Kyash's notice)
The following is based on Kyash Inc.'s notice of November 19, 2026.
About 9:20, Wednesday, October 28, 2026
Unauthorized access to the internal tool from outside (per the company's notice).11:42, Wednesday, October 28
End of the period of unauthorized access (per the company's notice).Thursday, November 19
Notice and apology published, saying internal materials posted on the tool may have been obtained by a third party.
The notice does not say when the company found out or how the access was detected.
- All 11,996 people
- A unique ID that identifies the customer (different from card numbers, account numbers and the Kyash ID)
- Of those, 11,786 people
- Account status (active, withdrawn and so on), some payment merchants, dates and amounts, and refund and settlement status
- Of those, 310 people
- One or more of usage records (login, top-up and transfer history and more), card restriction status, a number identifying the device used, and the source IP address
- Stated not to be included
- Name, address, phone number, email address, date of birth, registered credit card data, registered bank account data, Kyash Visa card data, passwords and other information that can identify a user
- Cause
- A deficiency in the internal tool's access control allowed unauthorized access from outside. The tool was operated in an environment separate from the customer-facing services, and no unauthorized access to the app or card systems has been confirmed
Do not add the numbers together
The 11,786 and 310 are parts of the up to 11,996. What is included for everyone is the unique ID; the other items cover the stated number of people. The same person could appear in both, so adding them does not give the number of affected people.
What is known and what is not
State as of November 21, 2026. When a follow-up appears, the status column in this table will be rewritten.
| Item | What the notice says | Status |
|---|---|---|
| Date and time of unauthorized access | About 9:20 to 11:42 on October 28, 2026 | Confirmed (company) |
| Number of people | Up to 11,996 (including those who have withdrawn) | Confirmed (company; a "maximum" figure) |
| Unique ID | All | Possible (company) |
| Account status, some payment information | 11,786 people | Possible (company) |
| Usage records, card restriction status, device identification number, IP address | 310 people (one or more) | Possible (company) |
| Name, address, phone number, email address, date of birth | Not included | Not included (company) |
| Registered card, registered bank account, Kyash Visa card data | Not included | Not included (company) |
| Password | Not included | Not included (company) |
| App and card systems | No unauthorized access confirmed | Not confirmed (company) |
| Secondary damage | The notice says the included data alone cannot identify a person or be used to log in or pay, so it considers the risk low | Not stated (whether damage occurred is not written) |
| Cause | Deficiency in the internal tool's access control | Confirmed (company) |
| Specific method, recurrence prevention | Not mentioned | Not stated |
How to read this: 'may have been taken' does not mean 'was not taken'
The company writes that the internal materials "may have been" obtained by a third party. The notice does not say definitively that they were. The company's view is that the data included cannot identify whose it is.
What this combination of items can lead to
In general, a unique ID alone cannot identify a person or log in. A number identifying a device or a source IP address, however, can sometimes be tied to a person when matched against other data. This does not mean that has happened here.
Because some people's data includes merchants, dates and amounts, a realistic-looking contact imitating the company is possible, such as one that mentions a payment you made on a given day. The company says it does not ask for passwords, card numbers or PINs by email or text message.
What operators can review: what the published facts support
The disclosed cause is a deficiency in the internal tool's access control. The specific method has not been disclosed, so no particular measure can be named as the cause here. Two points follow from the published facts.
- The company says the internal tool was run in a separate environment and that unauthorized access to the app and card systems has not been confirmed.
- The materials posted on the tool included customer identifiers and usage history. Keeping the personal data in internal materials to the necessary minimum reduces the impact if they leak.
Who can open an internal tool and from where, and what information goes into the materials posted on it, are worth checking regularly. This section does not evaluate the company's response.
Sources (public record)
The facts in this article are based on the public information below. We do not speculate on undisclosed methods.
- Kyash Inc., "Apology regarding unauthorized access to an internal web tool" (November 19, 2026, Japanese) — kyash.co
Update history
2026-11-21: First version, based on Kyash's notice of November 19. We could not find any follow-up after the notice. We will update this article when one is published.
Read next
- Same day: SBC Medical Group (Shonan Beauty Clinic and others) customer data stolen
- A payment and prepaid case: Value Card prepaid platform breach
- Follow-on scams: What is phishing?
- For operators: The minimum security baseline for organizations
- Other 2026 incidents: Data breaches and cyberattacks in 2026 (Japan and worldwide)