Matt Ketchum, MKUltraman · Scope: incidents disclosed 1–31 August 2026 · Data as of 16 November 2026 · Source: the Japan Cybersecurity Tracker
Written in November 2026 from tracker data and dated to the period it covers. It was not published at the time.
The 30-second briefing
Key facts. Organisations in Japan published 94 breach notices in August 2026, up 22 on July’s 72. They trace back to about 78 distinct breaches. 25 of 94 (26.6%) notices came from organisations hit through a supplier, and one online-shop platform produced 17 of 94 (18.1%). Where a notice gave a figure, the headline numbers add up to about 28.0 million, and that platform’s 23.36 million people make up 83.5% of it.
Who should act. Anyone selling online through a hosted shop platform, and anyone whose staff log in to email, file-sharing, code or shop-admin accounts from the internet, which is nearly everyone.
One first action. Put phishing-resistant multi-factor authentication on every admin, cloud-storage and code-repository account, starting with the ones that can export customer data.
Biggest uncertainty. How attackers got in. 50 of 78 (64.1%) of the distinct breaches do not say.
Posture
August was the busiest month of the summer, but most of the rise came from organisations breached in their own systems, not from suppliers. Where the route is known, it is mostly a misused account: a phished staff login, a hijacked mailbox, stolen credentials for a code repository. The one big supplier story was a shop platform whose breach reached thousands of online stores, including stores that had already left it.
The count
94 notices were disclosed between 1 and 31 August, up 22 from July’s 72 (30.6% more). The first full week carries the shop-platform wave. After that, own-system notices rose to 22 in the last full week, the highest weekly figure of the summer.
| Week | Notices | Through a supplier | Own systems | Supplier’s own notice | Unclear |
|---|---|---|---|---|---|
| 1–2 Aug | 3 | 2 of 3 (66.7%) | 0 | 1 | 0 |
| 3–9 Aug | 31 | 16 of 31 (51.6%) | 15 | 0 | 0 |
| 10–16 Aug | 14 | 2 of 14 (14.3%) | 12 | 0 | 0 |
| 17–23 Aug | 21 | 3 of 21 (14.3%) | 17 | 1 | 0 |
| 24–30 Aug | 24 | 2 of 24 (8.3%) | 22 | 0 | 0 |
| 31 Aug | 1 | 0 of 1 (0.0%) | 1 | 0 | 0 |
| August | 94 | 25 of 94 (26.6%) | 67 | 2 | 0 |
Weeks run Monday to Sunday and are cut at the month’s edges. “Own systems” means the organisation’s own systems were breached. “Supplier’s own notice” is a supplier announcing its own breach.
Notices vs distinct breaches
When one supplier is breached, every customer that publishes counts as a notice, but it is still one breach. To count breaches, I collapsed every notice linked to a named supplier into that supplier’s breach, and counted each own-system incident once.
About 78 distinct breaches produced the 94 August notices. Eight named supplier breaches account for 24 notices. 67 were breaches of the organisation’s own systems, and 3 came through a supplier the notice does not name. Those 3 are counted one each, so 78 is an upper bound.
7 of 8 (87.5%) named supplier breaches produced a single notice in August. ShopServe produced 17.
| Supplier breach | What it does | August notices | Share of 94 |
|---|---|---|---|
| ShopServe (E-Store) | Hosted online-shop platform | 17 | 17 of 94 (18.1%) |
| PeakManager (EPARK Relax & Esthe) | Booking and customer system (July breach, late customer notice) | 1 | 1 of 94 (1.1%) |
| Fuso Dentsu | IT services; cloud file storage (July breach, late customer notice) | 1 | 1 of 94 (1.1%) |
| Meruhai-kun (Delightful) | Bulk email delivery (June breach, late customer notice) | 1 | 1 of 94 (1.1%) |
Counts include the supplier’s own notice where it published one. Four other supplier breaches also produced one notice each.
ShopServe alone made up 18.1% of the month’s notices. The single-notice rows are mostly the tail of June and July breaches, still turning up weeks later.
Through a supplier
25 of 94 (26.6%) notices came from organisations hit through a supplier, and another 2 were suppliers announcing their own breach. Of the 25, 20 (80.0%) name the supplier, 2 (8.0%) are inferred from the service described and 3 (12.0%) do not name one.
Two notices show how long the chain can get. The Japan Association for the 2025 World Exposition reported that a re-subcontractor, a supplier’s supplier, had its Microsoft 365 account taken over through phishing, exposing stakeholder and event-participant data. It found out in May and published on 20 August. Logi-Net Japan reported customer data exposed through Fuso Dentsu’s cloud file storage, a July breach.
Notable cases
- E-Store disclosed on 1 August that attackers had exploited a flaw in its ShopServe shop platform, run a malicious program on the server and sent out the database. The window ran from 21 May to 1 August. Its later reports put the total at about 23,356,000 people across 7,858 current and former shops, with partial card data (first six and last four digits, and expiry) for about 2.1 million. PFU had stopped using ShopServe in October 2025, and its customers’ data was still there.
- Yellow Hat, the car-parts chain, reported 1,797,124 members exposed from its online work-reservation system. Its first report said passwords were not held in that system. Its final report lists passwords, stored in a non-recoverable form, among the leaked data.
- REXT, the RIZAP group retailer behind WonderGOO and Shinseido, was hit by ransomware through a network device. 1,044,906 records were at risk, and the attackers published 310 files.
- Phished and hijacked accounts were everywhere. Kodansha lost up to 3,812 contacts after a phishing attack, and 553 people then received spoofed mail. Kindal, a Treasure Factory subsidiary, had a staff account on its shop platform taken over and 136,464 customer records exported in bulk. Rakuten Drive had an admin account taken over, exposing 15,382 accounts’ stored data. The Japan Science and Technology Agency found 12 staff mailboxes accessed, about 16,000 emails.
- Chubu Electric Power reported credential misuse that exposed about 2,400 people’s mail and about 71,700 group contacts. Innovation reported stolen GitHub credentials and personal data for 62,691 people sitting in its code repositories.
- Gakken Medical Support reported a WordPress flaw used to create rogue accounts and change passwords across 78 websites it managed.
How attackers got in
The route is stated for 28 of 78 (35.9%) of the month’s distinct breaches. 50 of 78 (64.1%) say “unauthorized access” and nothing more. The shares below use only the 28 that state a route, so treat them as a sketch.
| Route, in plain English | Distinct breaches | Closest MITRE ATT&CK technique |
|---|---|---|
| Misused account: stolen or guessed passwords, hijacked email or admin accounts | 15 of 28 (53.6%) | Valid Accounts (T1078) |
| Ransomware: files encrypted, often with data taken first | 7 of 28 (25.0%) | Data Encrypted for Impact (T1486), which describes the damage, not the way in |
| Flaw in an internet-facing system or app: an unpatched or vulnerable website, server, plugin or programming interface (API) | 5 of 28 (17.9%) | Exploit Public-Facing Application (T1190) |
| Other: malware on a contractor’s computer, payment fraud, supplier outages | 1 of 28 (3.6%) | Varies |
MITRE ATT&CK is a public catalogue of attacker techniques that security teams use as a shared vocabulary. Supplier breaches take the route stated in the supplier’s own notice.
Misused accounts lead clearly, and the count is conservative: the Chubu Electric and Innovation notices describe misused credentials too, but the tracker files both as “method undisclosed”, so they are not in the table. The ShopServe flaw produced the most notices, but by distinct breaches, the cheaper problem to fix, account security, is the bigger one.
What’s affected
76 of 94 (80.9%) notices list at least one type of data. The shares below use those 76 as the base.
| Data type | Notices | Share |
|---|---|---|
| Email addresses | 39 | 39 of 76 (51.3%) |
| Names | 36 | 36 of 76 (47.4%) |
| Phone numbers | 31 | 31 of 76 (40.8%) |
| Postal addresses | 29 | 29 of 76 (38.2%) |
| Date of birth | 5 | 5 of 76 (6.6%) |
| Passwords (hashed or not) | 20 | 20 of 76 (26.3%) |
| Payment card data (including partial numbers) | 4 | 4 of 76 (5.3%) |
Data types are matched on the wording of each notice, and a notice that says “no card data” is not counted as card data. Passwords use the tracker’s own password flag.
Contact details lead, and the password share is 26.3%. 17 of 20 (85.0%) of those notices are ShopServe and its shops, where customer logins sat on the platform. Yellow Hat’s final report added passwords too.
Records
August’s deduplicated total is 27,980,501. Notices whose figures already sit inside a supplier’s own total are left out: 19 of 94 (20.2%). That way each supplier breach counts once. Of the 75 that remain, 37 of 75 (49.3%) give a number.
The unit is the catch. Notices count email addresses, people, accounts or simply “records”, and the same person can appear in many of them. Read this as the sum of headline figures, not as a count of people.
| Unit stated | Records | Share of total |
|---|---|---|
| People | 25,484,408 | 91.1% |
| Records, unit unspecified | 1,361,638 | 4.9% |
| Accounts and form submissions | 1,126,565 | 4.0% |
| Unit not stated | 4,078 | 0.0% |
| Email addresses | 3,812 | 0.0% |
One breach carries the month. ShopServe’s 23,356,000 people are 83.5% of the total. The top five make up 98.0%. The median notice with a figure is 5,000.
ShopServe’s figure is from its later reports, which put the deduplicated estimate at about 23.36 million people, up from an earlier figure of up to 8.85 million. It is filed under August because that is when the breach was first disclosed.
| Organisation | Headline figure | Breached |
|---|---|---|
| E-Store (ShopServe) | About 23,356,000 people | Supplier’s own systems |
| Yellow Hat | 1,797,124 members | Own systems |
| White Essence | About 1,050,000 accounts | Own systems |
| REXT | 1,044,906 records | Own systems |
| VOISING | About 170,000 records | Own systems |
Disclosure speed
Only notices with an exact discovery date and an exact disclosure date are used: 41 of 94 (43.6%). Discovery here means when the organisation says it found out, which for a supplier’s customer is often when the supplier told it.
| Group | Notices with both dates | Median days, discovery to disclosure | Disclosed within 7 days |
|---|---|---|---|
| All | 41 | 4 | 30 of 41 (73.2%) |
| Own systems | 36 | 3.5 | 28 of 36 (77.8%) |
| Through a supplier | 3 | 22 | 1 of 3 (33.3%) |
| Supplier’s own notice | 2 | 4 | 1 of 2 (50.0%) |
Disclosure got quicker. 3 of 41 (7.3%) disclosed on the day they found out, and 5 of 41 (12.2%) took more than 30 days. The slowest was 196 days, a construction-industry information site that found the intrusion in January and published in August. The Expo association took 99 days.
ShopServe’s attackers were inside for 72 days before the company found out.
Sectors two ways
Counting notices and counting breaches give different pictures. The second column counts breaches of the organisation’s own systems, including suppliers that announced breaches of their own systems (69 in August).
| Sector | Notices | Own-system breaches |
|---|---|---|
| Retail / e-commerce | 24 of 94 (25.5%) | 12 of 69 (17.4%) |
| Manufacturing / construction / utilities | 19 of 94 (20.2%) | 17 of 69 (24.6%) |
| IT / internet / software services | 14 of 94 (14.9%) | 14 of 69 (20.3%) |
| Other | 9 of 94 (9.6%) | 6 of 69 (8.7%) |
| Media / entertainment | 7 of 94 (7.4%) | 7 of 69 (10.1%) |
| Education / research | 5 of 94 (5.3%) | 4 of 69 (5.8%) |
| Government / public sector | 5 of 94 (5.3%) | 3 of 69 (4.3%) |
| Healthcare / pharma | 3 of 94 (3.2%) | 2 of 69 (2.9%) |
| Travel / hospitality / leisure | 3 of 94 (3.2%) | 3 of 69 (4.3%) |
| Finance / insurance | 3 of 94 (3.2%) | 1 of 69 (1.4%) |
| Transport / logistics | 2 of 94 (2.1%) | 0 of 69 (0.0%) |
Retail tops the notice count with 24 of 94 (25.5%), and 11 of 24 (45.8%) of those came through ShopServe. By own-system breaches, manufacturing, construction and utilities lead with 17 of 69 (24.6%), a mix of ransomware, hijacked accounts and intrusions the notices do not explain.
Outside counts
The Personal Information Protection Commission (PPC) received 235 initial reports of personal-data leaks from unauthorized access in August, up from 212 in July. It counts reports filed with it rather than public notices, and leaves out financial and telecom firms and public bodies.
Tokyo Shoko Research (TSR), which counts only listed companies and their subsidiaries, says its monthly count stayed in the teens until September.
One practical tip
Put phishing-resistant multi-factor authentication (MFA), meaning passkeys or hardware security keys rather than codes sent by text, on every account that can see or export customer data: shop admin, email admin, cloud storage, code repositories. Start with the accounts that can export in bulk.
And keep personal data out of code repositories. A repository is for code. If test data is needed, make it up.
30, 60 and 90 days
Review every supplier that touches personal data. Keep the ones that are necessary, and bring the rest in-house or drop them. For the ones you keep, check who logs in and how. Fewer suppliers and fewer admin accounts mean fewer ways in and less to manage: operational efficiency as well as lower risk.
| When | Action | Owner | Done when |
|---|---|---|---|
| 30 days | List every admin and bulk-export account, at home and at suppliers, with a named owner. | IT operations | One list; dormant accounts closed. |
| 60 days | Phishing-resistant MFA on all of them. Search code repositories and shared drives for personal data and remove it. | IT operations and development leads | Admin accounts covered; repositories clean. |
| 90 days | Ask each shop, booking or form platform you use, or used, what of yours it holds, and delete what you do not need. | Named supplier owners, with legal | Written answers from each; deletion confirmed. |
What remains unknown
- How most attackers got in. 50 of 78 breaches (64.1%) do not say.
- How many people were really affected. Units are mixed, and 38 of the 75 counted notices (50.7%) give no number.
- How many of ShopServe’s 7,858 shops will ever publish. 16 had by the end of August.
- How complete August is. These rows were added later, so small notices may be missing.
How we counted
Each row of the Japan Cybersecurity Tracker is one organisation’s published notice about a cyber incident in Japan. This briefing uses rows whose disclosure date falls between 1 and 31 August 2026, from the snapshot of 16 November 2026. The June to September rows were mostly added after the fact, in a backfill, so small notices that never reached the press are more likely to be missing than in later months.
- Included: incidents disclosed by the organisation itself, or a supplier’s notice confirmed by the customer’s own notice. Hijacked email and admin accounts count even when no leak is confirmed.
- Not included: ransomware gangs’ claims on the dark web without a notice, lost USB sticks and other physical losses, and precautionary shutdowns with no incident.
- “No leak confirmed” is recorded as stated. It is not read as “no leak”.
- Supplier links: of the 25 notices through a supplier, 20 (80.0%) name the supplier, 2 (8.0%) are inferred from the service described and 3 (12.0%) do not name one.
- Distinct breaches: notices are collapsed to the parent breached supplier named in the data. Own-system incidents and unnamed-supplier notices count one each, so the distinct count is an upper bound.
- Records: the headline or maximum figure each notice gives, including later revisions. Blank stays blank, not zero. Figures already inside a supplier’s total are excluded from the sum.
- Dates: notices are placed by disclosure date. 13 tracker rows have no exact disclosure date. None of them is placed in this month, and they are left out of every monthly figure.
- Limits: categories come from the wording of notices, much of it translated from Japanese. The data is a snapshot and changes as reports are revised.
The full row-level dataset is available on request through the dataset page, which also explains the method and how to cite it.
If you need any help, don’t hesitate to get in touch.
Matt Ketchum