3MediumPartly confirmedAnnounced Updated
A third party misused GitHub credentials to copy repositories. No intrusion into production databases or customers' bank credentials was confirmed. Cardholder names and last four digits for 370 cards were involved.
This incident was imported from a dataset that compiles public announcements, and we are still checking it against the sources. Counts and causes will be updated after the check. Sources are in Japanese.
| Data | Status | Count | Group | Evidence |
|---|---|---|---|---|
| Credentials | Leak confirmed | Not disclosed | — | Source(opens in a new tab) |
| Name | Possible leak | 370 records | — | Source(opens in a new tab) |
| Payment details | Possible leak | 370 records | — | Source(opens in a new tab) |
Counts are the figures the organization announced. Because the same person may be counted more than once, we do not add the rows together.
General steps based on the type of data involved. Check the organization’s notice or help line to see whether you are affected.
Picked from the cause of the incident: tools that help you check your own systems for the same kind of weakness, or spot the warning signs.
An agentless vulnerability scanner that checks the packages installed on a server and lists the ones affected by known CVEs.
A free security platform (SIEM/XDR) that collects logs, configuration, and vulnerability data from agents on your endpoints and shows it all in one dashboard.
An intrusion detection and prevention engine (IDS/IPS) that matches network traffic against rules and records suspicious activity as alerts.
UpDown to select Enter to open Esc to close