Security Guides

Kyash internal tool accessed without authorization (up to 11,996 people): names, contact details and card data not included, and what users should do

Kyash disclosed on Nov 19, 2026 that data on up to 11,996 people may have been taken from an internal tool. What is and is not included, and what to do.

Published 2026-11-21 Updated 2026-11-21 Last verified 2026-11-21 8 min read
On this page

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 ↓
  1. Wait for an individual contact from the company
  2. Check the sender and do not respond to fake contacts
  3. Look over your statements now and then
1 more
  1. Use the contact listed in the notice
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

1

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.

2

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?).

3

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.

4

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.

  1. About 9:20, Wednesday, October 28, 2026

    Unauthorized access to the internal tool from outside (per the company's notice).
  2. 11:42, Wednesday, October 28

    End of the period of unauthorized access (per the company's notice).
  3. 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.

Up to 11,996
Covered (including people who have withdrawn)
11,786
Account status, some payment information and more
310
Usage records, card restriction status, device identification number or IP address (one or more)
About 2 hours
Window of the access (this site's calculation from the announced 9:20 to 11:42)
What was and was not included (from Kyash's notice)
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.

ItemWhat the notice saysStatus
Date and time of unauthorized accessAbout 9:20 to 11:42 on October 28, 2026Confirmed (company)
Number of peopleUp to 11,996 (including those who have withdrawn)Confirmed (company; a "maximum" figure)
Unique IDAllPossible (company)
Account status, some payment information11,786 peoplePossible (company)
Usage records, card restriction status, device identification number, IP address310 people (one or more)Possible (company)
Name, address, phone number, email address, date of birthNot includedNot included (company)
Registered card, registered bank account, Kyash Visa card dataNot includedNot included (company)
PasswordNot includedNot included (company)
App and card systemsNo unauthorized access confirmedNot confirmed (company)
Secondary damageThe notice says the included data alone cannot identify a person or be used to log in or pay, so it considers the risk lowNot stated (whether damage occurred is not written)
CauseDeficiency in the internal tool's access controlConfirmed (company)
Specific method, recurrence preventionNot mentionedNot 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.

Latest breaking reports

All breaking reports →

FAQ

QWhat may have been taken from Kyash?
A

According to Kyash's notice of November 19, 2026, up to 11,996 people (including those who have withdrawn) are covered. Everyone's unique ID identifying the customer was included; for 11,786 of them, account status (active, withdrawn and so on), some payment merchants, dates and amounts, and refund and settlement status; and for 310 of them, 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.

QAm I affected?
A

The company says it will contact affected people individually at the email address registered with Kyash. The email will be sent from cs@kyash.co. Until you receive an individual contact, you cannot tell whether you are affected.

QDid names, phone numbers, card data or passwords leak?
A

The notice says information that can identify a user, such as name, address, phone number, email address, date of birth, registered credit card data, registered bank account data, Kyash Visa card data and passwords, is not included. The unique ID is also stated to be different from card numbers, account numbers and the Kyash ID.

QShould I change my password?
A

The notice says passwords are not included and does not ask users to change them. The company says no unauthorized access to the app or card systems has been confirmed. Whether to change is up to you, but if you reuse the same password on other services, using a different one is sensible (that is this site's general advice, not the company's).

QWhat caused it?
A

The company says the cause was a deficiency in the internal tool's access control, which let someone access it from outside without authorization. It says the tool was operated in an environment separate from the customer-facing services. The specific method has not been disclosed.

QWhat if someone contacts me claiming to be Kyash?
A

The company says it does not ask for passwords, card numbers or PINs by email or text message, and asks people to be careful with suspicious emails and text messages imitating Kyash. Check by opening the app yourself or the official website. The notice gives Kyash customer support (cs@kyash.co) as the contact for this incident.