1MinorConfirmedAnnounced Updated
A configuration error let a third party obtain files covering 2,007 companies and 37,747 people (provisional). Most data are emails, some are billing names and addresses. Passwords and MFA data were not included.
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 |
|---|---|---|---|---|
| Email address | Leak confirmed | Not disclosed | — | Source(opens in a new tab) |
| Name | Leak confirmed | Not disclosed | — | Source(opens in a new tab) |
| Postal address | Leak confirmed | Not disclosed | — | Source(opens in a new tab) |
| Phone number | Leak confirmed | Not disclosed | — | 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 audit tool that reads the configuration of AWS, Azure, Google Cloud, and other clouds and lists the settings that fail security standards.
A scanner that finds vulnerabilities, misconfigurations, and embedded secrets in container images, code, and Kubernetes.
UpDown to select Enter to open Esc to close