For: anyone who has shopped online in Japan (especially if you received a notice email from E-store) anyone who runs a shop on ShopServe, and anyone registered as an affiliate. This article is based on E-store's official notices (up to the final report of October 16, 2026) and announcements by affected shops, and does not cover attack techniques.
Corrected in the final report (what differs from the second report)
The second report said shops' mail system and FTP IDs and passwords, and bank account details of the accounts E-store transfers money to (payout accounts), had also leaked. In the final report, the investigation confirmed that these did not leak, and they were removed from the list. The count also changed from the second report's 8,853,839 records (possibly including duplicates) to "about 23,356,000 people" after removing duplicates. The units differ, so the two figures cannot be compared.
What buyers should do today
Check whether you are affected (start from the shop names)
As far as this site can tell, E-store has not published a list of affected shops. You can check in three ways:
- Look for an individual notice from E-store (the company says individual notices are complete)
- Check the official sites of online shops you have used for notices mentioning unauthorized access or E-store
- Ask through the buyer inquiry form linked from E-store's final report
For people whose contact details could not be confirmed, the company says its public notice and inquiry desk serve as the notification. At least one affected shop said its affected buyers go back to 2008. A purchase made years ago can still be included.
Be suspicious of messages that quote real order details or your card's last four digits
The leak includes names, addresses, phone numbers, email addresses and workplaces, plus the cardholder name, first 6 and last 4 card digits, and expiry date. That means a fake message can say "your card ending in 1234" and get the details right.
E-store says it never asks, by email or SMS, for card details to be re-entered, for re-payment or for passwords, and warns of suspicious emails, SMS and calls posing as the company or financial institutions. If you get such a message, do not use its links or phone numbers; open the shop's or card company's official site yourself (see What is phishing?).
Check your card statements
According to the company, it does not hold full card numbers or security codes, and they did not leak. About 2,096,900 people had part of their card data included. Still, in case a fake message tricks someone into entering card details, check your statements this month and for the next few months.
If you see a charge you do not recognize, call the number on the back of your card. You can also ask your card company whether a replacement card is needed.
Change reused passwords
The company says member passwords are stored encrypted and judges it unlikely they can be identified, and says the leaked data cannot link a member to the shop they use. If you use the same email address and password on other services, change those. The company also recommends a different password for each service and multi-factor authentication.
Changing your member password at the shop you used is also sensible. A password manager is the practical way to keep track.
If you entered your workplace, watch for suspicious messages at work too
Buyer data includes workplace. If you had orders delivered to your office, messages combining your name and employer may arrive by work email or phone. Check anything about deliveries or payments through the shop's official site.
What shop owners and affiliates should do today
According to E-store's final report, shop admin-panel IDs and passwords, shop details printed on convenience-store payment slips (sales manager's name, shop name, postal code, address, phone and fax numbers) and affiliates' email addresses and passwords leaked. The shop mail system and FTP IDs and passwords, and bank account details of the accounts E-store transfers money to (payout accounts), listed as leaked in the second report, were corrected as not affected.
Change your admin password and turn on two-step verification
Shop admin-panel IDs and passwords are among the leaked items. Change the password. The company says it has strengthened admin authentication as a preventive measure (including two-factor authentication), so turn on any such feature that is available to you. If you used the same password on other services, change those too.
If you were registered as an affiliate, change your password
Affiliates' email addresses and passwords are also included. Change the password, and change it on any other service that uses the same email address and password. If a message about rewards or an account check reaches your registered email address, do not open its links; check through the official site.
Check the admin panel for changes you did not make
The company says no specific secondary damage caused by the incident had been reported. As a precaution, look at the admin panel's login history and recent settings changes for anything your team did not do. If you find something, contact E-store's shop desk (phone 03-6434-0946, weekdays 10:00 to 18:00 JST).
Be alert to contacts that use your payment-slip shop details
Your sales manager's name, shop name, postal code, address, phone and fax numbers on convenience-store payment slips are included. If a suspicious call, fax or email aimed at your shop claims to be from a business partner or about a payment, do not use the contact details it gives; check through an official channel (to protect your own domain, see SPF, DKIM and DMARC).
Post a notice for your own customers
Most buyers do not know the name ShopServe, so E-store's notice alone does not tell them which shop it is about. A notice on your own site that states the affected period, the leaked items (including whether card data was involved) and a contact point lets buyers judge their own situation.
What happened (from E-store's notices)
E-store Co., Ltd., published a first notice on August 1, 2026, a second notice on August 2 and a final report on October 16. The following is taken from the company's official notices; where they differ from the second report, the final report takes precedence.
May 21 – August 1, 2026
The period in which an outside third party exploited a vulnerability in an application on the server and used a malicious program to send database contents out (final report).August 1
The company confirmed a leak of buyer data from unauthorized access to its servers and published its first notice. It said it had cut off communication with the attack source and confirmed that access was no longer possible.August 2
Second notice. It set the period as starting May 21 and added partial card data and merchants' credentials and payout account details to the leaked items (mail, FTP and the payout account details were corrected in the final report).From August
Affected shops began announcing the impact on their own sites. Announcements from shops saying E-store had informed them continued into September.October 16
Final report. An outside specialist's forensic investigation found no other intrusion route or backdoors. It put the affected count at about 23,356,000 people and corrected that shop mail and FTP credentials and E-store's payout account details did not leak.
- Buyer data
- Name, address, phone and fax numbers, email address, workplace, and other information customers entered voluntarily (including delivery details)
- Member data
- Member IDs and encrypted passwords. The company judges it unlikely the passwords can be identified, and says the data cannot link a member to a shop
- Credit cards
- Cardholder name, first 6 and last 4 card digits, expiry date (about 2,096,900 people). Full card numbers and security codes are not held and not affected
- Shop data
- Admin-panel IDs and passwords; shop details on convenience-store payment slips (sales manager's name, shop name, postal code, address, phone and fax numbers)
- Affiliates
- Email addresses and passwords
- Correction (removed from the second report)
- Shops' mail system and FTP IDs and passwords, and E-store's bank account details, were confirmed not to have leaked
- Count
- About 23,356,000 people (buyers and members, shop operators and affiliates combined) and 7,858 shops (including current and former ShopServe shops). An approximate figure after matching on several fields to remove duplicates; some duplicates that did not meet the criteria may remain
- Cause
- An outside third party exploited a vulnerability in an application on the server, ran a malicious program and sent database contents out, May 21 to August 1
- Investigation
- Attack source blocked on August 1; the vulnerability fix has been carried out. An outside specialist found no other intrusion route or backdoors, and no sign of the data on the dark web
- Secondary damage
- As of the final report, no specific secondary damage caused by the incident had been reported
- Reporting and measures
- Reported to the Personal Information Protection Commission and the Kanto Bureau of Telecommunications; police consulted. Individual notices completed (the public notice and inquiry desk stand in where contact details are unknown). Vulnerability assessments and stronger admin authentication, including two-factor authentication
- Contact
- Buyers, members and affiliates: the company's inquiry form / Shops: phone 03-6434-0946 (weekdays 10:00 to 18:00 JST)
Reading note: the leaked items differ by shop
E-store's notice lists everything that leaked across the whole service. Announcements by affected shops show that some included card data and some did not, and the affected purchase period also differs by shop.
The reliable way to know your own situation is the notice from the shop you used. If you cannot find one, ask the shop or E-store's contact.
Why one service leaked buyer data from many shops
In a service like ShopServe, many shops share the same servers and software. To a buyer they look like separate shops, but where order data is kept and the programs that handle it are shared.
Company A's online shop
Company B's online shop
Company C's online shop
↓ buyers see only each shop's name ↓
Shared servers (ShopServe)
every shop's buyer data, partial card numbers, shop admin passwords
↓ May 21 – August 1, 2026: a malicious program sends data out ↓
About 23,356,000 people
This setup has advantages. Each shop does not need its own server, and security updates can be applied in one place. But when the shared servers are breached, it is not one shop's problem but every shop's buyers who are affected.
What makes it hard for buyers is that they remember which shop they bought from, but not which service that shop runs on. That is why it is difficult to tell whether you are affected in this incident.
Not proof a message is genuine
- It shows your name, address and phone number
- The last four digits or expiry date of your card are correct
- It names a shop you have bought from
What you can check yourself
- Whether My Page or a contact point opened from the shop's official site tells you the same thing
- Whether the charge appears in your card company's official app or online statement
- Whether the message is asking you to enter a card number or password
For anyone running a service that holds data for many shops
The company names a vulnerability in an application as the cause but has not said which flaw it was. This section sticks to general points that services of the same shape (one system holding data for many client businesses) can check.
Treat "one process read many shops' data" as an alert signal
Normal order processing handles one shop's data per operation. A single process or database connection reading many shops' data in a short time is unusual outside scheduled batch jobs.
A first step: from database audit logs, count "shops touched per hour" for each connection source, and alert when anything other than a known batch job goes over a limit (for example, 10 shops).
Limit outbound traffic from servers by destination
In this case, database contents were sent out from the servers. Servers that process orders only need to reach a few destinations, such as payment processors and delivery companies.
Allow outbound traffic only to the destinations you need, and log and alert on traffic to anywhere else and on unusually large transfers. Firewalls and cloud network settings can do this.
Protect each shop's secrets separately from shop data
If credentials such as shops' admin passwords can be read from the same place as buyer data, they leave together. Store credentials in a form that cannot be restored, and keep anything that must be restorable in a separate store with a separate key.
See storing passwords safely (hashing and salt) for storage, and the minimum security baseline for organizations for the wider picture.
Give client businesses what they need to explain a leak to their buyers
Buyers only know the name of the shop they used. A single service-wide notice from the operator does not let them tell whether they are affected.
Make sure you can quickly produce, per shop, the affected period, the leaked items and whether card data was involved, and include handing that to each client business so it can explain to its own buyers in your incident-response procedure.
For other online-shopping cases, see the Abahouse breach (order data and fake refund emails) and the APORITO online store (RIZAP); for other major Japanese breaches this year, see Japan's major data breaches of 2026.
Sources (public record)
The facts in this article come from the public sources below. Undisclosed methods or causes of the intrusion are not speculated on.
- E-store Co., Ltd., apology and notice regarding a personal data leak from unauthorized access (August 1, 2026, Japanese) — estore.jp
- E-store Co., Ltd., notice regarding a personal data leak from unauthorized access (second notice, August 2, 2026, Japanese) — estore.jp
- E-store Co., Ltd., notice regarding a personal data leak from unauthorized access (final report, October 16, 2026, Japanese) — estore.jp
- Examples of announcements by affected shops (Japanese): Harima Chemicals Group, Inc. (second notice, August 10, 2026) — harima.co.jp / PFU Limited (September 18, 2026) — pfu.ricoh.com
- The shop announcements and news reports below may reflect the items and counts up to the second report; where they differ from the final report, the final report takes precedence.
- Security NEXT (Japanese) — security-next.com
- INTERNET Watch (Japanese) — internet.watch.impress.co.jp
Update history
2026-10-03: First version, based on E-store's notices of August 1 (first) and August 2 (second) and announcements by affected shops. The first notice placed the leak on the morning of August 1; the second set the period as May 21 to August 1 and added partial card data and merchant data to the leaked items.
2026-10-30: Rewritten for the final report (October 16). Corrections: (1) Shops' mail system and FTP IDs and passwords, and bank account details of the accounts E-store transfers money to (payout accounts), listed as leaked in the second report, were confirmed by the investigation not to have leaked, and were removed. The shop-owner steps for them (changing mail and FTP passwords, checking pages for tampering and forwarding rules, checking the bank account) were removed and replaced with admin-panel and affiliate steps. (2) The count changed from the second report's 8,853,839 records (possibly including duplicates) to the final report's about 23,356,000 people (buyers and members, shop operators and affiliates combined; approximate after removing duplicates). The units differ, so the two cannot be compared. New facts: the cause is a vulnerability in an application, about 2,096,900 people had part of their card data included, 7,858 shops are affected, affiliates' data is included, and forensics found no other route or backdoors. The company says the investigation is complete; we will update this article if it publishes more.
Read next
- An online printing incident: Unauthorized access to Raksul's print data submission system
- Follow-on scams: What is phishing? / Abahouse (order data and fake refund emails)
- Card data: The APORITO online store (RIZAP) card-data case
- Passwords: Choosing a password manager / Choosing multi-factor authentication
- Other incidents in Japan this autumn: Yamato Transport and Sagawa Express (parcel senders and recipients) / Times Car
- Other 2026 incidents: list of breaches and cyberattacks (Japan and worldwide)
- For operators: The minimum security baseline for organizations