tag

Japan

162 articles with this tag

2026-11-21

Japan's Digital Agency: Files on the GSS File-Sharing Service May Have Been Accessed by Someone Other Than the Intended Recipients (July 30 to November 12, Personal Data May Be Included)

On November 20, 2026, Japan's Digital Agency announced that some files handled by the file-sharing service of the Government Solution Service (GSS), which the agency operates, may have leaked outside. On November 12 it detected that someone other than the intended sharing recipients may have accessed files and began an investigation; its investigation so far confirms that such access took place between July 30 and November 12. It stopped the service on November 12. The service was used among users at government bodies and with outside parties such as contractors to share large files such as meeting materials. The agency says the files that may have leaked can be expected to include personal information. The number of files, their content and the method of access are not stated. It is working with police, has reported to the Personal Information Protection Commission, and says no secondary damage from personal information has been confirmed so far. Bottom line: officials and contractors who shared materials through GSS should take stock of what they shared and wait for guidance from their own organisation; the general public has nothing to do at this stage, other than being wary of contact claiming to be from the agency or related bodies.

2026-11-21

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

On November 19, 2026, Kyash Inc. announced that between about 9:20 and 11:42 on October 28, 2026, its internal tool was accessed from outside without authorization, and internal materials posted there may have been obtained by a third party. 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, some payment merchants, dates and amounts, and refund and settlement status; and for 310 of them, one or more of usage records, card restriction status, device identification number and source IP address. The company says name, address, phone number, email address, date of birth, registered credit card data, registered bank account data, Kyash Visa card data and passwords are not included. The cause was a deficiency in the internal tool's access control. No unauthorized access to the app or card systems has been confirmed. This site's take: within what was announced there is no setting users need to change in a hurry; watch for fake contacts imitating Kyash.

2026-11-21

LEGOLAND Japan Annual Pass Buyers' Personal Data May Have Leaked (About 150,000 People): Name, Address, Phone, Email and Barcode Number, and What Buyers Should Do

On November 18, 2026, LEGOLAND Japan LLC announced that the operator of the platform it uses to sell annual passes reported, in the early morning of November 15, that a third party had accessed the platform by exploiting a vulnerability. About 150,000 people, including buyers whose passes have already expired, may be affected. The data involved is name, date of birth, gender, address, email address, phone number and the annual pass barcode number. Credit card and bank account information is not included at this time. The company says the vulnerable connection points have been removed and a fix applied, that an external specialist organisation is still investigating, and that affected people will be contacted by email in sequence. This site's conclusion: if you have ever bought an annual pass, do not open links in emails, texts, LINE or WhatsApp messages or calls in the company's name, and do not give payment, card, verification-code or login details.

2026-11-21

Osaki Electric Ransomware Attack: VPN Login Broken, Smart Meter Production and Shipping Halted, Apparent Technical Data Posted (Second Report, November 20)

On November 18, 2026, Osaki Electric Co., Ltd. announced that its systems were hit by a ransomware attack confirmed on November 17 (first report). It stopped the production-related systems of its Saitama works and two group companies, and production and shipping of smart meters and similar products cannot take place; no restart date is set. In its second report of November 20, the company says unauthorised access is estimated to have started around 1:30 on November 15 through its VPN device, that some accounts without multi-factor authentication remained, and that it is highly likely the authentication was broken by repeated password attempts. Some virtual servers were encrypted. On November 19 it found technical information that appears to be stored on its systems posted on a site that appears to be run by the attacker; the scope is under investigation. Backups are confirmed intact, and operations will resume in phases where safety is confirmed. The company says its products and services are not affected. Bottom line: partners should confirm delivery through their business contact and ignore messages impersonating the company; any organisation with a VPN should check today that every account has multi-factor authentication.

2026-11-21

Rumoi City Resident Data (Up to 71,002 Records) and Support-Needed Data (Up to 4,503) May Have Leaked: A Contractor's Subcontractor Device Was Infected With Malware. What Affected People Should Do

In a notice dated November 19, 2026, Rumoi City (Hokkaido, Japan) said the company it contracted in August 2020 for an integrated GIS introduction project reported that a development device of that company's subcontractor showed traces of infection with information-stealing malware, and that personal data kept on the device after the contract ended may have leaked. The data that may have leaked is resident register data as of February 3, 2022 (up to 71,002 records) and data on people needing support as of March 2022 (up to 4,503 records). My Number (individual number) is not included. The city says no leak or misuse has been confirmed at this time. The device was physically cut off from the network on November 4. This site's conclusion: if you were on the city's resident register or support register at those times, do not respond on the spot to calls or messages in the name of the city or welfare staff, and check by phoning the city office yourself.

2026-11-21

Sagawa Express Baggage Storage Web Reservation Hacked (13,059 Reservations): Names, Phone Numbers and Emails May Have Leaked, and What to Do If You Booked Between April 1 and November 14

On November 20, 2026, Sagawa Express Co., Ltd. announced that its web advance reservation for baggage storage, part of the SAGAWA Hands-Free Service, was accessed without authorisation by a third party and that personal information may have leaked (published as the 7th report in its series on the September unauthorised access). It occurred on November 14 and was found on November 16. It covers people who booked on the web from April 1 to November 14, 2026; the count is 13,059 reservations (not people), 36 of which include the last 4 digits of a credit card number. The information is the reservation number, name, phone number, email address and last 4 card digits; no address is included. The company says this occurred in a different system and by a different method than the September parcel-tracking incident, that the relationship is still being investigated, and that the system had been found free of problems in a vulnerability assessment. Web reservation is suspended; the counter still accepts baggage. It has reported to the Personal Information Protection Commission. Bottom line: people affected should not open URLs in messages claiming to be from the company, and should not assume a message is genuine because it quotes a reservation number or name. The company says it will not ask for passwords, card numbers or security codes in its contact about this.

2026-11-21

SBC Medical Group (Shonan Beauty Clinic and others) customer data stolen (personal data of about 1.62 million people): names, addresses, birth dates and passwords, and what customers should do

On November 19, 2026, SBC Medical Group announced (first report) that a database held by SBC Medical Group Co., Ltd. on behalf of the group's medical institutions was hit by a cyberattack by an outside third party and customers' personal data was taken. A separate unauthorized login to the group's accounts on an external clinic booking service also took booking data. According to the notice, personal data (excluding booking and treatment information) such as name, sex, phone number, email address, password, address, date of birth, clinic card number and member ID covers 1,624,000 people; booking application data from specific web routes covers 255,416 people; and web inquiry form contents cover 217,769 people (14 of them include credit card data, all of it expired or otherwise unusable for further payments). Electronic medical records and other core systems are not covered, and no data from the booking site mySBC has been confirmed taken. The company confirmed the access on November 16, 2026 and reported to the Personal Information Protection Commission the same day. No secondary damage has been confirmed so far. This site's take: if you reuse the same or a similar password elsewhere, change it there.

2026-11-21

Tsukaeru.net Hosting (Shared Servers and Cloud VPS) Unauthorized Access: Customer Registration Data May Have Been Viewed, Shared-Server Data and Email Lost, and What Customers Should Do

Tsukaeru.net Co., Ltd. has announced its unauthorized-access incident from a flash report on November 7, 2026 to a third report on November 20. According to the third report, it confirmed unauthorized access exploiting a vulnerability in software used by its contract-management portal, Tsukaeru Portal, plus unauthorized connection to an internal system that manages customer registration data. In customer-facing service environments, it has confirmed access only on some cloud VPS host machines and some shared servers. Shared servers were restored from the November 2 backup, so data updates and email sent or received after it, up to the early morning of November 7, were lost. Name, company name, address, phone number, email address and more may have been viewed or obtained, but the scope and number of customers are under investigation. This site's conclusion: reset the portal password and two-factor authentication, replace credentials stored on your server, and check shared-server data and email for gaps.

2026-11-20

Japan's Children and Families Agency Will Not Operate the 'Komamorou' Record-Check System for Now: Many Serious Vulnerabilities Found, and What Schools, Childcare and After-School Operators Should Check (Not a Data Leak)

On November 18, 2026, Japan's Children and Families Agency announced that the 'Komamorou system', developed so that operators and staff can check past sex-offence records (criminal-record checks) under the child sexual-violence prevention law, which is due to take effect on December 25, will not be operated for the time being. After the Prime Minister instructed on October 26 that a vulnerability check using high-performance AI be carried out ahead of schedule, a vulnerability assessment of the system found many serious vulnerabilities, and the agency says handling them before the effective date became difficult. The minister apologised to those concerned and told officials to urgently consider alternative procedures that do not use the system. The agency plans to compile alternatives around early December. This is about vulnerabilities in a system that had not yet gone into operation; the agency did not announce that personal data leaked. This site's take: affected operators should stop preparing on the assumption that the system will be used, wait for the alternatives due in early December, and check the agency's official page.

2026-11-20

Rokkatei Online Shop Payment Page Tampered With (About 8,000 Cards): Card Number and Security Code May Have Leaked, and What to Do If You Paid Between October 21 and November 18

On November 18, 2026, Rokkatei Co., Ltd. announced that its own site, Rokkatei Online Shop, had been accessed without authorisation by a third party, and that the program on the payment page had been altered so that entered data may have been sent outside. People who entered credit card details on the payment page from 21:00 on October 21 to 11:00 on November 18 may be affected; the number confirmed so far is about 8,000. The card number (all digits), cardholder name, expiry date and security code may have been taken. The company says it does not store card data on its servers and that the data may have been captured as it was typed. It is still checking other kinds of information. It has stopped the site and reported to the Personal Information Protection Commission. This site's take: if you entered a card in that period, check your statements and ask your card issuer about changing the number, and do not respond to suspicious calls, mail or text messages.

2026-11-19

Customer Analytics Service Provider Breach: Member Data Leaks at 38 Companies Including DHC, JINS, GDO, MUFG Bank and Francfranc, and What Members Should Do

The provider of a customer analytics and on-site messaging service announced unauthorized access by a third party on November 13, 2026 and the scope of the leak on November 16. Companies using the service have since announced, from about November 17, that their members' information leaked or may have leaked. We opened and confirmed the official notices of 38 client companies. The largest by count is DHC (about 19.11 million records, not people), plus 37 more (JINS up to about 18.29 million accounts, a maximum; Golf Digest Online up to 6,974,506 records, MUFG Bank about 6.5 million, Francfranc up to about 5.98 million member records, CAMPFIRE 5,819,779, RIZAP and chocoZAP up to about 4.32 million email addresses, Club Tourism about 4.06 million, Ainz and Tolpe and AYURA up to about 2.6 million, Sharp COCORO STORE up to 3,264,445, J.League Ticket and WE League Ticket 2,383,073 and others). The provider itself confirmed 79,249 email addresses registered for its own service accounts. The items differ a lot by company, from items without names or contact details to names, birthdates, emails and phone numbers, and the counts cannot be added together. Our conclusion: do not open links in messages claiming to be a company, and check through the official app or site you open yourself.

2026-11-19

Nulab Cacoo Unauthorized Access: 765 Inquiry Records Leaked, 890 Payment Billing Records at Risk

On November 16, 2026, Nulab Inc. announced unauthorized access by a third party to the production environment of Cacoo, its online whiteboard and diagramming tool, and to some inquiry records it manages. On the morning of November 14 it detected that the company's own credentials were being used without authorization, and it has had Cacoo stopped since 18:45 that day. In its second report of November 18, Nulab put the confirmed leak at 765 inquiry records (down from about 792 in the first report): names, email addresses, phone numbers, addresses and so on, with the last four digits of a credit card in some. It also said two further sets of information may have leaked: billing information from an external payment service (890 records) and part of the data from a past internal investigation (310 records). Whether either was actually viewed or taken is still under investigation, and affected customers are being contacted individually. Nulab says it has found no unauthorized access to the database that stores Cacoo diagrams and account information, nor to customer data of Backlog and its other services. This site's take: if you are contacted, expect fake messages built from your name and contact details; do not open links in messages claiming to be Nulab, and check through the official site.

2026-11-19

Pokepay (Enterprise) unauthorized access: what users and merchants of Hokupay, the Fuku app and other local-currency apps should do

On November 14, 2026, Pocket Change Inc., the operator of the Pokepay electronic-money platform, announced that it had confirmed unauthorized access by a third party to the Pokepay (Enterprise) system and suspended all Pokepay (Enterprise) services from 20:00 that day. The shop-facing Pokepay was not affected and was not suspended. Service resumed at 16:40 on November 15, and the card-charge and other externally linked functions resumed on November 18. The company's notices do not list what data was exposed or how much, and say it will report the investigation results later. Kita City in Tokyo, which uses the platform, said on November 17, citing the company's report, that application information of some merchants (the representative's date of birth, address, phone number, email address, payout bank account information and so on) may have leaked, covering 801 shops; leakage of users' phone numbers and card information has not been confirmed. Mebuku Pay said that records of third-party viewing were found for seven merchants in a payment-processing contractor's system and that leakage of users' phone numbers and email addresses has not been confirmed. Our conclusion: users should check balance and history in the official app and not open links in messages claiming to be about this; merchants should not act on messages asking to confirm or change payout accounts.

2026-11-19

Rakuten Securities unauthorized access (up to about 11.25 million accounts): names, addresses and payout bank details may have leaked — what customers should do

On November 17, 2026, Rakuten Securities, a Japanese online brokerage, announced that part of the customer information it holds may have leaked after unauthorized access by a third party. It detected possible unauthorized access to some systems on November 16, blocked access and applied fixes, and its investigation found that some information managed inside a test-environment system may have been exposed on November 11. The data includes former customers who closed their accounts. Branch and customer codes and login IDs cover up to about 11.25 million accounts; names, kana names, dates of birth, addresses, phone numbers, email addresses, employers, payout bank accounts (institution, account number, holder), self-declared income and financial assets, per-product asset information and last login date cover up to about 4.47 million accounts. The company has not confirmed leakage of login passwords, PINs or other information needed to trade, and has not confirmed unauthorized access or trades caused by this incident. The cause and full timeline are still under investigation. Our conclusion: do not open links in messages claiming to be from Rakuten Securities, set up a passkey, and consider turning on the temporary trading and withdrawal suspension.

2026-11-17

AXA General Insurance Japan MyAXA Unauthorized Access (About 597,000 Records): Names, Addresses, Birth Dates, Emails and Phone Numbers May Have Leaked

AXA General Insurance Co., Ltd. (Japan) announced on November 12, 2026 that a third party had gained unauthorized access to its customer portal MyAXA. In a second report on November 13, it said that unauthorized access and leakage of some customer information had been confirmed in both MyAXA and at an outsourcing partner that handles part of its roadside assistance. The company says it noticed suspicious access to MyAXA at about 8:30 a.m. on November 9, took measures including blocking access at 10:53 a.m., and restored the service on November 12. The number of records in MyAXA that may have been accessed is about 597,000, and the information that may have leaked is customers' names, addresses, birth dates, email addresses and phone numbers. It says credit card information is not included. The range and content at the outsourcing partner are still being investigated, and the company will contact affected customers individually as they are confirmed. It says no misuse of the information or secondary harm has been confirmed so far, and the cause and scope are under investigation. This site's takeaway: expect convincing messages posing as the insurer or roadside assistance, do not open links in emails or SMS, do not enter passwords or verification codes, and check through the official website or the official phone line that you open yourself.

2026-11-17

i Cubed Systems CLOMO MDM unauthorized access: part of the data customers registered leaked — what administrators at companies using it should do

On November 16, 2026, i Cubed Systems, Inc. announced that a third party gained unauthorized access to the systems that run its services including CLOMO MDM (a service for managing smartphones, tablets and other devices), and that part of the information customers had registered in CLOMO MDM leaked. It says it confirmed suspicious access on November 2, began investigating, blocked the route and started contacting affected customers individually. It says no new unauthorized access from the same route has been confirmed, the service continues, and no outage has resulted. It has not published the specific contents of the leaked information, the number or names of affected customers, or the route of entry, saying that could give clues to abuse. No misuse or secondary harm of the leaked information had been confirmed. Individual notices go to the system administrator's email address registered with CLOMO. This reflects the situation as of November 17, 2026. Our conclusion: administrators should check whether they received the company's notice, beware of messages posing as the company, and carry out only the actions they are told to.

2026-11-17

Daiwa Living D-ROOM NAVI breach: partner data for 65,472 people and employee data for 16,450 leaked, including initial passwords — what partners and staff should do

On November 16, 2026, Daiwa Living Co., Ltd. announced that unauthorized access to D-ROOM NAVI, a site it runs for real estate brokerage companies, had leaked information. It confirmed the access on November 10, stopped the system on November 11 and has been restarting it in stages since November 12. The company says the leaked data is partner information of 77,033 records (65,472 people: company name, department, email address, phone number and the initial passwords of its D-ROOM NAVI and D-ROOM Rinc systems), employee information of 19,696 records (16,450 people, including past employees: employee number, name, work email, work mobile number, work-system password and hire date), D-ROOM NAVI account information of 143,923 records (company ID, employee ID, encrypted password) and temporarily held account information of 13,927 records. General residents and owners with no business dealings with the company are not included. The company says the leaked passwords have been unusable since the November 11 shutdown. As of November 17, 2026, the cause has not been disclosed. Our conclusion: expect realistic messages that pose as partners or colleagues, do not open their links or attachments, and change any password reused elsewhere.

2026-11-17

GoQSystem Unauthorized Access (About 4.37 Million People, 1,694 Companies): What Shoppers and Shop Operators Should Do

GoQSystem Co., Ltd. announced on November 12, 2026 that its system had been accessed without authorization and part of the order data it holds, including personal information, had been taken outside. In its second report of November 13, it gave the scale as 1,694 shops (companies), 4,984,595 orders and 4,367,390 individuals. The items that leaked are the names, addresses, phone numbers, email addresses and order details of buyers and delivery recipients. The company says credit card information is out of scope because it does not hold it. It says the cause was exploitation of a vulnerability in a contact form it had placed on its system, and that the form has been deleted. In its third report of November 16, it said it submitted a preliminary report to the Personal Information Protection Commission on November 13, and described a procedure for shops to file jointly with the company. This site's takeaway: a buyer from any of the shops may be affected. Expect messages posing as a delivery company, a shop or the company, even ones that get your order details right; do not open links, and check through an official channel you open yourself.

2026-11-17

Meetsmore breach (up to 366,850 records): customers' addresses, phone numbers and meeting URLs leaked, 201 accounts logged into — what customers and pros should do

On November 16, 2026, Meetsmore Inc. announced unauthorized access to its quote-comparison service Meetsmore. The company says a vulnerability in part of its system was exploited and up to 366,850 records (a record count, not a head count) may have leaked: customers' addresses and phone numbers registered in service providers' schedules, the identification numbers it assigns to members and requests, and online meeting URLs registered in Meetsmore. This happened between 16:27 on November 11 and 0:22 on November 12. Before that, between 15:39 and 16:27 on November 11, 201 accounts were logged into with IDs and passwords that appear to have been obtained elsewhere. The company says names, email addresses, passwords and credit card information are not part of the leaked information, and that no misuse or secondary harm had been confirmed. Our conclusion: do not respond to realistic calls, visits, texts or emails that know your address and phone number, and never give out passwords or card numbers. Service providers should reissue meeting URLs registered inside Meetsmore.

2026-11-17

MIC General Planning's Merupara and J-Mail Unauthorized Access: Member and Card Data May Have Leaked, and What Members Should Do

On November 16, 2026, MIC General Planning Co., Ltd. (Yugen Kaisha MIC Sogo Kikaku) published a first report saying unauthorized access to Merupara and J-Mail, the services it runs, may have exposed member information, phone numbers, email addresses and credit card information. The company says it detected unauthorized third-party access on November 9, began investigating on November 11, and took measures including stopping the services and blocking access. The services have been suspended since 5:30 p.m. on November 11. For card data, the company says the cause was a malicious program placed on some screens of its own website, not unauthorized access to the payment processor's systems, and that no leak from the processor's payment systems has been confirmed. The number of people affected and the scope are under investigation, and the company says it has not confirmed an actual leak, misuse or secondary harm at this point. This site's bottom line: if you used a card on these services, check your statements and ask your card issuer about changing the number, and do not respond to messages that claim to know you used the services or that demand money.

2026-11-17

Mitsui Sumitomo Insurance: Unauthorized Access to Its Policyholder Page and MS Compass (About 37,000 and 23,000 Records)

On November 6, 2026, Mitsui Sumitomo Insurance Co., Ltd. announced that unauthorized access to its policyholder-only page had led to a leak of about 37,000 records, including policy numbers, names, addresses, phone numbers and email addresses. On November 9 it announced a separate intrusion into MS Compass, an information site for small and mid-sized businesses, with about 23,000 records leaked, including company names, corporate numbers, job titles, names, email addresses and phone numbers. The company says neither leak includes credit card or bank account information, and that it has not confirmed misuse of the leaked data. The cause and full scope are under investigation. Our conclusion: do not open links in messages posing as the insurer; check through the official site or the contact on your policy documents, and never enter passwords or card details in response to a message.

2026-11-17

RIKEN supercomputers Fugaku and Rikyu unauthorized access (up to 4,597 users): treated as a leak, 430 stored credentials collected — what users should do

On November 16, 2026, RIKEN announced that an outside third party gained unauthorized access to the operations system of the supercomputer Fugaku, run by its Center for Computational Science, on November 12, and that it confirmed this on November 13. Information registered in the users' authentication system (names, email addresses and IDs for up to 4,222 Fugaku users; names and email addresses for up to 375 users of the supercomputer Rikyu) and some files in users' home directories (credentials for connecting to supercomputers and services outside RIKEN, such as SSH private keys and access keys, and research data) were taken, or may have been. RIKEN says it has not confirmed any specific fact showing research results leaked. It stopped Fugaku at 4:30 a.m. on November 14 and invalidated all users' public keys for login. In its second report of November 20, RIKEN said it had identified traces of the intruder accessing the target information and, although it has not confirmed external misuse, is responding on the premise that a leak occurred. Newly covered are the information entered at account registration (address, affiliation, other attributes and contact details such as phone number) and a record of identity verification (only the type of document used; leak of the documents themselves not confirmed), and the number of affected Fugaku users is given as 4,222. RIKEN also confirmed traces of 430 credentials for connecting to external systems (233 private keys without a passphrase, 197 with one) being collected and moved from some users' home directories, and traces of external connections with some of the credentials; it has not confirmed any other misuse. It will set up an investigation committee that includes outside experts. This site's take: revoke and reissue any SSH private keys or access keys you stored on Fugaku at the destination side, and do not open links in emails claiming to be from RIKEN.

2026-11-17

Shippio Platform Unauthorized Access (About 1,300 Document Files Downloaded, About 1,100 Teams Hit): What Client Companies Should Do

Shippio, Inc. published notices on November 4 (first report), 5 (second) and 16 (third), 2026 saying its Shippio Platform was accessed without authorization several times between about 19:30 on November 1 and about 17:00 on November 2 (JST). According to the company, an internal work tool was misused and the credentials stored in it were used to access its systems. Company names, team names, addresses and phone numbers of all customers were viewed; shipment information and document file names and types were viewed for almost all customers that have registered shipments; and about 1,300 document files were actually downloaded. Unauthorized user accounts and API credentials were created in about 1,100 customer teams. The company stopped the service on November 2, restarted it on November 5 and reset all users' passwords. It says it has confirmed no misuse of the leaked information. Our conclusion: reset your password, do not open documents you do not recognise, and verify shipment or invoice messages through a separate channel.

2026-11-17

Uchicomi ransomware attack (142,591 accounts): names, addresses and phone numbers may have leaked — what members should do

On November 4, 2026, Uchicomi Inc. announced that the server of its site Uchicomi! was hit by ransomware by a third party and that members' personal information may have leaked. It says a failure occurred on the server on July 6, it investigated and isolated systems, and a later expert investigation found that some files on the server had been encrypted and stolen. Up to 142,591 accounts may be affected. The items that may have leaked are name, email address, date of birth, gender, address and phone number; which items the company holds differs by member. It says it holds no credit card information and that all passwords are encrypted. As of the announcement, no misuse, secondary damage or publication on the internet had been confirmed. This site's take: expect messages that already know your name, address and phone number, do not open links in anything claiming to be from the company, and change the password on other services if you reused it.

2026-11-17

Yasukuni Shrine Online Shop Data Breach (About 14,500 Records): Names, Emails and Password Information

On November 11, 2026, the Yasukuni Shrine administrative office announced that its online shop for amulets and distributed items was accessed without authorization, as discovered on October 28, and that it took the site offline the same day. Its investigation confirmed that part of registered users' personal information leaked: names, email addresses, information related to account passwords (hash values and auxiliary information used to generate them) and account management information (registration date and time, usage status). About 14,500 records are affected, a figure that may change as the investigation continues. The shrine says credit card numbers, expiry dates, security codes, addresses, phone numbers, dates of birth and purchase history are not among the confirmed leaked items, and that no secondary harm has been confirmed. Our conclusion: if you reuse the password elsewhere, change it there today, and do not open links in messages posing as the shrine.

2026-11-15

Unauthorized access to a company that handles e-commerce logistics (warehousing and shipping) may have leaked delivery data from several online shops: names, addresses, phone numbers and more — what buyers should do

On November 11, 2026, a company that handles logistics (warehousing and shipping) for e-commerce shops announced that an outside third party had gained unauthorized access to its systems between November 8 and 9, and that part of its shipping data had been taken. In its first notice (November 11) the data covered shipping requests made from April 8 to November 8, 2026; its second notice (November 17) adds shipping requests from October 27, 2017 to November 25, 2024 and November 9, 2026 (the added periods are partial data). The information confirmed as leaked is the recipient's name, address and phone number, the email address (if registered), item and amount information, and order and tracking numbers. The company says it does not hold credit card numbers, so they are not affected. The number of people is under investigation, and as of November 17 no misuse or secondary damage had been confirmed. Online shops that outsource logistics to this company have published the effect on their own customers on their official sites (this article lists the seven whose official notices we were able to read; counts are as each shop states them and no total is given). Our conclusion: buyers should assume that contact pretending to be a courier, the shop you bought from or an order can look genuine, and should not respond to payment demands or confirmations from anyone who knows their contact details and what they bought.

2026-11-15

Unauthorized access to GFS Education's GFS member site (about 110,000 people, My Number Card back images for 84): ID document images and password-related data leaked or may have leaked — what affected people should do

On November 13, 2026, GFS Education Inc. announced that a third party had gained unauthorized access to the GFS member site it operates, and that some personal information and information containing individual numbers (My Number) has leaked or may have leaked. The company detected an abnormal server load on November 9, investigated, and found the access. The personal information covers about 110,000 people (members, former members, applicants and people who sent inquiries) and includes name, email address, date of birth, password-related information (values protected when stored), phone number, address, viewing and purchase history, inquiry content, submitted homework images and images of ID documents. For 84 of them, the data includes the back of the My Number Card (which shows the 12-digit individual number). The company stores credit card numbers partly masked and says leakage of full card numbers has not been confirmed. The cause was the exploitation of a program flaw in the image upload feature, which let an attacker place and run a malicious program, together with a flaw in the server's access permission settings. As of November 15, 2026, no follow-up has been found. Our conclusion: change your password, and if your ID document images or the back of your My Number Card are involved, watch for notices of contracts you did not make and for contact that pretends to be the company or a public agency.

2026-11-15

Unauthorized access to Keisei Electric Railway's Skyliner seat reservation system (up to about 3.37 million records): user IDs, encrypted passwords, names, phone numbers and email addresses may have been obtained — what users should do

On November 13, 2026, Keisei Electric Railway announced that a third party had gained unauthorized access to its Skyliner seat reservation system late at night on Wednesday, November 11, 2026. Customer information of the Skyliner Ticketless Service may have been obtained, covering up to about 3.37 million records. The items are user ID, password, name in kana, phone number and email address; the company says the passwords are encrypted, so a third party cannot recover them. Affected customers will be contacted individually at their registered email address at a later date. To strengthen security, the company has suspended the whole seat reservation system, and it has not said when it will resume. Skyliner tickets are still on sale at station counters and ticket machines. As of November 15, 2026, no follow-up notice had been found. This site's conclusion: names, phone numbers and email addresses can be used to make genuine-looking contact, so be ready for emails, texts and calls in Keisei's name. The company says the passwords are encrypted, but if you reuse the same password on other services, change it there as a precaution.

2026-11-15

Unauthorized access at the provider of a LINE delivery tool: Keihan Holdings, Kintetsu Real Estate and Human Adjust say official-LINE friend data may have leaked — what registrants should do

On November 12, 2026, the provider of a cloud-based delivery tool for LINE official accounts announced that a third party had gained unauthorized access and obtained customer information of multiple companies and organizations. The access ran from 23:04 on November 9 to 09:17 on November 10, after the credentials of the provider's internal accounts used for operations and support were improperly obtained. Keihan Holdings (November 14), Kintetsu Real Estate (November 13) and Human Adjust (November 13) then published the scope for their own accounts. In its final report of November 20, Keihan Holdings fixed the affected numbers and leaked items for its six official LINE accounts and gave a total of 214,639 people after removing duplicate registrations. Higashikagura Town (November 13) also said that registration data for 1,505 accounts of its official LINE may have been obtainable. On November 16, Feiler Japan (friends of its prize-draw LINE account: up to 764,429, of whom up to 147,164 people had name, phone number and address affected) and Nissin Foods (1,374,157 LINE friends, plus name, address and phone number of 543 campaign winners) also announced that they were affected through the same tool. On the same day the Hokkaido Tourism Organization announced that up to 63,708 friend records of its official LINE account HOKKAIDO LOVE! (of which up to 14 campaign applicants had name, phone number and address affected; the two groups overlap) had leaked. Except for Keihan Holdings (whose figures are now final), counts are the current maximum and may change. The items centre on the LINE display name, profile image (URL) and LINE user ID. For Keihan Department Store, some people had at least one of name, phone number, email address, address, date of birth or gender affected (the final report gives the breakdown), and for Human Adjust up to 58,510 people had at least one of similar items. The provider says the tool does not hold credit card information, and Keihan Holdings' notice also says the service does not hold it. Kintetsu Real Estate, Feiler Japan and Nissin Foods say they confirmed the friend-data leak, and Keihan Holdings confirmed the leak in its final report, while Human Adjust says it is possible. The counts other than Keihan's may overlap, so this article gives no total. As of November 17, 2026, the cause (how the credentials reached a third party) is under investigation. Our conclusion: even when a message arrives through an official LINE account, do not act on anything that asks you to enter information or pay through a link until you have checked it on the official website or app.

2026-11-15

Unauthorized access to Monex Securities' account-opening system (up to 1.13 million email addresses, 1,592 ID document images): what may have leaked and what to do today

On November 13, 2026, Monex Securities announced that unauthorized access to part of its account-opening systems, which are run and managed by an outsourced contractor, may have leaked personal information. The contractor detected an attempted unauthorized access on October 18 and cut off external access on October 19 (account opening is currently partly suspended). An interim report from an external forensic firm named, as confirmed so far, two kinds of data: up to 1.13 million email addresses (registered in the first step of online account-opening applications since October 16, 2019) and 1,592 ID document image files (the front of My Number cards, the front and back of driver's licenses, and selfie images). Account numbers, login passwords and trading passwords are not in the same database, and the company says it has confirmed they have not leaked as of now. No leak of the My Number or the back of the My Number card has been confirmed. The investigation continues, and the figures may change after further review. No unauthorized trading or impact on assets has been confirmed. The cause is under investigation. Our conclusion: if your email address may be affected, do not open links in email or SMS that claim to be from Monex Securities; if images of your ID documents may be affected, watch your accounts for impersonation attempts.

2026-11-15

Unauthorized access at Snow Peak (reuse buyback 24,948, event reservations 5,923, community app 21,553): bank transfer details and more may have leaked — what affected customers should do

On November 13, 2026, Snow Peak announced unauthorized access by a third party to several online services. For the reuse buyback service, 24,948 people (still under investigation) may be affected: in addition to name, address and date of birth, the bank account information used for payouts (bank name, branch, account type, account number and account holder name) may have leaked. For the event reservation system, data on 5,923 people may have leaked, including applicants' and companions' names and application details. For the community app, 21,553 people may be affected, and the data is the member number, display name, self-introduction text and cover image. The company attributes each to a vulnerability in the service. Credit card information and passwords are not included (for event reservations, leakage has not been confirmed). Separately, unauthorized logins using IDs and passwords that appear to have been obtained elsewhere were confirmed on up to 445 accounts of the official online store and official member app. The counts are separate figures for each service, and no combined total has been announced. The company says no secondary damage has been confirmed and has suspended four services (the online store was due to reopen on November 13; whether it has reopened is unconfirmed). As of November 15, 2026, no follow-up has been found. Our conclusion: if you used the reuse buyback service, check your bank account's transactions and be ready for contact that pretends to be the company, a bank, or a payment.

2026-11-15

Unauthorized access to Yamada Denki's renovation management system (up to 3.5 million records): names, addresses, phone numbers, renovation history and quotes may be affected — what customers should do

On November 13, 2026, Yamada Denki Co., Ltd. announced that its renovation management system had been accessed without authorization by a third party. It confirmed the access on November 12, immediately blocked access from outside and began a detailed investigation. The personal information that may have been affected is that of customers registered in the system: name, address, phone number and other sales records such as renovation history and quotation data, for up to 3.5 million records. My Number and credit card information are not included, and information unrelated to renovation (such as appliance purchases in stores or on the online shop) is outside the scope. Whether customer information was leaked outside is still under investigation, and the company says it will announce further developments. As of November 15, 2026, no follow-up has been found. Our conclusion: this is not yet a confirmed leak, but be wary of emails, texts and calls pretending to be Yamada Denki, and remember that the company says it never asks for passwords or PINs by email or phone.

2026-11-15

Cyberattack on the Yomiuri Giants fan club CLUB GIANTS: 807,030 member email addresses leaked — what members should do

On November 13, 2026, the Yomiuri Giants announced that the system managing member information for its official fan club, CLUB GIANTS, was hit by an external cyberattack and that 807,030 member email addresses leaked. The attack began around 3:00 a.m. on November 12, the addresses leaked by around 9:00 a.m., and the count was established at 1:00 p.m. on November 13. The club says it does not hold credit card information in that system, so it is not affected, and it has received no reports of misuse so far. It is still investigating whether anything other than email addresses leaked. The attack has been blocked, and the club reported the matter to the Personal Information Protection Commission on November 13. It plans to contact affected members individually by email and other means. It warns that suspicious emails pretending to come from the club or related parties may be sent, and asks people not to open URLs or attachments in them. Our conclusion: what leaked is email addresses, which makes fake messages in the name of the Giants or the fan club look convincing, so do not open links in such messages and check through the official site or app instead.

2026-11-14

Unauthorized access to a digital bond contractor: customer data at Marui Group, Sony Bank, Kintetsu and others may have leaked — what affected people should do

The contractor that provides management systems for digital bonds and digital securities (security tokens) was accessed by a third party on October 29, 2026, and customer data held by issuers and distributors may have leaked. This site confirmed official notices from 10 companies. Marui Group says up to 9,086 people (54 of them with bank account numbers), Sony Bank 621 people (4 with account numbers), NTT Data 111 and 2,678 bond purchasers (separate groups) plus staff users, Rakuten Securities 362 cases in total, Kagome 109 people, Kintetsu Group Holdings 2,678 cases, West Japan Railway 2 cases, Phillip Securities Japan 162 people, Starts Securities names and holdings, and Pan Pacific International Holdings is still investigating. Companies count differently and the same person may appear in more than one, so the numbers cannot be added up. Marui Group says credit card information did not leak because it was not entrusted to the contractor. This site's conclusion: the data is mostly names and contact details given at application, so do not respond to contact in the name of these companies, and check your account activity if bank account numbers may be included. As of our check on November 14, 2026, the follow-ups were Sony Bank (updated November 2 and 4), Phillip Securities Japan (November 2), NTT Data (second report, November 2) and PPIH (first report only).

2026-11-14

Yeny's ultra pay Card and three other services: member data leaked (1,332,505 records): phone numbers and member IDs, and what users should do

On November 12, 2026, Yeny, Inc. announced that part of the member information (phone numbers and the company's own member IDs) for ultra pay Card, Azul Claro Numazu Pay (アスルクラロ沼津Pay), Kamigami Kon Pay (巫神こんPay) and Toshiba Brave Lupus Tokyo Pay (東芝ブレイブルーパス東京Pay) leaked because of a flaw in an API connection setting. The count is 1,332,505 records, including former members. It is a number of records, not people, and no per-service breakdown is given. The company says leaks of payment information such as credit card numbers have not been confirmed, and that the leaked information alone cannot be used for unauthorized login to its app or for payments. It says it was told of suspicious API calls by a connected business on October 31, confirmed the leak on November 5, and reported to the Kanto Local Finance Bureau and the Personal Information Protection Commission on November 6. Affected users will be notified in the app's notice section. As of November 14, 2026, we found no follow-up. This site's conclusion: because phone numbers leaked, be ready for SMS and phone scams that use the name of ultra pay or the teams, and check the official app's notices to see whether you are affected.

2026-11-13

Unauthorized access to the Japan Chamber of Commerce and Industry's online exam management system (up to about 980,000 people): names, birth dates, pass/fail results and scores may have leaked — what test-takers should do

On November 10, 2026, the Japan Chamber of Commerce and Industry (JCCI) announced that unauthorized access to the external server it uses for its online exams (the exam management system) may have leaked test-taker information. A malicious file was placed on November 1; JCCI confirmed it on November 4 through a report from the system management company, deleted it and applied a vulnerability fix (patch) the same day. On November 9 the scale was found to be up to about 980,000 people (about 1.97 million records), and JCCI reported it to the Personal Information Protection Commission. The scope is people who took any of eight online exams, including bookkeeping and Retail Marketing, from April 1, 2022 to November 4, 2026. Name, name in kana, sex, date of birth, pass/fail result and score, plus the optional email address, phone number and address, may have leaked. Payment information is not included, and no leak or misuse has been confirmed. As of November 13, 2026 we found no follow-up. Our conclusion: be ready for fake emails, texts, calls and mail in the name of the Chamber of Commerce, and do not trust a sender just because they know your result or score.

2026-11-13

Unauthorized access to Netmile, run by Wills (up to about 5.49 million people): names, email addresses and more may have leaked — what members should do

On November 2, 2026, Wills Inc. announced that a third party had gained unauthorized access to the system environment of Netmile, a point-exchange service it runs in its advertising business, and that some members' personal information may have leaked. Up to about 5.49 million people may be affected, including members who have left. Name, email address and other information related to reward exchange may be included, and the type of information stored differs by member. The company does not hold credit card information or My Number Card information. It has not confirmed that the information was published or spread on the internet, or that it has been misused. To prevent secondary harm and for security measures it has suspended the Netmile and Sugutama sites, with no restart date. Netmile's notice says it guarantees held miles and that miles will not expire during the suspension. The date of the access, the date of detection and the cause have not been disclosed. As of November 13, 2026 we found no follow-up. Our conclusion: be ready for fake contact in the name of Netmile, banks and exchange partners, and change the password on any service where you reused your Netmile password.

2026-11-13

Unauthorized access to Shiseido's skin analysis system (2,515 records): names, email addresses, questionnaire data and skin measurement results leaked — what users should do

On November 6, 2026, Shiseido announced that an outside third party had gained unauthorized access to the online skin analysis system "Facial Condition Analyzer (FCA)" used by its group's skin measurement services, and that some personal information had leaked. It confirmed the unauthorized access on October 27 and suspended some services from that day. The investigation found that some information in the system had been altered and data had been taken outside. A total of 2,515 records leaked: name, email address, age, gender, member ID, questionnaire data and skin measurement results (including date and time). Face images taken during measurement are not included, and the system does not handle credit card information. Two services where a leak was confirmed and five more services that use the same system are suspended as a precaution; no restart date is set. Shiseido has reported the matter to the Personal Information Protection Commission and the police, and the cause and scope are under investigation. As of November 13, 2026, no follow-up notice had been found. This site's conclusion: users should not respond to emails in the name of Shiseido or its brands, and should check whether they have used these skin measurement services.

2026-11-13

Unauthorized access to SMBC Nikko Securities' employee stock plan system (up to 56,487 members): names, addresses and transfer account information may have leaked — what plan members should do

On November 11, 2026, SMBC Nikko Securities announced that a third party had gained unauthorized access to the system it uses to administer employee stock ownership plans (mochikabu-kai) and that personal information of plan members had leaked or may have leaked. It confirmed the unauthorized access on November 9, blocked access to the system the same day and suspended the service. Up to 56,487 members are covered. The items are: plan name, investment stock information, member ID number, name, address, dividends and taxes, holding balance and transfer account information; the items that leaked differ from member to member. Phone numbers and email addresses are not registered in the system and did not leak. The company says no secondary damage caused by this incident has been confirmed. The cause and scope are under investigation, and the company says it will contact the affected plans individually. As of November 13, 2026, no follow-up notice had been found. This site's conclusion: plan members should not respond to contact in the company's or the plan's name, should check the deposits and withdrawals on the account where dividends are paid, and should wait for guidance from their plan's administration office.

2026-11-12

Unauthorized access to Edion's online store (order data on up to 9,554 customers and more): card details, gift card PINs and login credentials may have leaked — what users should do

On November 6, 2026, Edion Corporation announced that unauthorized access to the server hosting its online store may have leaked some customers' personal information, and on November 9 its second report corrected and added to that notice. The first report listed information recorded in log files for up to 4,131 customers (name, email address, phone number, date of birth, address, customer number and more) and order information for up to 9,554 customers (name, order number, order amount, credit card expiry date, gift card number and more), and said credit card numbers and login passwords were not included. The second report corrects this: credit card information recorded in order-time error logs (number, expiry date, cardholder name, security code) for up to 5 cases, Edion Gift Card information for 5,360 cards (number, PIN, usage history), and login IDs and passwords for up to 1,141 customers were included. It also says a malicious program had been inserted into payment-related processing by an outside third party and had been running since just after 19:00 on November 4. For card details newly entered on a PC at the payment input screen (up to 556 entries), the company cannot rule out that they leaked directly to a third party; smartphones were not affected. The company stopped the online store and related services at 22:00 on November 7, and the online store has no restart date. This site's conclusion: if you entered a new card on Edion's online store from a PC after 19:00 on November 4, check your statement and ask your card company about changing the card number.

2026-11-12

Kyushu Electric Power Transmission and Distribution unauthorized access (4,139 electricity usage records): usage and sales volumes and supply point numbers may have leaked — what customers should do

On November 5, 2026, Kyushu Electric Power Transmission and Distribution announced that unauthorized access to its system may have leaked part of the electricity data it holds (4,139 records) outside the company. It detected an unnatural error on October 30, investigated, found a possible unauthorized access, and urgently stopped the system. A server log investigation showed that information may have leaked. The information that may have leaked is: electricity usage (monthly values and 30-minute values) with the demand-side supply point identification number, and electricity sold (monthly values and 30-minute values) with the generation-side receiving point identification number. Contract information such as customer names, addresses, phone numbers, email addresses and bank account information is not included, the company says. It reported to the Personal Information Protection Commission and the supervising authority on November 2, and plans to notify affected customers individually around mid-November under the Act on the Protection of Personal Information. The Electricity Usage and Charge Inquiry web service, for customers on remote islands and registered members who sell electricity to the company on mainland Kyushu, is stopped, and no restoration date has been set. The company says the stable supply of electricity is not affected. As of November 12, 2026, we have found no follow-up. Our conclusion: because contact details are not included, wait for the individual notice and be ready for fake notices and for calls that use the supply point number to push a contract switch.

2026-11-12

Unauthorized access to the e-ticket service teket: names, email addresses and other member data leaked — what buyers and organizers should do

On November 8, 2026, teket Inc. announced (first report) that unauthorized access by a third party to its e-ticket sales and management service teket had leaked some member information. On November 5 it judged that unauthorized access was highly likely, and it stopped the service and blocked the access at 20:30 the same day. On November 6 it confirmed unauthorized access to the system that manages member information and that information had leaked. The confirmed leaked information is the name and email address of all members and, for members who registered or purchased only, date of birth, age, gender, address, phone number and ticket information (the code used to issue the ticket and the serial code issued by the organizer). The number of people affected is still being examined. The company says it has not confirmed secondary harm such as unauthorized logins, and it reported to the Personal Information Protection Commission on November 6. All services are stopped and there is no restart date. This site's conclusion: be ready for fake emails and texts that use the name teket, and keep your purchase confirmation email for any event held during the outage.

2026-11-11

Unauthorized access to Sharefull's internal management system (up to about 7.5 million accounts): names, bank details, emergency contacts and more may have leaked — what workers should do

On November 9, 2026, Sharefull announced that a third party had gained unauthorized access to its internal management system and that users' personal information may have leaked. The access occurred around 23:30 on November 4, was detected around 09:45 on November 5, and the route was blocked the same day. Up to about 7.5 million individual accounts may be affected. The information that may have leaked is: name and name in kana, phone number, email address, address, date of birth, bank account information for salary payments (PINs and passwords are not included), the URL of the face photo, emergency contact (relationship to the user and phone number), residence-status-related information, and account attributes such as registration date, number of jobs worked and preferences. Pay and points, contract and work data, and images of ID documents are not affected, and the company says it holds neither My Number nor credit card information. A separate notice the same day covers contact details of employer companies (up to about 7,500 companies). As of November 11, 2026, no follow-up notice had been found. This site's conclusion: because bank details, emergency contacts and residence status may be included, be ready for contacts that use Sharefull's or an agency's name, calls pretending to be a family member's emergency, payments made to look like mistaken transfers, and demands for money citing your residence status.

2026-11-11

Unauthorized access to Sumitomo Life's Vitality application system (about 80,000 people): names, addresses, phone numbers and partly masked card numbers leaked — what users should do

On November 9, 2026, Sumitomo Life Insurance Company announced that unauthorized access by a third party to the system of a company it outsources system work to had leaked information on about 80,000 people who use or have used 'Sumitomo Life Vitality Trial / Corporate' and 'Vitality Smart' (including the employee-benefit type). The leaked items are any of name, address, phone number, date of birth, email address and credit card number (partly masked); card numbers were leaked for about 1,000 people. Insurance contracts, and data such as step counts from use of Vitality or the Vitality health program that accompany insurance contracts, are not included. The company confirmed the access on November 2 and has suspended new applications and some procedures. The cause is not stated in the notice. The roughly 80,000 are users of these services, not all Sumitomo Life policyholders. This site's conclusion: if you used these services, check your card statement, and do not use the links or phone numbers in any message that claims to be from Sumitomo Life; verify through the official contact point.

2026-11-10

Unauthorized access to Mitsui Direct General Insurance's website (about 234,000 records): names, addresses and vehicle details leaked — what people who got a quote or bought a policy should do

On November 6, 2026, Mitsui Direct General Insurance Co., Ltd. announced that a third party had gained unauthorized access to its website and that part of its customer information had leaked. It detected the access early on November 4 and has suspended all procedures on its website and app. The affected people are customers who got a quote or took out a policy, about 234,000 records (as of 13:00 on November 6). The leaked items are policyholder and named-insured information (name, address, phone number, date of birth, email address and so on), vehicle information (vehicle name, registration number, owner and so on), and policy terms and coverage. Credit card information, bank account information and My Page login passwords are not included. On November 9 the company separately reported a follow-up on unauthorized access to the server of its roadside-assistance contractor: about 45,000 customers (as of 09:00 on November 6), and this one includes bank account information. As of November 10, 2026, no cause has been disclosed. This site's bottom line: a message using the Mitsui Direct name is not genuine just because it knows your address, vehicle or policy details. Do not open links in messages that arrive while procedures are suspended; check the official site or the contact line.

2026-11-10

Nitori unauthorized access: personal data of up to 37.62 million records may have leaked (names, addresses, phone numbers, birth dates) — what individual and corporate members should do

On November 9, 2026, Nitori Holdings Co., Ltd. announced that it confirmed unauthorized access by a third party to a system it manages on November 6, and that personal information held on its servers, up to 37.62 million records, may have leaked externally. The data covers individual members and purchasers at the Nitori Group (member number, name including furigana, email address, address, phone number, date of birth, gender), corporate members (member number, company name, department, representative's name, company address and phone number, and the contact person's name, email address and phone number), and order data placed through Nitori Net and the official Nitori shop on e-commerce malls. The company says login passwords and credit card information are not included. Third-party access may also have taken place from mid to late October, the route is under investigation, and the count may change. The company says it will contact affected customers by email or post in turn. As of November 10, 2026, no follow-up notice had been found. This site's conclusion: because address, phone number and name are all in the data, a call, text or email using the name of Nitori or a delivery company is not genuine just because it knows your correct address or order.

2026-11-10

Unauthorized access to Raksul's print data submission system (count being tallied): names, addresses and phone numbers in print data may have leaked — what customers and people named on printed items should do

On November 9, 2026, Raksul Inc. announced that the system involved in processing data submissions for its Raksul service had been accessed without authorization by a third party, and that personal information may have leaked externally. The access came to light at about 00:20 on November 8, 2026. The company says credentials for its own system were obtained illegitimately, leaving part of the stored data reachable from outside. The information that may have leaked is names, company names, addresses, phone numbers, email addresses and similar details in print data submitted to the service, and in data such as invoices and Web Yubin (online postal mail). Print data such as business cards and postcards may also contain information about people other than the person who ordered. The count is being tallied. The company says it has confirmed that credit card information, login IDs and passwords did not leak. It stopped some services on November 8 and began restoring them in turn from 07:00 on November 9. As of November 10, 2026, the count and details of the cause have not been disclosed. This site's bottom line: not only people who ordered business cards or postcards but also the business contacts and recipients named on them may be affected. Customers should know what could happen to the people they put on printed items and consider explaining it to them.

2026-11-09

Unauthorized access to Euglena's akyrise online store (up to about 900,000 records): names, addresses and phone numbers may have leaked — what buyers should do

On November 5, 2026, Euglena Co., Ltd. announced that the online store of its cosmetics brand akyrise was accessed without authorization by a third party on November 4, and that member information leaked. The company closed the store the same day and filed a preliminary report with Japan's Personal Information Protection Commission. The information that may have leaked falls into two groups: login account information (customer ID, email address and the login password, which was stored in hashed form), up to about 490,000 records; and registration and purchase information (name, address, phone number, date of birth, gender, email address, and purchase and delivery information), up to about 900,000 records. Both counts are still being verified, and since the company does not say how they overlap, the two figures cannot be added together. Credit card numbers are not held on the company's servers and are not included. The same notice also covers separate unauthorized access at an email delivery service provider and a delivery company, which the company describes as independent events. As of November 9, 2026, no follow-up notice had been found. This site's conclusion: a message, text or call using the akyrise name is not genuine just because it knows your name or address. Do not open links, and if you reused your akyrise password elsewhere, change it there first.

2026-11-09

Unauthorized access at Rohto Pharmaceutical's mail-order business (2,797,545 people in the customer system, 9,715 card numbers in call recordings): what phone-order customers and everyone else should do

On November 6, 2026, Rohto Pharmaceutical Co., Ltd. published the results of its investigation into unauthorized access to the phone system used for its mail-order business. Names, addresses and phone numbers of 2,797,545 people in the customer management system were taken (the items differ by person), and credit card numbers and expiry dates contained in call recordings were taken for 9,715 people. Card security codes and passwords are not included. The cause was that account credentials for the phone system were used by a third party without authorization. The outside expert investigation of the phone system finished on October 16, and affected people are being notified individually by post, email or similar means, in turn. No secondary damage attributable to the incident has been confirmed. This site's conclusion: if you may have read out your card number on a mail-order call, check your card statements whether or not you received a notice, and talk to your card issuer if worried. Everyone else should be wary of calls, emails and text messages from people who know their name, address and phone number.

2026-11-09

Unauthorized access to the online mahjong game Maru-Jan (1,855,578 members): email addresses and passwords leaked — what members should do

On November 7, 2026, Signaltalk Co., Ltd. announced that unauthorized access to Maru-Jan, the online mahjong game it operates, had leaked the email addresses and passwords of 1,855,578 members. The company says a function of its administration system was abused and that data including member information was downloaded externally by about 15:00 on November 4. The affected group is all Maru-Jan members; email addresses are included for members who registered one. Credit card numbers are not included because the company does not hold them. The notice does not say how passwords were stored (for example whether they were hashed). The company says it identified the intrusion route, applied a fix and resumed service at 16:00 on November 7. It asks members to change their Maru-Jan password, change the password at any other service where they used the same one, and watch for suspicious emails. As of November 9, 2026, no follow-up notice had been found. This site's conclusion: change the password at any service where you reused your Maru-Jan password before anything else, and do not open links in emails that use the Maru-Jan name.

2026-11-09

SMBC Consumer Finance loan guarantee system breach (up to 320,118 people): driver's license numbers, employer details and income leaked — what bank card loan customers should do

On November 5, 2026, SMBC Consumer Finance Co., Ltd. announced that a third party had gained unauthorized access to the system it uses for its loan guarantee business and that data had been sent out of the system. It detected the access on November 2, cut off access to the system the same day, and confirmed the leak while investigating further. Up to 320,118 people are affected. The company guarantees card loans issued by regional banks, credit unions (shinkin banks) and internet banks, so those affected are likely mainly people who borrowed a card loan from such an institution with this company as guarantor (the company does not define who is affected). The leaked information is name, sex, date of birth, address, home phone number, mobile phone number, email address, driver's license number, employer information (phone number, income and so on) and contract information (financial institution code, customer number, guaranteed amount, guarantee start date and so on). Images of identity documents such as driver's licenses are not included. After it pins down the scope, the company plans to notify affected people individually by email, SMS and similar means, in consultation with its partner institutions; no timing is given. A toll-free number was added on November 6. As of November 9, 2026, we found no follow-up notice. This site's view: a call, email or text claiming to be from your lender or guarantor is not genuine just because it knows your license number or income.

2026-11-07

NTT Docomo online shop and My docomo breach (up to about 300,000 records): ID document numbers leaked — what customers should do

On November 4, 2026, NTT Docomo confirmed unauthorized access from outside to the Docomo Online Shop and My docomo, and from about 1:05 a.m. on November 5 it stopped procedures on both and began emergency maintenance. In its second report (November 5) the company said some customer information had leaked through unauthorized access before the maintenance, and in its third report (November 6) it put the number at up to about 300,000 records. For all affected customers the leaked data is name, date of birth and age; address, contact phone number and email address; the number of an identity document; mobile phone number and contract start date; and the rate plan, options and discounts. For some customers it also includes the name and contact details of a legal representative or procedure agent, the workplace or company name and address, the financial institution, branch, account number and account holder name, and information on a childcare support programme. The cause is given as unauthorized access from outside; the route and the exact scope and count are under investigation, no new leak has been confirmed, and the time of recovery is undecided. As of November 7, 2026, no fourth report was found. Our bottom line: a call or message that quotes your name, address or contract details is not proof it is from Docomo. Do not open links, do not give PINs, passwords or card details, and if an ID document number leaked, watch for fraudulent contracts.

2026-11-07

Unauthorized access to Hotto Motto's newsletter delivery service (up to about 7 million records): names, dates of birth and phone numbers leaked — what members should do

On November 4, 2026, Plenus Co., Ltd. announced that the Hotto Motto newsletter delivery service, provided by an outside contractor, had been accessed without authorization by a third party and that member information including customers' email addresses had leaked. The company received the report from the contractor on November 2. The incident occurred from October 28 to 31 and covers up to about 7 million records. The leaked information is member information that includes email addresses, names, dates of birth and phone numbers. Credit card information is not included, and the company says it does not hold card information. No impact on the online ordering service has been confirmed, and it remains available. The newsletter delivery service has been fully stopped, with no date set for restarting it. As of November 7, 2026, no follow-up notice had been found. This site's conclusion: an email that uses the Hotto Motto name is not proof of anything just because it knows your name or birthday. Be especially wary of anything that looks like the newsletter while delivery is stopped, and check through the official site or app instead of clicking links.

2026-11-07

Unauthorized access at Iris Plaza (data on about 7.7 million people): names, addresses and encrypted passwords may have leaked — what members and shoppers should do

On November 5, 2026, Iris Plaza Co., Ltd., part of the Iris Group, said in a second notice that unauthorized access to Iris Plaza, the official Iris Ohyama online store, may have leaked part of its customers' personal information. On October 28 the company found suspicious files in an external cloud service it uses, immediately stopped Iris Plaza and related systems, began an investigation and confirmed unauthorized access by a third party. The personal data stored in the external cloud service covered about 7.7 million people, and the company has confirmed that this data may have been viewed or obtained. The actual number of records leaked and people affected is still under investigation. The information that may have leaked is, for member data (about 5.8 million people, including former members), name, address, phone number, email address, gender, password (except for former members), date of birth and more, and for non-member data (about 1.9 million people, including people who bought without registering or entered campaigns), name, address, phone number and email address. Some items, including passwords, are encrypted. The company says credit card information was not stored in that cloud service and has been confirmed as unaffected. It asks people who use the same password elsewhere to change it. As of November 7, 2026, no third notice had been found. This site's conclusion: if you use your Iris Plaza password on any other service, change it today. Former members and people who bought without registering are also covered.

2026-11-07

NIKKE (Goddess of Victory) PC Launcher Files Were Tampered With and a Malicious Program Was Distributed: What Windows Users Since September 27, 15:41 JST Should Do

On November 5, 2026, the operator of Goddess of Victory: NIKKE (Level Infinite) announced that some files of its PC launcher had been tampered with by a third party, so a malicious program could run when the launcher started. According to the operator, an external domain used by part of the game service was taken over on September 27, four official CDN scripts that the launcher downloads were tampered with at 15:41 JST that day, and distribution of the malicious program through those scripts began at 3:52 on October 30. It noticed the anomaly on November 4 and replaced the scripts to block further distribution. Anyone who started the Windows PC launcher at least once since 15:41 on September 27 is in scope; people who play only on mobile are not affected. The operator says the PC, accounts on external services and assets may be affected, and since 8:00 on November 5 it has offered a scan-and-remove function in the official PC client. The scope of damage and the route of tampering are under investigation. This site's take: if you are in scope, use a separate clean device to change passwords (email, banking, crypto, game stores, Discord first), sign out other sessions, re-issue API keys and tokens, and turn on two-factor authentication.

2026-11-07

Suntory Group Personal Data Leak (About 90,000 Employees and Partner Staff, and Other Groups): Names and Email Addresses Leaked After Unauthorized Access to an External Cloud Service, and What Applicants and Customers Should Do

Suntory Group announced on November 2, 2026 that it had confirmed unauthorized access by a third party to an external cloud service the group uses, and that some of the files the third party downloaded contained personal information. It detected anomalies on October 28 and blocked the access, and on October 29 confirmed that personal information was included. The personal information confirmed as leaked by November 1 falls into seven groups: names and email addresses of about 90,000 group employees and employees of partner companies; email addresses of 7,323 people registered as of the end of 2023 with the corporate experience programme Mar de Shine; applicant My Page registration data and so on (name, email address, phone number, etc.) of 7,173 applicants to the business-track open selection of Suntory Holdings' 2026 new-graduate recruitment; names and phone numbers of 1,097 people stored on two company mobile phones of Suntory Beverage Solution; names, email addresses and phone numbers of 324 employees and partner-company employees of Monte Bussan; names and delivery location information of 96 Izutsu Maisen delivery customers and delivery staff; and names and job titles of 25 employees of Suntory's business partners. Credit card and other payment data are not included. No misuse had been confirmed at the time of the notice. The company says it is contacting the people affected individually. Our conclusion: do not open links in messages claiming to be Suntory or a group company about selection, job offers, deliveries or business dealings; check through the official site you open yourself or the contact points on the notice page.

2026-11-05

Unauthorized Access to Arara's Email Delivery Service Arara Message (About 81.3 Million Email Addresses): Names and Other Member Data Too. What Newsletter Recipients and Client Companies Should Do

On November 6, 2026, Arara Inc. (a subsidiary of PayCloud Holdings) said in a third report that, counting 3,249,492 email addresses taken from a separate cloud environment (environment B), the unauthorized access to its email delivery service Arara Message took 81,329,467 email addresses with duplicates between categories removed (about 81.3 million; a count of email addresses, not people). Environment B was not a new intrusion: it happened during the same series of access from October 28 to 31, and only email addresses were taken. The breakdown: 78,102,937 via the service in environment A (31,346,375 email-only, 46,756,562 with attributes), 2,842,400 in the shared environment (corrected from 3,386,187 in the second report) and 3,249,492 in environment B, with overlaps subtracted. The affected client companies number up to about 380 (the second report's estimate; the third report explains it includes the 61 shared-environment companies and those in environment B). October 27 was access that looks like reconnaissance; the unauthorized login and taking began on October 28 and continued until the October 31 stop. The service holds no credit card numbers (second and third reports). From October 28 to 30, the service was misused to send up to about 7.13 million fake emails posing as credit card companies, from the sender news@arara.com. The service has been fully stopped since October 31 with no restart date. Client organizations including Workman, Asoview, Kakaku.com, Matsui Securities, MOS Food Services, Bic Camera, Kojima and Sofmap, TKC, IIJmio, Zaif, the Bank of the Ryukyus, KEYUCA (Kawajun) and five Kewpie Group companies have published their own notices. On November 13, Osaka City disclosed 1,078,713 email addresses of users of its administrative online system (a count of addresses, not people; via the email delivery service used by the system's provider, TKC) and, separately, 33,868 users and 14,669 participating shops of its premium voucher program, and JR Kyushu Shoji disclosed about 50,000 email addresses. Kyoto City also said on November 6 that data may have leaked through ARTPASS at the Kyoto City KYOCERA Museum of Art, and that part of the user data held by Asoview! (Nijo Castle) was found to have leaked. From November 16, Itami City (mail magazine 12,813, online applications 14,570), Sakai City (64,073) and Okayama Prefecture (1,045) also published notices (all counts are email addresses). This site's conclusion: do not open fake emails from news@arara.com or in a card company's name, and contact your card issuer if you entered card details; check the table in this article for the services you use; and client companies should note the November 9, 6 p.m. deadline to apply for joint reporting to the Personal Information Protection Commission.

2026-11-05

Asoview! Member Data Breach (15,821,184 Records): Names, Phone Numbers and Ticket Purchase Details Leaked via an Email-Delivery Vendor, and What Members Should Do

Asoview Inc. announced on November 3, 2026 that part of the member data of its leisure booking service Asoview! leaked after a third party gained unauthorized access to the service of the vendor it used to send email. The company says the cause lies in the vendor's service, not in its own systems. The figure is 15,821,184 records. The items are email address, member ID and number, name, gender, date of birth, registration date, last login date, phone number, postal code, area of residence, ticket purchase date and time, ticket type, quantity, facility used, date of use, number of participants, whether the booking was cancelled, and others. Passwords and credit card information were not entrusted to the vendor and are not included, the company says. Which members the leaked email addresses belong to has not been identified; the vendor is investigating. The vendor reported to the company on November 2, and the same day the company stopped all email sent through that service and invalidated its credentials. No harm from misuse had been confirmed at the time of the notice. Affected members are to be contacted individually. Our conclusion: do not open links in messages claiming to be Asoview! about refunds, cancellations, prize wins or identity checks, and check the booking in the official app or site that you open yourself.

2026-11-05

Seven-Eleven Japan 7NOW Customer Data Leak (164,180 Name-Only Records and More): What a Delivery Contractor Breach Exposed and What Users Should Do

Seven-Eleven Japan announced on November 3, 2026 that a service run by a contractor handling part of the deliveries for its 7NOW delivery service was accessed without authorization by a third party, and that part of the 7NOW orderer (delivery recipient) data was taken. According to the company, the contractor's investigation found the access on November 1 and found on November 3 that 7NOW data was also taken. The confirmed items are: name (katakana) only, 164,180 records; name (katakana) and address, 4,762 records; name (katakana), address, phone number and postal code, 209 records. For some records the order date, store name and store address, and product name were also taken. The company says no credit card information and no IDs or passwords were leaked. It says the contractor's investigation found no leak or alteration of its own credentials or integration settings, and 7NOW is operating normally. Affected customers are being contacted in turn by SMS to their registered phone number. The Personal Information Protection Commission has been notified. Our conclusion: do not open links in calls, texts or emails that seem to know your 7NOW order. Within the scope of the notice, no password change is requested.

2026-11-04

istyle @cosme Breach (Data of About 3 Million Members Leaked): What Members Should Do About Leaked Names, Addresses, Phone Numbers and Skin Type

istyle Inc. announced on November 2, 2026 that it confirmed unauthorized access to @cosme by a third party on October 28, and that part of the member information registered under the @cosme common ID had leaked. About 3 million people are affected, including people who have since left @cosme but were members at the time of the access. The leaked items are the user ID (not used for login), nickname, name (kanji and kana), postal code, address, phone number, email address, gender, date of birth, skin type and hair type. The company says that, as of now, login passwords and credit card information are not included. When the access happened and how are not disclosed, and a third-party security firm is investigating. The company has reported to Japan's Personal Information Protection Commission and plans to finish individually notifying affected people by email from the cosme.net domain on November 6. It says no misuse or secondary damage has been confirmed as far as it knows. This site's takeaway: if you are or were an @cosme member, do not open links in emails, texts or calls that do not come from cosme.net, and verify even messages that get your name, address and skin type right through the official app or a site you open yourself. The company says passwords are not included as of now, but change a reused one to be safe.

2026-11-04

Nojima Online and Used-Phone Buyback Site Unauthorized Access (About 7 Million Records): Names, Addresses, Phone Numbers and Encrypted Passwords, and What Members Should Do

Nojima Corporation announced on November 2, 2026 that the Nojima Online member management system was accessed without authorization and that member data of Nojima Online and its used-phone buyback site leaked. According to the company, it detected and confirmed the access on November 1 and confirmed the same day that personal data had leaked outside. The scale is about 7 million records (members who have withdrawn are not included). The items are name (kanji and kana), date of birth, gender, postal code, address, phone number, login ID, encrypted password and email address. The company says it does not hold payment information and holds no credit card information on the two sites. The cause, the period of intrusion and whether any misuse or secondary harm has occurred are under investigation, and both sites were suspended as of the November 2 announcement (no reopening notice seen as of November 4). The company warns that the data could be abused for impersonation emails and phishing, but its notice does not ask members to change passwords. Our conclusion: do not open links in messages that claim to come from Nojima. If you reuse your Nojima password elsewhere, change it on those other services.

2026-11-04

Prestige International Road Service System Breach (Up to About 5.5 Million Records, Including Duplicates; JA Kyosai Separately Expects Up to About 2.85 Million People, a Provisional Count of Total Persons): Names, Vehicle Data, Some Bank Account Data and 3 Card Numbers, and What Insurance, Lease and JA Kyosai Customers Should Do

Prestige International Co., Ltd. announced on November 2, 2026 that the system of its group company Prestige Core Solutions, which handles road service reception and dispatch for client companies, was accessed without authorisation and customers' personal data was taken out. The count is up to about 5.5 million records, duplicates included; the number of unique people is still being checked. The items are names, addresses, phone numbers, email addresses, vehicle information (registration and chassis numbers and similar), accident and breakdown reception information, and, for part of the records, bank account information. No credit card leak was confirmed in the November 2 notice, but in a second report on November 6 the company confirmed that 3 credit card numbers were among the data taken (recorded in part of the system's reception records). It has contacted the issuers of those cards and will contact the customers after talks with the issuers. The company detected the access on October 29 and invalidated the misused credentials, but the access continued, so it stopped the system on October 30. Road service continues through an alternative operation. Sony Sonpo, AXA Direct Insurance, ENEOS (car lease), KDDI (au Bicycle Support), Nissan Financial Services, Mitsui Direct General Insurance and JA Kyosai have each published their own notices about their customers. In its second report of November 12, JA Kyosai (the national federation of JA mutual insurance) said the leaked data for contract-holder and requester names in the towing and road service of its auto mutual insurance is expected to be up to about 2.85 million people (a provisional count of total persons, with duplicates, expected to fall after review): names, addresses, phone numbers, vehicle information, reception information and, for some users, bank account information. It confirmed that credit card information of its own users was not taken. Our conclusion: people who used road service through an insurance, JA Kyosai auto mutual insurance or lease contract, or au Bicycle Support, should open their own provider's official notice themselves, and should not click links in calls, texts or emails that talk about their vehicle or an accident. If you used a credit card, check your statement and contact the card company about any charge you do not recognise.

2026-11-03

Good Smile Company Official Shop Breach (Full Card Data May Have Leaked for 2,800 People, Partial Card Data on 402,466 Cards, Up to 202 Orders Possibly Viewed): What Each Group Should Do

Good Smile Company Co., Ltd. announced on October 23, 2026 that its official shop had been accessed by a third party, and by its fourth report on October 30 it had sorted those affected into three groups. Group B (2,800 people) may have had the cardholder name, card number, expiry date and security code entered on the payment page captured by a malicious program that was in place from 13:55 on October 21 to 7:00 on October 23. Group A (anyone who ever registered a card; 402,466 cards, number of people still being checked) is limited to the last four digits of the card number and the expiry date, and the company considers misuse of that alone extremely unlikely. Group C (5,356 people) concerns unshipped order data (name, address, phone number, email, order contents and similar); at most 202 orders may actually have been viewed. The company says the cause is not the recently reported PHP vulnerability. This site's conclusion: Group B should contact the card issuer and ask about changing the card number. People who get no email but ever registered a card on the shop are still in scope and should check statements. Do not open links in unexpected messages claiming to come from the company.

2026-11-03

PingCAP (TiDB Cloud) Unauthorized Access and Data Leak (Up to About 50,000 Records in Japan): What TiDB Cloud Organization Admins Should Do About Account Data, SQL Editor History and Support Tickets

PingCAP says that between September 9 and October 7, 2026 (US time), an unauthorized party used stolen credentials to enter internal systems and copy data, and that up to about 50,000 personal records in Japan were found to have leaked (Japanese notice). The categories the company has confirmed as affected (varying by customer) are TiDB Cloud account data (user names, email addresses, organization and project associations, SQL editor execution history and errors, and inquiry information, meaning support tickets), business and billing information (names, emails, company names, phone numbers, orders, payment terms, billing settings) and the encrypted Public Key part of TiDB Cloud API keys. The company says it has not confirmed credit card leakage or unauthorized access to TiDB Cloud itself, and that Private Keys were not exposed. The unit the count measures (people or records) is not stated. The company's English notice also says source code was obtained. This site's conclusion: TiDB Cloud organization admins should rotate API keys, review access logs, members and roles, and change any credentials that may have been pasted into the SQL editor or a support ticket.

2026-11-02

MyBRANDS Job Site Unauthorized Access and Possible Personal Data Leak (Up to About 135,000 Accounts): What Job Seekers and Employer Contacts With Names, Contact Details and Work History Should Do

iDA Co., Ltd. (Japan) announced on October 30, 2026 that unauthorized access by a third party to the server environment of its job site MyBRANDS may have leaked outside the information of registered job seekers and employer contacts. It says a cloud access key used by a contractor was misused by a third party on October 21 to 22, and that on October 26 it learned there were records of data being sent outside from a copy of the database. It could not confirm what the sent data contained, so it is notifying on the basis that all information it held is covered. The scope is up to about 135,000 accounts as of October 30, including people who have left the service. The information is name, email address, phone number, profile (such as work history) and login password (stored as a transformed value), and varies by registration. Credit card and bank account information was not held and is not included. Name, email address, phone number and address were stored encrypted, but the key to decrypt them may also have been taken, it says. No misuse (secondary damage) has been confirmed so far. This site's conclusion: change passwords on any other service that shares your MyBRANDS password (employer contacts, also internal systems), and check messages claiming to be a recruiter or scout through an official channel, not through their links or numbers.

2026-11-02

Saga University ransomware attack (personal data of students, staff and former students may have leaked, about 80,000 people, plus patient information): what people whose names, addresses and passwords are listed should do

Saga University, a national university in Japan, announced on October 30, 2026 that, following the ransomware attack it disclosed on September 28 on its administrative information systems, it had confirmed that it cannot rule out that personal information it holds, including patient information, leaked outside the university. According to the university, at 8:42 a.m. on September 24 it confirmed damage thought to be caused by ransomware on a NAS (network-attached storage) used by administrative departments. It then asked an external specialist company to investigate the intrusion route and the scope. The affected group is about 80,000 people: students, staff, former students, former staff and related persons. The items are name, date of birth, sex, address, phone number, email address and password. The number of patients is still under investigation, and the patient information is described as special-care-required personal information (clinical department, disease or injury name, date of visit and so on). The notice does not say in what form the passwords were stored (whether encrypted or hashed). The university warns that suspicious emails, text messages and phone calls pretending to come from the university or related organisations may arrive. This site's take: check any message claiming to be from the university or its hospital on an official website you open yourself, even if the details in it are correct, and change any password you reused from your university account.

2026-11-01

Club Tourism Unauthorized Access and Possible Personal Data Leak (About 4.32 Million Records): What Members With Names, Addresses, Phone Numbers and Emergency Contacts Should Do

Club Tourism Co., Ltd. (Japan) announced on October 31, 2026 that it detected unauthorized access from outside at 5:45 on October 30 and that information of internet members registered in its internet reservation system may have been leaked outside (First Report). The items are name (kanji and kana), nationality, sex, date of birth and age, address, phone number, email address, member ID and emergency contact. The count is about 4.32 million records. Login passwords, passport information, credit card information and bank account numbers are not included, it says. Information of people who have never registered as internet members is not affected, and no specific secondary damage attributed to this incident has been confirmed. The company says it isolated the server, identified and fixed the intrusion route, has stopped its website to prevent further damage and investigate, consulted the police, and reported to the Personal Information Protection Commission and its supervising authority. This site's conclusion: if someone claiming to be the company calls, emails or texts you, do not use the links or numbers in the message; check on the official site, at a branch, or through the contact in the notice.

2026-11-01

World subsidiary Tin Pan Alley (RAGTAG operator, per press) breach (about 1.2 million records in total): names, addresses and phone numbers may have leaked — what members should do

On October 30, 2026, World Co., Ltd. announced that a business server of its consolidated subsidiary Tin Pan Alley Co., Ltd. had been accessed without authorization by a third party, and that part of the member information stored on it may have leaked. The member information that may have leaked totals about 1.2 million records (an aggregate count, not a number of people). The items are name, address, phone number, date of birth, gender and email address. The company says no leak of credit card or other payment data, or of face data, has been confirmed. The access happened around 14:51 on October 17, was detected around 12:08 on October 28, and the route was blocked by 21:36 the same day. Which members and how many are affected is still being confirmed, and individual emails to members will go out once ready. Press reports say Tin Pan Alley operates the used-clothing brand RAGTAG and others, but the notice itself names no service or brand. This site's take: assume your name, address, phone number and email are together in someone's hands, do not open links in messages, check in an official site you open yourself, and never give out passwords or card numbers.

2026-10-31

GETTIIS Member Data Breach (317,971 member IDs): What Leaked and What Members Should Do

On October 19, 2026, Linkstation Inc. (Japan) announced that GETTIIS member information had leaked after unauthorized access, and on October 20 it published a second report with counts per item. According to the company, between about 0:00 and 7:00 on October 18 a third party exploited a vulnerability in the program of Gettii-Lite, a performance-registration service for organizers, and obtained GETTIIS member data. The counts are per item, not a total number of people: member IDs 317,971; hashed passwords 311,451; email addresses 311,426; names 309,759; phone numbers 309,668; card-related information 29,515 (the first and last four digits, cardholder name and expiry date, encrypted); gender 5,900; dates of birth 5,192; postal codes 489. The company says it does not store full card numbers or security codes, that the leaked data alone cannot be used for card payments, and that passwords were stored as hashes. This site's conclusion: change the GETTIIS password and any other password you reused, and treat messages that use your name and phone number as suspect, because those two items were leaked for about 310,000 records each.

2026-10-31

Matsuya app management system breach (2,377,127 records plus app members): names, phone numbers and delivery addresses leaked — what members should do

On October 30, 2026, Matsuya Foods Holdings Co., Ltd., the Japanese beef-bowl restaurant chain, announced that the management system of the official Matsuya app (Matsuben Net, Mobile Order and Matsuben Delivery) had been accessed without authorization by a third party and that member data had leaked. The company found the intrusion and the leak on October 28. For users of Matsuben Net, Mobile Order and Matsuben Delivery (2,377,127 records), the items are member ID, delivery address, name, phone number and Matsuya points. For Matsuya app members (2,000 records, possibly up to 3,000), the items are member ID, prefecture, name, phone number, date of birth, email address, encrypted password and Matsuya points. The company says it does not hold credit card data. The cause and how the intrusion happened are under investigation, and the app and related services such as its website are suspended. Our conclusion: do not open links in messages claiming to be Matsuya, check only in official places you open yourself, and if you are an app member, stop reusing your Matsuya password elsewhere.

2026-10-31

Ryohin Keikaku (MUJI) app and online store breach (up to about 27.26 million records): about 1.09 million MUJI Card numbers affected, online store reopening postponed — what users should do

After its October 30 first notice, November 4 second notice and the November 6 online store suspension, Ryohin Keikaku Co., Ltd., the Japanese retailer behind MUJI, said in a fourth notice on November 9, 2026 that the online store had been hit by unauthorized logins (credential stuffing) and that information of cash-on-delivery recipients had been accessed, and postponed reopening the store. Email address, date of birth, gender and member ID in up to about 27.26 million records of MUJI app and online store members (withdrawn customers included) may have been accessed from outside, and for about 750,000 of them name, address and phone number too (up from about 520,000 in the second notice). About 270,000 more are unauthorized logins to the online store using IDs (email addresses) and passwords obtained from outside the company, where purchase history and points may also be affected. The delivery name and postal code of people who were the recipient of a cash-on-delivery order from January 2, 2020 to February 10, 2025 are affected in about 440,000 records (the sender's details are not included). For about 1.09 million members of the MUJI Card (issued by Credit Saison, joined by July 2021), the full card number, MUJI Card ID and date of birth are affected; the name on the card, expiry date and security code are not included. The company says it has not confirmed harm from misuse of information that may have been viewed, and began contacting affected customers individually by email or post on November 10. It plans to ask all customers to reset their password when the store reopens. This site's take: if you hold a MUJI Card, check your statement and contact Credit Saison; keep your MUJI password different from other services; and verify any message claiming to be MUJI or a card company through an official channel you open yourself.

2026-10-31

Yakult Honsha website breach (39,505 records): names, addresses, phones, emails and inquiry contents leaked — what affected people should do

Yakult Honsha Co., Ltd. confirmed unauthorized access to its website on October 26, 2026 and suspended the site's functions the same day. In its third report of November 4, it narrowed the "about 40,000" of the October 30 second report to 39,505 records at this point. The breakdown: users of the email inquiry form, 31,781 (name, gender, age band, address, phone number, email address, inquiry contents; April 2015 to October 2026); members of the school lunch site "Tanoshii Kyushoku", 5,698 (name, type of business, workplace, email address, encrypted password and more; September 2021 to October 2026); users of the press inquiry form, 1,613 (February 2011 to October 2026); web entrants to a cosmetics campaign, 354 (name, postal code, address, age, phone number, product bought, reason for buying and more; August 2021 to February 2022; newly found in the third report); and staff who handled inquiries, 59 (names). The company says the website did not hold credit card or bank account data. It opened a dedicated inquiry line (0120-400-507) at 9:00 on November 5 and is contacting affected people by email in sequence. It has reported to Japan's Personal Information Protection Commission and consulted the police, and the website remains suspended. The cause and how the intruder got in have not been disclosed. This site's take: do not open links in messages claiming to be Yakult, and if you are a school lunch site member, change the password on any other service where you used the same one.

2026-10-30

Aena EC App Unauthorized Access (My Page Data of Up to 817,215 People): Names, Addresses and Delivery Details That May Have Been Viewed, and What Members Should Do

Aena Co., Ltd., a Japanese off-price retail chain, announced on October 14, 2026 that member My Page data in its EC app may have been viewed without authorization. According to the company, system log analysis found it at 5:58 on October 13, and up to 817,215 members (full members) may have been affected. LINE members and customers who bought through Amazon, Rakuten and similar sites are not affected. The information that may have been viewed is name, address, phone number, email address, date of birth, gender, occupation, delivery address, name and phone number (including those for third parties), favourite store and mail settings, and the last 4 digits, expiry date and cardholder name of registered credit cards. The company says it does not hold full card numbers or security codes, that no password was viewed or leaked, and that it confirmed no member information was changed, no one was withdrawn and no purchase was completed. The cause is given as mechanical continuous access made through unauthorized access, and the investigation continues. The company blocked access to its EC site, and the EC app, which had been suspended, resumed at noon on Monday, October 19; a password reset screen appears at the first launch after the restart. This site's conclusion: reset your password in the app, change any other service where you reused it, and check messages about deliveries or orders without using their links or numbers.

2026-10-30

Benefit One 'Toku-Kai' Contractor Breach (29,465 People): Names, Birth Dates and Email Addresses Leaked, and What Members Should Do

On October 28, 2026, Benefit One Inc. announced that a system run by one of its outsourcing contractors was accessed without authorization and that personal data of 29,465 members (including some who have already left) of Toku-Kai, a service for Credit Saison Co., Ltd. cardholders, leaked. The access happened intermittently from October 14 to 20; the contractor detected part of it on October 21 and reported it to Benefit One, which suspended the service the same day. The leaked items are name, furigana (reading of the name), date of birth, gender, postal code, email address, customer number, enrollment and withdrawal information, and a management number used for membership-fee payment processing (items vary by member). Separately, some of Benefit One's authentication-related information used to link to the payment system may have leaked; it was changed on October 26, and no fraudulent payment attributable to this incident has been confirmed. Benefit One says card numbers, expiry dates and security codes are not held in the affected system and did not leak. The company says the data did not come from Credit Saison's systems. The cause and the final number are under investigation. This site's take: Benefit One's notice does not ask members to change card numbers, but names, birth dates and email addresses leaked, so do not open links in messages claiming to be from the company or its partners, and verify on an official site you open yourself.

2026-10-30

Hana-cupid Member Data Breach (Up to 4,238,242 Records): User IDs, Encrypted Passwords and Email Addresses Leaked, and What Members Should Do

Hana-cupid Co., Ltd. announced on October 28, 2026 that unauthorized access by a third party to its online florist services, Internet Hana-cupid and Business Hana-cupid, had leaked some member information. According to the company, a third party accessed its management system without authorization between October 14 (Wed) and October 15 (Thu), and the company confirmed the leak of member information on October 19 (Mon) during its investigation. The count is 4,238,242 (customers who may be affected). The leaked items are: user ID (login ID), password (an encrypted form that cannot be used as it is; the FAQ calls it hashed), PC email address and mobile email address. The company says name, gender, date of birth, address, phone number, credit card number, company name, department name and delivery destination information did not leak. Only members who registered an email address on the company's official online shop (i879.com, i879.com/biz/) are covered; orders through external shopping malls, phone orders without an email address, and purchases at Hana-cupid member florists are not. The company says it does not hold credit card information and that there is no need to stop or reissue a card. It has not confirmed any secondary harm, began emailing affected members individually on October 28, and has reported to the Personal Information Protection Commission and the police. The cause is not stated, and the company is investigating with an external specialist organisation. It says it does not plan monetary compensation or refunds. This site's conclusion: if you could be affected, change your password and any other service where you reused the same ID and password. Check anything claiming to be from Hana-cupid or a financial institution by opening the official site yourself, not through its links.

2026-10-30

Unauthorized Access at the Reservation System Vendor of JAL, JTA, ANA, Korean Air and Asiana (About 92,000 JAL/JTA and 37,800 ANA Customers): Booking Numbers, Names and More, and What Travellers Should Do

Japan Airlines (JAL) and Japan Transocean Air (JTA) announced on October 28, 2026 that on October 23 they were told by the vendor of their passenger service system, an overseas company, that unauthorized access to the vendor's systems left traces of some booking information being viewed from outside. The period is August 10, 2023 to September 23, 2026. About 90,000 people had booking number, name, boarding date, route and cabin class involved; about 2,000 people also had email address, phone number, passport number, nationality, mileage number, ticket number, seat number and more viewed. The total is about 92,000 people. On October 30 JAL and JTA updated the notice to say they had contacted those customers at the email address given when booking. All Nippon Airways (ANA) announced on October 30 that there are traces of some booking information of about 37,800 people who booked in the same period being viewed (about 1,700 of them including passport and mileage numbers). In South Korea, Korean Air and Asiana Airlines announced on October 23 that there are signs that some customers' booking numbers leaked from the same company's reservation system; they say it was caused by unauthorized access using login credentials and is estimated to have occurred between August 2023 and September 2026 (neither has published a number). JAL, JTA and ANA say credit card details and passwords were not included. According to press reports, 144,249 passengers of Norwegian and Widerøe (a figure from a letter Norwegian sent to Norway's data protection authority) and about 350,000 SAS passengers (a figure SAS reportedly filed with Swedish authorities) are also part of the same vendor incident; these are press reports, not airline announcements. In a statement the vendor says it implemented measures to fix a vulnerability affecting a booking-display environment and enhanced monitoring and detection (its investigations continue), and has no evidence payment or financial data was accessed. This site's conclusion: even if a message claiming to be from an airline gets your booking number, name and flight right, do not use its links or numbers; check in the official app or site. If your passport or mileage number may be involved, change your mileage account password and review its redemption history.

2026-10-30

Sony Life Unauthorized Access Leaks Policy Data (About 2.9 Million Sony Life Records, 385,000 Medicare Life Records): Names, Addresses, Policy Numbers and More, and What Policyholders Should Do

Sony Life Insurance Co., Ltd. announced on November 9, 2026, in a second report, that it had newly confirmed information leaks stemming from the unauthorized access to its systems: personal information on its own insurance policies (policy number, name, address, phone number and more), about 2.9 million records including records of contracts already ended; the email addresses and agent numbers of sales agents, about 780 records; and the email addresses and employee numbers of its own employees, about 12,500 records. Sensitive personal information such as health status and medical history, My Number, credit card information, account information and policyholders' email addresses are stated not to be included. This follows the first report of October 28 (information on Medicare Life policyholders and insured persons that Sony Life handled as an agent, about 385,000 records), so Sony Life's own policyholders are now affected too. The access came to light on October 27. As of November 9 no misuse of customer information had been confirmed, but the company warns of emails, texts and calls impersonating it. The cause has not been published. Our conclusion: assume you may be affected if you hold or held a Sony Life policy, or took out a Medicare Life policy through Sony Life, and check any message through the contact points on the official sites, not through links or numbers in the message.

2026-10-30

White Essence Unauthorized Access and Personal Data Leak (About 1.05 Million Accounts): Names, Addresses, Phone Numbers and Encrypted Passwords, and What Users Should Do

White Essence Co., Ltd. announced on August 12, 2026 that it had suspended its systems after unauthorized access to its booking site and core systems, and on October 5 published its findings in a notice titled 'Apology and Notice Regarding Leak of Personal Information Due to Unauthorized Access'. According to the company, it confirmed unauthorized access from outside on August 5, suspended the systems on August 12, and the investigation later found that personal information had been taken outside. Of the information registered as of August 5, 2026, the number of people affected is about 1.05 million accounts (a total that includes customers, franchise clinic personnel and head office employees). The leaked items, in whole or in part, are name, address, phone number, email address, date of birth, gender, workplace, login ID and password (in encrypted form), information about use of and responses to services, and the company's management number. The company says it does not hold financial institution account information, and that it has not confirmed that customers' images leaked. The cause, it says, was the exploitation of a vulnerability in the program of its booking site, used as a starting point to access its core systems without authorization; the company says it has finished dealing with that vulnerability. As of October 5 no secondary harm had been confirmed, but the company says suspicious emails, calls or mail posing as the company or other businesses may arrive. Our conclusion: if you use the same login ID and password on other services, change them there. Treat any message claiming to be from the company or a dental clinic as unverified even if your name, address and birth date are correct, and check through an official channel you look up yourself.

2026-10-29

Beauty Garage and Eyelash Garage Unauthorized Access (775,725 Records): Salon Names, Phone Numbers, Emails and Password Hashes Leaked, and How to Guard Against Impersonation

Beauty Garage Co., Ltd. announced on October 15 that its e-commerce site servers, and those of Eyelash Garage, were accessed without authorization from October 10 to 12 and that some customer information leaked. It detected the incident on October 13, identified the route and blocked it the same day. According to the company, the scope is 775,725 customer records held in the Beauty Garage and Eyelash Garage e-commerce systems as of 23:55 on October 10, 2026 (no per-brand breakdown is given); Eyelash Garage's own notice gives 49,191 (how this relates to 775,725 is not stated). The main items confirmed as leaked are company name, salon name, customer name, business type, salon URL, phone number, email address, password hash values, and hash values of the password-reset question and answer. Leaks of address and shipping information, purchase history and payment information including credit cards have not been confirmed so far. The company says it has not confirmed that the data was published or misused. Second notices from both companies on October 20 say the e-commerce sites are operating normally and that the matter has been reported to the Personal Information Protection Commission. The cause has not been disclosed. This site's conclusion: a message claiming to be from either company or a business partner is not genuine just because it gets your salon name or your name right. Verify any request to change a bank transfer destination or make an extra payment through an official contact.

2026-10-29

So-net Member Database Unauthorized Access (2.14M So-net Records, 443K plala S-Course Records): Names, Phone Numbers and Birth Dates Leaked, and What Users Should Do

Sony Network Communications Inc. announced on October 27, 2026 that it had confirmed an information leak from unauthorized access to the member database of its internet service So-net. According to the company, the database was accessed from outside on October 19, the company confirmed this on October 23 and stopped the affected server, and on October 24 it established which items and how many records had leaked. The leaked information is: So-net member information, 2,141,986 records (1,869,771 current members and 272,215 former members who left in or after March 2026), and plala (S-Course) member information, 443,495 records (422,365 current and 21,130 former members who left in or after March 2026). Both contain name, phone number, email address, user ID, date of birth, gender and internet connection ID. The company says no password leaked in the member information. For four mail services (Mail Service G, A-Box, Sonnet VAIO Mail and PostPet Mail Account Service), mail passwords also leaked, for 54,401 addresses in total, and the company reset them on October 27. Bank account information for 16 records and password-reset notice information for 7 records also leaked, and the company says it will contact those people individually. Credit card information is not included, and the company has not confirmed a leak from other services, including NURO. The cause is given as unauthorized access by a third party (under investigation); the route of the intrusion has not been announced. This site's conclusion: if you used any of the four mail services, reset your mail password and change any other service where you reused it. Everyone should check a message claiming to be from So-net through an official site or the special phone line, not through its links or numbers, even if it gets your name and birth date right.

2026-10-29

Toypo App Unauthorized Access (697,209 Users Affected, per Toypo): Phone Numbers, Names and Addresses Leaked, and What Store App Users Should Do

Toypo Inc. confirmed unauthorized access by a third party to its customer-management app, the Toypo app, on October 4, 2026, and said in a notice dated October 14 that 697,209 users are covered and that their information may have leaked. A second Toypo notice page, which has no date and no number of people, says the information leaked. Since October 13 the company has been contacting those covered one by one, including by in-app push notification. According to the company, part of its system had an access-control flaw that let an authenticated user obtain other users' information they were not entitled to see, and its logs show a third party used it to obtain user information. The flaw has been fixed. The information that may have leaked is the phone number and user ID or similar identifiers and, where registered, name, name in kana, email address, date of birth, gender and address. Passwords and other login credentials, credit card numbers and other payment data, points, store-visit history and purchase or usage history are not included, it says, and users do not need to change passwords or take other action in the app. No specific secondary harm has been confirmed. It has reported to the Personal Information Protection Commission. A third-party security assessment is being arranged. In notices by stores that use the app, JR Kyushu Food Service says about 26,900 of about 61,500 registered members are covered, and Mannoya says 12 of 212 members of its Kineya Mannoya official app. Toypo's contact is 0120-546-030 (weekdays 9:00 to 18:00 Japan time; the call center takes calls until 18:00 on October 30, then the in-app contact). This site's conclusion: a message that gets your phone number and name right is not necessarily genuine. Do not use its links or numbers; check through the in-app contact or the contact listed in the notice.

2026-10-28

Ichiban Kuji ONLINE (387,895 records) and Ichiban Kuji Club (25,632 records) delivery data may have leaked (unauthorized access at Bandai Logipal): names, addresses and phone numbers, and what members should do

In their second report on November 16, 2026, BANDAI NAMCO Holdings Inc., BANDAI SPIRITS CO., LTD. and Bandai Logipal Co., Ltd. gave counts of the delivery information that may have leaked: 387,895 records for Ichiban Kuji ONLINE (people with product shipments between January 22, 2025 and October 22, 2026) and 25,632 records for Ichiban Kuji Club campaigns (some people with prize shipments between January 1, 2019 and October 22, 2026). The items are name, address and phone number in both. Some customers may be counted in both, so this site does not add the two counts. The three companies had announced on October 26, 2026 (first report) that a system managed by Bandai Logipal, the logistics subsidiary of BANDAI NAMCO Holdings, had been accessed without authorization by a third party, and that this was discovered on October 21. According to the three companies, the personal information that may have leaked is the delivery information (name, address and phone number) for Ichiban Kuji ONLINE, a service for which BANDAI SPIRITS outsources product delivery to Bandai Logipal. The second report says the investigation found that some information on delivery for Ichiban Kuji ONLINE orders and Ichiban Kuji Club campaigns may have leaked. Credit card details were not included, and no misuse has been confirmed so far. The companies say they will contact the customers concerned by email or post in turn from November 17. On October 21 the company found traces suggesting unauthorized access on a server in its logistics system and shut the server down, and on the same day confirmed that operations had been carried out through misuse of a Bandai Logipal account. It stopped the logistics system in question on October 24 and reported to the police and Japan's Personal Information Protection Commission on October 26. The shipping system was suspended from October 24 to 28 and has been restarted in turn from October 28, mainly with the systems confirmed safe. How the unauthorized access happened has not been published. The companies warn that suspicious phone calls and postal mail related to the incident may arrive. This site's conclusion: anyone who has had items delivered through Ichiban Kuji ONLINE should not respond to unexpected calls or mail claiming to be from Ichiban Kuji or Bandai, and should use the inquiry form on the official website, opened themselves, to check anything.

2026-10-28

Joshin (formerly Joshin Denki) Unauthorized Access (Up to About 6 Million Records): Members' Names, Addresses and Phone Numbers May Have Leaked, and What Users Should Do

Joshin Corporation, which changed its name from Joshin Denki Co., Ltd. on April 1, 2026, announced on October 17 that it had recognized unauthorized access on October 16 and that, after taking steps such as restricting access from outside, some services could not be provided (filed with the Tokyo Stock Exchange on October 19). Its second notice on October 26 says it detected an anomaly on its network on October 16 and took steps such as disconnecting servers showing signs of unauthorized access from the network. According to the second notice, the information that may have leaked is: up to about 6 million records on the member database server (name, address, phone number, member number); up to about 230,000 records of the Joshin subscription service (member number, phone number + handwritten signature (binary data), login ID and initial password, billing history, contract number and device ID, activation code); and up to about 800 records of the renovation photo upload system (2 driver's license images, 1 My Number card, 5 bank account numbers, and photos of renovation work in progress). The company says these are total counts of records that may have leaked, not confirmed leak counts. It does not hold payment data, including credit card information. It has consulted and reported to the Personal Information Protection Commission and the police. The cause, the route of the intrusion and when suspended services will resume have not been announced. This site's conclusion: a message claiming to be from Joshin is not genuine just because it gets your name, address or member number right. Do not use its links or phone numbers; check through the contact listed in the notice or an official site you open yourself.

2026-10-28

Qzoo survey site breach (about 400,000 records): member data including bank account details may have leaked, and what members should do

On October 21, 2026, Monitas Inc. announced that its survey site Qzoo had been accessed by a third party without authorization and that members' (panelists') personal data may have leaked. According to the timeline, unauthorized access began at 8:30 on October 17; at 12:22 the database was viewed and updated through SQL injection; at 18:44 the access was detected and blocked; at 19:02 the service was put into emergency maintenance; and on October 20 a preliminary report was made to Japan's Personal Information Protection Commission. The scope is about 400,000 records (all records held in the Qzoo system as of October 17). The database that may have been affected stores basic information (name, date of birth, address, phone number, email address, etc.), member authentication information (member ID, password, etc.), financial information (account number, branch name, account holder name, etc.) and survey answers (annual income, occupation, etc.). The items are still under investigation. The company does not hold credit card data or My Number (Japan's national ID number). It says the intruder exploited a vulnerability in its system. No unauthorized access to its other systems has been found. This site's take: change any password you share with Qzoo today, do not open links in messages claiming to be Qzoo or a bank, and never give your PIN or login details to anyone. Check your bank account activity as well.

2026-10-27

M3 "MR-kun" breach (25,775 m3.com members and others, 2,260 pharma staff): what leaked, and what doctors and pharmaceutical staff should do

On October 15 and October 23, 2026 (second notice), M3, Inc. announced that a third party had gained unauthorized access to the system of MR-kun, a service it runs for pharmaceutical companies, and that personal information had leaked. According to the company, it confirmed the unauthorized access on October 14 and cut off the route it had identified the same day. The second notice confirms leaks for 25,775 m3.com members and others (name, workplace, email address for some, some information about their use of M3 services, and information that client pharmaceutical companies had registered in the service (assignment relationships and similar); email addresses for 6 of them) and for 2,260 pharmaceutical company staff (name, workplace, email address for some and other items; email addresses for 264 of them). It also includes some doctors who are not m3.com members, whose details pharmaceutical companies had entrusted to M3. Login passwords and m3 points were not included, and M3 does not hold credit card numbers. The cause has not been published. The company says it has found no public posting or misuse. Since October 22 it has been contacting affected members individually at their registered email addresses. Our conclusion: doctors and others who use m3.com should not open links in messages claiming to be from M3 or a pharmaceutical representative, and should not give out passwords or bank details.

2026-10-27

Pizza Hut Japan online ordering breach: email addresses, phone numbers and login session tokens leaked, and what customers should do

On October 23, 2026, Pizza Hut Japan Ltd., which runs Pizza Hut in Japan, announced that a third party had gained unauthorized access to a system linked to Pizza Hut's online ordering service for Japan and that part of its customers' information had leaked. According to the company, on October 19 it confirmed that a third party had gained unauthorized access to a payment API linked to the online ordering service (a mechanism that exchanges payment-related information between systems) and obtained some information from a database containing customer information. The information confirmed to have leaked is customer IDs, email addresses, phone numbers, records relating to deleted customer information, session login tokens and transaction records. Credit card details were not included. The number of people affected has not been published. The company says the cause and the full scope are still under investigation. The company blocked the attacking IP addresses, addressed the vulnerability and filed a preliminary report with Japan's Personal Information Protection Commission. No secondary harm has been confirmed, but it warns of suspicious emails, texts and calls impersonating the company or Pizza Hut. This site's conclusion: anyone who has used Pizza Hut Japan's online ordering should not open links in messages claiming to be from Pizza Hut, and should check their order history in the official app or on the official website opened themselves.

2026-10-27

Rakuten Travel Unauthorized Access (Up to About 2.6 Million Records): Names, Contact Details and Partial Card Data from Overseas Hotel Bookings, and What Users Should Do

On October 26, 2026, Rakuten Group, Inc. announced that it had confirmed unauthorized access by an outside third party to some pages of Rakuten Travel's overseas hotel booking site, managed and operated by its subsidiary Rakuten Travel Xchange, and to the multilingual booking site that Rakuten Group operates. On the overseas hotel booking pages (incident 1), an anomaly was detected on September 10 and the system fix was completed on September 16. The information that was subject to the unauthorized access covers names, email addresses, phone numbers and internal ID numbers for up to about 2.6 million records of logged-in customers, and, for up to about 40,000 records of customers who booked, names, contact details, country of residence, booking details and companions' names; payment information (card issuer identification number and last four digits, cardholder name, expiry date and card brand) for up to about 36,000 of those. Full card numbers, security codes, passwords, ID documents and addresses are not included (per the note on the booker item). On the multilingual booking site (incident 2), detected on October 20 and fixed on October 21, email addresses and internal IDs for up to about 860,000 records of logged-in customers, and account names and email addresses for up to about 40,000 records of accommodation staff entered in the admin screen, were affected. The cause, the period covered and any compensation have not been announced. This site's conclusion: a message asking you to re-enter your card number or pay is not genuine just because it gets your booking or your card's last four digits right. Do not use links in emails or texts; check your booking in the Rakuten Travel app or a bookmarked official site.

2026-10-26

Fujicco campaign entry data possibly leaked (about 15,500 entries): names, addresses, family details, and what entrants should do

On October 22, 2026, Fujicco Co., Ltd., a Japanese food maker known for its Caspian Sea Yogurt and kelp products, announced that a server of the company it contracts to handle campaign entries had been accessed without authorization by an outside party, and that entrants' personal data may have leaked. The access was found on October 21 and the server was promptly shut down. The data covers personal information entered in the non-member entry forms of two campaigns run since May 2026: the Caspian Sea Yogurt series 'Motto! Toro-mocchi Campaign Part 2' and the 'Fujicco Thanksgiving Festival Campaign'. There are about 15,500 entries in total, including repeated entries by the same person. The items are name, age, gender, occupation, marital status, family composition, phone number, email address, address and survey answers. Driver's licences, credit cards and bank account numbers are not included. Entries made as a Fujicoin member, by postcard or on X are not affected. No publication or misuse has been confirmed, but the company is treating the data as obtained by a third party. This site's conclusion: people who entered through the affected forms should not pay shipping or handling fees, resubmit receipts or re-enter personal details when asked, and should check with the campaign office on the number in the official notice.

2026-10-26

Green Monster's FX Navi app possible data leak (about 6.19 million records): email addresses and survey answers among the items, and what users should do

On October 23, 2026, Green Monster Inc. (Tokyo Stock Exchange Growth, 157A), announced that user information from its FX demo-trading app FX Navi (FXなび) may have been obtained by an outside party (first report). On October 17 it found unauthorized access to the app by an outside party and began investigating. In that investigation it found that, from around 20:26 on April 27 to around 14:26 on April 30, an outside party using a different IP address may have continuously obtained user information from the app. It says no leak from the October 17 access itself has been confirmed. About 6.19 million records may have been obtained, including data that is not personal information. The items are email address (66,003), nickname, gender, age group, occupation category, X (formerly Twitter) ID (6,434), self-introduction text, icon image URL, answers to the first-launch survey (4,809,631), device ID, login credentials, account transfer code (5,120), push notification identifier, advertising ID, source IP address and usage data such as trading results. Name, address, phone number, date of birth, credit card, bank account and My Number (Japan's national ID number) are not items users can register. The company says the cause was a function of the app's API; it fixed the API function and the login credentials and invalidated all login credentials issued before the fix. No secondary harm has been confirmed. This site's conclusion: FX Navi users should not open links or attachments in emails or X messages claiming to be from the company or related firms, and should treat every investment solicitation as fake.

2026-10-26

Lindt Japan online shop and app member data breach (3,147,469 records): names, addresses, phone numbers, birth dates and hashed passwords leaked, and what members should do

On October 23, 2026, Lindt & Sprüngli Japan, the Japanese arm of the Swiss chocolate maker, announced that the system of the outside company that provides its online shop platform and manages its member data had been accessed without authorization, and that 3,147,469 member records from its online shop and the Lindt official app had leaked. According to the contractor's report, a vulnerability in software used on the contractor's server was exploited between 23:02 on October 17 and 0:16 on October 18 (Japan time). The leaked items are member ID, name, email address, postal address, phone number, date of birth, gender, newsletter settings, registered store, login password (stored hashed), and other member data such as name reading, registration date and last login. Payment data such as credit cards was not included. As of 11:00 on October 23, no misuse had been confirmed. The online shop has been suspended since 16:00 on October 21, and members will be asked to change their passwords when it reopens. Affected members are being emailed from October 26. This site's conclusion: members should not follow instructions in emails, texts, calls or letters claiming to be from Lindt, and should change the password now on any other service where they used the same one.

2026-10-26

Piccoma newsletter email addresses leaked (1,002,404 records): only email addresses exposed, and what users should do

On October 24, 2026, Kakao piccoma Corp., which runs the Japanese manga app Piccoma, announced that blastmail, the email delivery system of RAKUS Lite Cloud Corporation that it used to send its newsletter, had been accessed without authorization by a third party, and that 1,002,404 customer email addresses that were recipients of one newsletter send had leaked. Piccoma learned of it from the delivery service's report on October 24. Only email addresses registered to receive the newsletter leaked; the company says it confirmed that customer management numbers and last-purchase dates were not included. Passwords were never given to blastmail and cannot have leaked, and Piccoma does not hold names or credit card details. The Piccoma app, website and the company's own systems were not accessed, and accounts, passwords and purchase data were not affected. No leak has been confirmed for the Piccoma Novels newsletter so far. The company stopped its newsletter, changed settings so that email sent from blastmail is not treated as genuine Piccoma email, and reported to Japan's Personal Information Protection Commission. It says it will contact affected customers individually. This site's conclusion: people who received the Piccoma newsletter should not open links in emails or texts claiming to be from Piccoma or publishers, should check in the app, and should never enter passwords or card numbers from an email.

2026-10-26

Value Card prepaid platform breach (1.42 million records, 1.13 million MOS Card records): card numbers, PINs and balances leaked, and what cardholders should do

On October 23, 2026, PayCloud Holdings, a company listed on the Tokyo Stock Exchange Growth market, announced that the servers of Value Card, an in-house electronic money (store prepaid card) issuing service that its subsidiary Value Design Inc. provides to card issuers, were accessed without authorization by a third party, and that 1,424,748 records of ID numbers, PINs and balance information leaked (569,224 issued IDs and 855,524 unissued IDs, meaning IDs not yet bought by a user). The access was confirmed on October 19, and the cause was a third party exploiting a web server vulnerability in part of the subsidiary's system environment. No personal information was involved; the risk of misuse of issued IDs has been dealt with, and there has been no actual damage from misuse. The same day, MOS Food Services, Inc., which runs the MOS Burger chain and its MOS Card prepaid card, announced that unauthorized access to the system of Value Design, which it contracts to operate and maintain the MOS Card servers, leaked 1,133,070 MOS Card records (16-digit card number, 6-digit PIN and balance; about 570,000 cards in circulation and about 560,000 not yet in circulation), and that it forcibly reset the PINs linked to the leaked card numbers. Names, addresses, phone numbers and credit card details were not included. Which other issuers' cards were affected has not been disclosed. This site's conclusion: MOS Card holders should check their usage history for charges they do not recognise, contact the dedicated help line if online balance checks and similar functions stop working, and never give their PIN or card number to anyone who asks.

2026-10-25

Digital Arts cloud services hit by unauthorized access (i-FILTER@Cloud and five others): some customer data may have been viewed, and what administrators should do

On October 21, 2026, Digital Arts Inc., a Japanese maker of web and email filtering and file-security products, announced in a timely disclosure and on its website that it had found traces of unauthorized access to the operating environment of its cloud services and to its internal environment. According to the company, credentials used to operate its cloud services were obtained by an outside party and used to get into the service operating environment. As a result, information on some customers of six cloud services (i-FILTER@Cloud, m-FILTER@Cloud (Modern Edition), m-FILTER MailAdviser for Microsoft 365, FINAL CODE@Cloud, z-FILTER and Desk) may have been viewed by the outside party. The traces were found on October 9 in a company-wide review that used AI, and some go back to around July 2025. As of noon on October 21, no taking of customer data outside the company had been confirmed, and no misuse or secondary harm had been reported. The data items and the number of customers that may have been viewed have not been published. The company asks every customer of the six services to change administrator and user passwords, and will contact some customers individually where more action is needed. On-premises software versions are not affected. In an investor Q&A on October 23, the company said its whitelist database was neither viewable by the intruder nor altered, and that it has reported the incident to Japan's Personal Information Protection Commission. This site's conclusion: administrators at organisations using any of the six services should change administrator and user passwords this week and check whether the company has contacted them individually.

2026-10-25

FANCL and Attenir online store breach (368,184 and 417,312 members): names, addresses, phone numbers and birth dates exposed, and what members should do

On October 16, 2026, FANCL Corporation and Attenir Corporation, two Japanese cosmetics and health-products companies, announced that their online stores had been accessed without authorization by an outside party between October 3 and 10, and that part of their member data had leaked. The access was found in an internal investigation on October 15, and the companies identified and stopped the feature that caused it. The leaked data covers 393,785 records for 368,184 FANCL members and 441,162 records for 417,312 Attenir members. The items are email address, name, address, phone number, date of birth, gender, customer number, a sub email address and its password (a hashed secondary password set by some members; the main password is not included), security question items (answers not included), and other registration data such as points and membership tier. Payment data such as credit cards is not included. No misuse or secondary harm has been confirmed. FANCL's FAQ says affected customers were contacted at their registered email address during October 17. This site's conclusion: members of either company should assume their name, address, phone number and birth date are known, should not follow instructions in emails, texts, calls or letters claiming to be from the companies, and should check through the official site or the shared help line.

2026-10-25

Trustbank's Furusato Choice breach (4,454,097 member records): names, addresses and hashed passwords leaked — what donors should do

On October 20, 2026, Trustbank, Inc., which runs Furusato Choice, a major site for Japan's furusato nozei hometown tax donation scheme, announced that an outside party had gained unauthorized access to member data and that donors' personal data had leaked. After noticing unusual access patterns on October 19, the company found that the unauthorized access had taken place on October 17, and it shut down the related services at 15:50 on October 19. The leak it confirmed covers 4,454,097 member records: name, email address, postal address, phone number, hashed password and estimated donation tax deduction amount. In a second report on October 23, the company said that for five of these donors additional items had leaked, including points history, donation history, date of birth and delivery address. For two of them, an outside party accessed the My Page screen that shows saved card details (last four digits, cardholder name, expiry date). The company says card details are fetched from the payment processor each time that screen is shown and are not stored in its systems, and that they cannot be used on their own to make a card payment. Members have been emailed individually since October 21 about whether their data leaked and which items. In a third report on October 26, the company said it had begun gradually resuming the donation management system used by municipalities and return-gift vendors that day (its FAQ of the same day says from October 25). New donations are not being accepted, and no restart date has been set for the donor-facing site. All members' passwords have been invalidated, and a new password will need to be set after the restart. This site's conclusion: members should change the password on any other service where they use the same email and password combination, and should not open links in messages claiming to be from Furusato Choice or a municipality.

2026-10-24

and ST HD breach (about 2.74 million customer records): what may have leaked and what members should do

On October 23, 2026, and ST HD Co., Ltd. announced that unauthorized access by a third party to its business servers may have leaked part of its customer, business-partner and employee data. According to the company, from around 7:30 a.m. on October 22 (Japan time) login attempts, intrusion and data extraction were carried out against several of its servers in turn; the company detected the unauthorized activity around 10:00 a.m., isolated the servers and cut off the access route by 5:00 p.m. The data that may have leaked covered about 2.5 million customer records (name, date of birth, gender, address, phone number, email address and member ID) and about 10,000 business-partner records (company name, ordering and return addresses, contact person's name, phone number and email address), with the scope for employees still being confirmed. In its results announcement of November 4, the company put the customer records at about 2.74 million (same items) and the employee records at about 24,000 (group social-insurance enrollees from June 2013 to November 2022: basic information such as name, address, phone number and date of birth, plus social-insurance calculation information; My Number data, sensitive personal information and bank account information are not included). It began emailing affected customers individually on November 4 and opened a dedicated desk (0120-668-043, until November 30). The November 4 notice does not mention business partners or member points. Payment data such as credit card details, and passwords set by customers themselves, are not included, the company says. Its and ST web store was not affected by the unauthorized access, but member points currently cannot be used in stores or on the web store. The company says it is starting to contact affected customers and partners in turn and will set up an inquiry desk. This site's take: since passwords are said not to be included, the priority today is not changing your password but doubting messages that use the company's or its brands' names together with your real address or birth date. Check through the official app or a website you open yourself.

2026-10-24

Unauthorized Access to the blastmail Email Delivery Service (All Customers' Account Data, and Mailing Lists and Similar Data for 345 Contracts): What Newsletter Recipients and Client Organizations Should Do

The email delivery service blastmail, provided by RAKUS Lite Cloud Co., Ltd., a subsidiary of RAKUS Co., Ltd., was accessed by an outside third party and data was taken out. The company shut the service down in an emergency at 0:30 a.m. on October 21, 2026, and the parent company RAKUS published a first and second report the same day. According to the notices, the third party intruded into two API servers, ran commands, and connected to the sales management system and the service database to take data out. From the sales management system, the company name, contact name, phone number, email address, billing email address and contract and payment history of every customer were taken. The company does not hold credit card numbers. For some customers, the leak of delivery data such as recipient lists was also confirmed. In its update at 17:00 on October 26, the company said one more case had been found, bringing this to 345 contracts, and that it had contacted all of them individually. The intrusion route is under investigation, and in its update at 12:00 on October 30 the company said the figure was still 345 and that it is aiming to restart around November 11 (subject to change). In notices from client organizations, The Niigata Nippo said the data of all members of its Niigata Nippo Passport service, up to about 253,000 people, including name (in katakana), email address, gender and age band, had leaked. JR Shikoku said about 30,000 records may have leaked, the City of Yokohama disclosed three related mailing services, the Ministry of the Environment disclosed six newsletters, and Japan Petroleum Exploration (JAPEX) disclosed its newsletter and investor-event mailing recipients as possibly affected. giftee said it confirmed its contract was not among the 288 counted as of October 23. This site's conclusion: people who receive newsletters from these organizations should not open links even if the sender name is genuine, and should check through the official site. Organizations that use blastmail should confirm whether they were contacted, decide on reporting to the Personal Information Protection Commission (joint reports with the company: second round of applications until November 5) and on notifying individuals, and warn their own staff about billing or re-login emails claiming to be from blastmail or RAKUS, since contact details of all customers were taken.

2026-10-24

Unauthorized Access to Medley's Clinic System @link (at-link): Patients' Names, Birth Dates, Login IDs and Passwords Leaked — What Patients and Clinics Should Do

On October 15, 2026, Medley, Inc. announced unauthorized access by a third party to its medical-institution management system @link (at-link), the patient-facing at-link app and related services, and said it had suspended them from late at night on October 14. According to the company, it began investigating on October 11 after an outside specialist organization alerted it to possible unauthorized access, and confirmed the access. On October 23 it said it had confirmed that, from late September to mid-October 2026, the third party accessed the company's database through a program it had planted without authorization and obtained information, and that personal data had leaked. For patients who used the at-link app or web booking, the leaked items are name, name reading (furigana), birth month and day, email address (only if registered), app and web-booking login ID and password, the name of the clinic used, registration date, last visit date, and credit card payment history (payment date and amount only; only for those who paid online through the app). For patients who did not use the app or web booking, the leaked items are name, furigana, birth month and day, the name of the clinic used, registration date, last visit date, and the app and web-booking login ID and initial password. The company says it does not hold card numbers. The number of clinics and people affected is under investigation; the company will notify affected people in turn, working with the clinics. It has not disclosed the specific method, saying doing so could invite similar attacks. It has closed the route and invalidated all related credentials, and has reported to the Personal Information Protection Commission and the Ministry of Health, Labour and Welfare. App and web-booking passwords will not be carried over; users will set new ones when the service restarts. In the notice updated at 12:30 on October 28, the company said test use of the clinic-facing “@link Cloud beta” began at some clinics on October 28 (features under test: checking and registering bookings, patient information and the consultation calendar), that the patient app and web-booking site and other services remain suspended, and that it plans to refund fees for the suspension period within November. The investigation into the cause and scope is continuing. This site's view: people who used the at-link app or web booking should change the password on any service where they reused it, and should not open links in messages that mention their clinic or visits. Clinics should direct patient inquiries to the company's dedicated contact.

2026-10-24

Nikkei Unauthorized Access (About 1.83 Million Records): Names, Email Addresses and More Leaked in About 150,000 — What Users Should Do

On October 16, 2026, Nikkei Inc., the Japanese newspaper publisher, announced that a cloud service it uses for system development had been accessed without authorization and that, as of the 16th, about 1.83 million records of personal information had leaked. About 150,000 contained at least one of name, email address, postal address, phone number or date of birth, and about 120,000 of those included an email address. The remaining roughly 1.68 million consisted only of identifiers that cannot identify a person on their own. Credit card information was not included. According to the company, credentials for accessing the cloud service were stolen by some means, and the unauthorized access took place from the early hours to the morning of October 7. The company disabled the credentials used and reported the incident to Japan's Personal Information Protection Commission on October 11. As of the 16th, no secondary harm such as misuse of the data, and no system outage or data tampering, had been confirmed. The company says it will notify individually those whose data is confirmed to have leaked. Group company Nikkei National Geographic said on October 22 that information on some users of its services was included. Which services' users are affected, counts per data item, and how the credentials were stolen have not been disclosed. This site's take: do not use links or phone numbers in emails or calls claiming to be Nikkei; check on the official site.

2026-10-24

Treasure Factory (Trefac) breach (746,277 email records): what home-buyback and Trefac Moving customers should do

On October 23, 2026, Treasure Factory Co., Ltd., a Japanese second-hand goods retailer, announced that an outside party had gained unauthorized access to the case-management system it uses to take and handle requests for its home buyback service (shutchō kaitori) and its Trefac Moving service, and had taken part of the customer and other data held there. According to the company's timely disclosure, the confirmed data is 746,277 customer records (email addresses; 11 of them also include name and address), 750 records of names and email addresses of business partners, employees and others, and 1,000 records of names and device identifiers for devices used by business partners, employees and others. Credit card numbers and other payment information were not included, and customer data held at stores and in the company's app is managed in separate systems and was not affected. The company confirmed the access through an access-log review on October 20 and cut off outside access and the request forms the same day. It believes a vulnerability related to database access was exploited, and says the incident is not related to a recently disclosed PHP vulnerability. No secondary harm has been confirmed. The system and request forms are scheduled to restart around October 28. This site's conclusion: if you have ever requested home buyback or Trefac Moving, assume your email address is known, do not open links in emails claiming to be from Trefac, and check on the official site instead.

2026-10-23

Capcom CAPCOM ID Breach (11,774,247 Records): Email Addresses and Login Data Leaked — What Account Holders Should Do

On October 22, 2026, Capcom Co., Ltd. announced that its online membership service CAPCOM ID (the shared account used for Capcom web services and some online games) was accessed without authorization by a third party, and that part of its customer information leaked. The leaked data are email addresses and system-specific identifier information (account creation date and time, last login date and time, number of logins, and the client IP address used at the last login), in 11,774,247 records worldwide. For 43 of them, date of birth, gender, country/region and nickname also leaked. On 196 of the accounts, the login password had been changed without authorization; the company has already reset those passwords. According to its second notice of October 23, for 19 of those 196 accounts (in Japan), an unauthorized third party accessed the account pages of e-Capcom, the company's online store in Japan, and the following leaked: name, name in Japanese phonetic characters, phone number, postal code, address, gender, date of birth, purchase history, e-Capcom inquiry history and saved address book information. For the remaining 177 of the 196 accounts, the company found no information compromised as a result of the password changes. The company says it has not confirmed any leak of passwords set by customers themselves, and credit card information was not among the affected data. According to the company, it found traces suggesting unauthorized access on October 19, immediately began blocking the access and investigating the cause and scope, and confirmed the unauthorized access the same day; on October 20 it confirmed the leak and the password changes; and on October 21 it reported the incident to the police and Japan's Personal Information Protection Commission. It says it has identified and addressed the attack method, but has not disclosed details of the cause. In the second notice it said the investigation into the scope of impact has been completed and that it will keep monitoring CAPCOM ID and related services. Services using CAPCOM ID and all games remain available. It said it would contact affected customers individually and set up dedicated support channels for each region. This site's take: CAPCOM ID holders should not open links in emails or texts claiming to be Capcom, should not give personal details over the phone, should change any password they reuse elsewhere, and should turn on two-factor authentication.

2026-10-23

Comic Cmoa Member Data Breach (Up to About 4.2 Million Records in Log Files): Email Addresses and Dates of Birth Leaked — What Users Should Do

NTT Solmare Corporation, which runs the Japanese e-book store Comic Cmoa (コミックシーモア), published four notices about unauthorized access to the service, from a first notice on October 15, 2026 to a fourth report on October 21. According to the company, on October 15 it judged that unauthorized access from outside to its servers had very likely taken place and suspended the service at 11:35. In its second report on October 16 it said it had confirmed that member data in the system that manages member information had leaked to a third party (the count was still being examined). In its third report on October 18 it said it had identified the intrusion route and attack method and was dealing with them, and that some system log files had also been viewed and taken. In its fourth report on October 21 it described the data confirmed as leaked as 319 records of registration data in the member database (email address, hashed password, nickname, date of birth, gender) and up to about 4.2 million records in system log files (email address, nickname, date of birth, gender; no passwords; possibly including duplicates for the same person). It says credit card data is not held in the affected systems and did not leak, and that no leak of purchase histories and no leak, loss or damage of MY Bookshelf (users' libraries) has been confirmed. It says identifying and blocking the intrusion route and attack method is complete, but has not disclosed what they were. Affected people will be contacted by email. The service remains suspended and is to resume in stages, starting with web reading of purchased titles; all users will be asked to reset their passwords on resumption. This site's take: anyone who uses the same email address and password as on Comic Cmoa for another service should change that password today, should not open links in emails claiming to be the company, and should check through NTT Solmare's news release page opened themselves.

2026-10-23

Iwai Cosmo Securities vendor breach (4,975 customers): what leaked, the unintended trades, and what customers should do

On October 16, 2026, Iwai Cosmo Securities Co., Ltd., a Japanese brokerage, announced through a timely disclosure by its parent company Iwai Cosmo Holdings that the system of a vendor it uses to operate and maintain its online trading system had been accessed by a third party, and that names, email addresses and other details (氏名、メールアドレス他) of 4,611 online trading customers had leaked. The company detected the access on October 14. In its second notice on October 20, it said a re-examination of access and communication logs found 364 more people, bringing the total to 4,975; it said this was not caused by any later access. The leaked data does not include trading PINs, and the company says it cannot be used to log in to accounts or trade. The second notice also disclosed that on October 14 the trade management system was attacked as well, and orders the customers did not intend were placed in 7 accounts (5 of them were executed). The trades have been reversed and customers bear no cost. The company says the leaked personal data was not used for these trades. It says the point that allowed the access has been identified and fixed, and that the vendor added measures such as access restrictions on management functions. The specific method has not been disclosed. This site's take: do not use links or phone numbers in messages claiming to be from Iwai Cosmo; check your order and execution history from a login page you opened yourself, and contact the official line (0120-405-546) with any concerns.

2026-10-23

Unauthorized Access to Onamae.com Desktop Cloud (GMO Internet) (26,739 Servers Possibly Affected): Customer Data Taken Out, Compensation, and What FX and Securities Traders Should Do Today

On October 21, 2026, GMO Internet, Inc. announced unauthorized third-party access to Onamae.com Desktop Cloud, a VPS (virtual private server) service for FX auto-trading, and said a malicious program had been placed in some customers' server environments. 26,739 servers may be affected; the company says this is the number of servers that could be affected, not the number where unauthorized access or data acquisition has been confirmed. From 04:00 on October 21 it stopped the servers of all plans one after another. In its fourth notice of October 24, the company said a security problem existed in the service's system, and that it had confirmed unauthorized access to the service environment and that customer information had been taken out. It also said some customers had reported trades on their trading accounts that they did not make. Which information was taken and for how many customers, the intrusion route, and the number of affected accounts and amounts have not been disclosed. The company will pay a flat 5,000 yen to every current user of the service, and will compensate realized losses from trades it finds were caused by this unauthorized access (minus any refund from the exchange or broker). It will not restart the current system platform as it is, and will offer a switch to an alternative service on a separate cloud platform, free for six months after switching. According to the company, someone it believes to be the attacker has demanded money and threatened to publish information and take other actions if it refuses; the company says it will not pay and has given evidence to the police. Its fifth notice of October 24 again asks customers to fully scan and back up their own devices, change passwords from a device not used for FX trading, end all signed-in sessions even if they have already changed their password, and set up two-factor authentication. In its seventh notice of October 26, the company said that a party believed to be the attacker had announced it would publish customer information and launch a ransomware attack at 12:00 on October 27. In its eighth notice of October 27, it asked customers to back up their data and then, before 12:00, disconnect from the network, shut down and unplug every cable connected to the PC. In its ninth notice (as of 11:59), it said no malware (including ransomware) had been found on the customer devices it had finished analysing, but that this did not confirm every device was safe, and that customers hit by ransomware who contact its support desk would be given a new PC of equivalent performance after the damage is checked. In its tenth notice of October 27 (as of 13:55), the company said it had confirmed at 12:30 that a party believed to be the attacker had published what it claims is information about the company and its customers (the company is still checking the content and says it may include false information). It said no ransomware attack had been confirmed as of 13:55. It asks people not to visit or share the site where the information was reportedly published, saying that the attacker obtains the information of anyone who visits it. In its twelfth notice (as of 19:10), the company said it would pay a special payment of 10,000 to 25,000 yen per category of information (capped at 3 million yen per publication) to customers whose information it confirms was included in what the attacker published, and set up a bounty capped at US$1 million in total for information that helps identify the perpetrators (accepted from 12:00 on October 28). In its thirteenth notice of October 28 (as of 11:00), the company said it had confirmed that the domain of the site of the party believed to be the attacker (including mirror sites) was suspended at around 04:00 that day, and that it would act to take down any similar site that appears. In its fourteenth notice the same day (as of 18:20), the company said the bounty site, opened at 12:00 that day, had received 113 tips in its first six hours or so (as of 18:00), that it had sent 20 warnings in total about posts on X spreading the URL or content of the site of the party believed to be the attacker (as of 18:00), and that its analysis of devices has found no traces of malware infection or ransomware attack so far. It thanked customers for powering devices off and asked them, if they reuse a PC, to run a security scan and take a backup beforehand. In its fifteenth notice (as of 12:40 on October 29), the company said its group white-hat hacker team had carried out its own investigation and obtained information it believes may lead to identifying the perpetrators, which it planned to submit to the police and other relevant parties that day, and reported 270 tips to the bounty site as of 11:30. In its sixteenth notice (as of 20:50 on October 29), it reported that tips had risen from 113 (as of 18:00 on October 28) to 321 (as of 18:00 on October 29), gave a reporting form (listed in the fifteenth and sixteenth notices) for new attacker sites and sites where personal information is published without authorization, and again asked people not to identify or contact perpetrators, post unverified information or share suspicious URLs. It also says it will take legal action, including criminal complaints, against the attack and the extortion. The disclosure of October 28 says that, according to its parent GMO Internet Group, the group is still checking its companies' services and, at present, no impact from this incident has been confirmed on services other than this one. Customers are reported to have received emails from a sender believed to be the attacker, with part of their browsing history attached as proof that the data is held. The company's group CEO wrote in a blog post that the attacker has threatened to publish information on customers' PCs and to attack them with ransomware, but the company has not said that any customer's PC was actually compromised. Its sixth notice of October 26 asks customers to fully scan the devices they used to connect and to keep browser sync off until their check is done, among other steps. This site's take: from a device you do not use for FX trading, change your broker passwords, end all sessions, and check your trading history and balance. Use only the company's official site and the notices sent to your registered email for compensation, and never give anyone a password that can trade.

2026-10-23

Unauthorized Access to Ymirlink's Cuenote FC Email Delivery Service (Now About 51.63 Million Cumulative Records): Express Reservation and smartEX Member Data Included. What Newsletter Recipients and Client Companies Should Do

On October 26, 2026, Ymirlink, Inc. (TSE Growth, 4372) published a second report on the unauthorized access to its email delivery service Cuenote FC, saying data leaked from 49 systems, a cumulative total of 51,628,280 records. In its first report on October 19 it had estimated five systems and about 9 million cumulative records; after reviewing the logs of all systems, it found records of unauthorized access and data export on 42 more systems on October 25. The leak count is still under investigation for 16 systems, and the cumulative total may rise. It attributes the incident to a library vulnerability and says it confirmed that the credentials of its support and quality-control staff were obtained, malicious programs were installed, and session information captured at login was used to log in without authorization. In its customer management system Cuenote BASE, 190 records of customer contract information (company name, name, phone, email address) were viewable. It says it has found no evidence that the leaked personal data was made public or misused. Among client companies, JR Central, JR West and JR Kyushu announced on October 26 that, although they had first been told their Express Reservation and smartEX services were not affected, the email addresses, member IDs, names (in katakana) and membership types of members sent emails through the service had leaked. In a second report on November 5, they said the number affected is 172,735. AsMarq said the same day it had been told that part of the data registered in the environment it uses had likely been obtained without authorization. On October 27 at 21:00, Bandai Namco Entertainment Inc. and BANDAI SPIRITS Co., Ltd. announced that 346,247 records (email addresses and internal identifiers for managing Bandai Namco ID) had leaked from the THE GUNDAM BASE MEMBERS environment of the Bandai Namco ID email service; they say names, addresses, purchase history, login passwords and credit card details are not included, and that other environments are still being checked. They say emails they send about this will not contain URLs. DCM Holdings (email delivery for its membership program Maibo) said in its October 30 second report that it confirmed a leak affecting 753,272 members (as of October 29), with the email address, member ID, name, gender, birth year and month, and prefecture of residence; passwords, card information and point balances or history are not included. This site's conclusion: Express Reservation and smartEX members should not open links even in emails or SMS that show their katakana name or member ID, and should check through the official app or a bookmarked official site. Newsletter recipients should not open links in emails claiming to come from the sender. Client companies should confirm with Ymirlink whether their environment is affected and decide whether they must report to the Personal Information Protection Commission and notify individuals.

2026-10-22

Recruit Carsensor.net and C-MATCH Breach (Up to 3,709,551 Records): Names and Addresses of People Who Contacted Dealers May Be Exposed — What Users and Dealers Should Do

On October 21, 2026, Recruit Co., Ltd. announced that information on users and business partners of Carsensor.net, its used-car listings site (including the app), and C-MATCH, its business support service for used-car dealers, may have leaked outside as a result of unauthorized access. According to the company, it detected suspicious access from outside to Carsensor.net-related systems on October 17 and suspended all related services from around 17:00 that day. On October 20 it identified the items and the number (maximum) of personal data records that may have leaked. The count is up to 3,709,551 records: 3,210,421 for people who contacted dealers through the site (mostly name and address; addresses are in principle only down to the city or municipality), 5,289 for people who posted reviews, 483,168 for dealers registered with C-MATCH (staff names and phone numbers, secondhand dealer licence numbers, login IDs and so on; for sole proprietors, also direct-debit bank account information), and 10,673 for company employees and staff of contractors and sales agents. None include payment data such as credit cards, or login passwords. The cause is unauthorized access by a third party, with details under investigation. The company has filed a preliminary report with Japan's Personal Information Protection Commission and will contact affected people individually in turn. As of October 21 no secondary harm had been confirmed. Services have been resuming in stages from around 13:00 on October 22, starting with those whose safety has been confirmed. This site's take: anyone who contacted a dealer through Carsensor should assume letters, emails and calls may come from someone who knows their name and address, should not open links or attachments in unexpected contacts, and should check through Recruit's notice page.

2026-10-21

[Breaking] PHP flaws CVE-2026-109618 and CVE-2026-109619 now exploited, added to CISA's KEV catalog: update to 8.5.12, 8.4.27, 8.3.36 or 8.2.35 now

On October 21, 2026, the PHP security team released PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35, fixing two critical vulnerabilities that can allow unauthenticated remote code execution (RCE), and urged all users to update immediately. CVE-2026-109618 involves out-of-memory handling and CVE-2026-109619 involves stale internal state surviving between requests; both are rated 9.2 under CVSS v4.0. All PHP installations serving web requests are at risk (PHP-FPM, Apache mod_php, php-cgi, FrankenPHP, LiteSpeed). The team considers mod_php the highest risk, citing a demonstrated exploit in which an unauthenticated request triggers the attack before any application code runs. PHP 8.1 and older get no official update; the team provided minimal source backports for 7.4, 8.0 and 8.1. Linux distributions received the patches in advance. There is no complete mitigation; updating is the only safe choice. On October 22, Japan's IPA and JPCERT/CC issued alerts and JVN published JVNVU#99905564. CISA, which had not observed exploitation when it first published its alert, added both flaws to its Known Exploited Vulnerabilities (KEV) catalog on October 26, with an October 29 deadline for US federal civilian agencies. According to media reports, a security researcher's honeypots running unpatched PHP 8.4.26 under mod_php saw successful remote code execution on October 24. A major cloud provider's honeypots had seen exploitation attempts from October 17, four days before disclosure. As far as this site could find, no break-in outside honeypots had been made public as of October 27. Most major Japanese shared-hosting providers have announced that the fix is applied, but some, such as KAGOYA, have not. On October 23, the PHP team disclosed a third issue (CVE-2026-115560) that the October 21 releases do not fix. It can lead to code execution only under a specific combination of configuration and application code; the team calls it unlikely in practice, will ship the fix and a full advisory with the next regular release, and recommends setting session.upload_progress.enabled=0 until then. Affected versions and a CVSS score have not been published, and no exploitation has been reported. As of October 29 (checked on php.net), no fixed release for this issue was out. On October 28, CISA also added the Linux kernel flaw CVE-2026-46300 to KEV (October 31 deadline for US federal agencies) and said it can be chained with these two flaws to implant PHP webshells and run commands as root. This site's take: exploitation is now confirmed, so confirm whether you or your provider updates PHP for each site and move to the fixed version today. Also check logs from October 17 onward for signs of a break-in. On shared hosting, check your provider's completion notice on its official website.

2026-10-20

H2O ID Data Breach (About 1.26 Million Records) via the Hankyu and Hanshin Department Store Reservation Site: Addresses, Phone Numbers and Birth Dates Leaked — What Members Should Do

On October 19, 2026, H2O Retailing Corporation and Hankyu Hanshin Department Stores, Inc. jointly announced that the Hankyu and Hanshin department store reservation site, HANKYU HANSHIN E-STORES and Remo Order, all run by Hankyu Hanshin Department Stores, had been accessed without authorization by a third party, and that part of customers' personal data had leaked. On October 16 the companies confirmed unauthorized access to the customer management system via the reservation site and stopped that site's whole system; on October 17 they confirmed unauthorized access at E-STORES and Remo Order as well and stopped both. On October 19 it was established that part of the personal data of about 1.26 million H2O IDs managed in the customer management system had leaked. The notice says part of the personal data of almost all H2O ID members leaked. The items are H2O ID, name (kanji and katakana), gender, email address, postal code, address, mobile phone number, phone number, age, date of birth, and the services used with the H2O ID. For E-STORES and Remo Order, whether data leaked is under investigation; the companies list the data those services hold as order history, part of credit card information (card type, last four digits, cardholder name, expiry date), part of point card information, and address book information. Full card numbers and security codes are not held. No leak of login passwords has been confirmed, and no misuse or secondary damage has been confirmed. The cause is under investigation. E-STORES reopened at 14:00 on October 19. This site's take: expect convincing messages that know your name, address, phone number, birth date and which services you use; do not open their links, and check on the official site you open yourself or through the contacts in the notice.

2026-10-20

NIFTY Line Application System Breach (Up to 542,513 Records): Member IDs, Names, Addresses and Phone Numbers May Be Exposed — What Fibre Customers Should Do

On October 19, 2026, NIFTY Corporation, a Japanese internet service provider, announced (first report) that it had confirmed unauthorized access from outside to its line application and acceptance management system. According to the company, it confirmed the unauthorized access at around 10:20 on October 19 and immediately blocked access from the source. The system is an internal management tool the company uses to register information; it is separate from the website (application forms and so on) that customers use to apply directly. Up to 542,513 records may be affected. They cover customers who applied for a line since 2019 (excluding the company's website), for the services @nifty Hikari, @nifty MAX Hikari and @nifty au Hikari Plus. The items are member ID, name, gender, date of birth, address, phone number and email address; this is the full list of items that may have leaked, and what actually leaked is under investigation. The system holds no bank account or credit card data, which is not included. The notice does not mention passwords. The cause has not been disclosed; the company is investigating with outside specialists and is in the process of reporting to Japan's Personal Information Protection Commission. This site's take: anyone who applied for one of these services since 2019 should assume contacts may come from someone who knows their name, address, phone number and birth date, and should not follow links or instructions in emails, texts or calls claiming to be NIFTY. Check through an official contact you look up yourself.

2026-10-20

Unauthorized Access to the Studio Website Builder: All Users' Data and Form Submissions May Have Leaked — What Form Senders and Site Owners Should Do

On October 16, 2026, Studio Inc. announced that a third party had gained unauthorized access to the cloud environment it uses, and that data on every customer registered with its website builder Studio may have been leaked. The third party exploited a vulnerability in some Studio features to access the environment and made its data retrievable from outside. The confirmed period of unauthorized access is September 30 to October 1, 2026 (Japan time); the company found it in an internal investigation on October 13 and finished fixing the vulnerability and closing the route on October 13–14. Data that may have leaked includes account data (user names, email addresses, hashed passwords and more), design editor and CMS content, the contents of forms submitted on Studio-built sites, live preview URLs, API keys and tokens for external services registered in API integrations, passwords of password-protected pages, and webhook notification URLs. Some data stored encrypted may also have been read, because the key needed to decrypt it was read in the same access. The company has not confirmed that a third party actually took the data, but is treating it as taken. The number of people affected and whether any misuse has occurred are under investigation. Companies and organizations that built sites with Studio have also said that personal data sent through their forms may have leaked: Luup gave 21,368 records, Link-U Group 7,663, TRUSTART about 1,440 and Saitama Prefecture's Saitama Green Forest Museum 162. Japan's Digital Agency said on October 22, after Studio Inc. reported the incident to it on October 16, that inquiries entered in its website's contact forms between May 2021 and March 2023 (five categories, up to 8,833 records in the largest; up to 13,323 in all, as added up by this site) and 35 Studio account records may have leaked. On reporting to Japan's Personal Information Protection Commission (PPC), Studio Inc. first asked form users on October 17 to put individual reports on hold, then said on October 20 that, after talks with the PPC, customers can choose to report individually or jointly with Studio (either way, customers still decide on notifying the affected individuals). On October 19 it added to its guidance page that even responses that are sales pitches, spam or raise safety concerns in principle require notifying the individual if they contain information that identifies a person. This site's conclusion: if you sent a form on a Studio-built site, check that site owner's notice and do not open links in messages that mention what you sent. Site owners should change their password and rotate integration keys in the order Studio Inc. gives.

2026-10-17

Burger King Japan App Breach (About 11.18 Million Records): Names, Birth Dates and Phone Numbers Leaked — What Members Should Do

On October 15, 2026, BK Japan Co., Ltd., which runs Burger King in Japan, announced that the official Burger King app it operates had been accessed without authorization by a third party, and that it had confirmed the leak of app members' information. The access took place from October 2 to October 7, 2026, and the leak was established on October 13. About 11.18 million app member records are affected. The items are member ID, email address, registration type, prefecture, gender, date of birth, name (in kanji and katakana), phone number, whether the member has a mobile order history, and whether the email address has been verified. The company says it does not hold credit card numbers, so they did not leak, and that no leak of login password information has been confirmed so far. The detailed cause is under investigation with an outside specialist organization, and no secondary damage such as fraudulent use had been confirmed at the time of the notice. There was no follow-up as of October 17. This site's take: expect convincing messages that know your name, birth date and phone number; do not open their links, and check in the official app you open yourself. If you use your birth date as a PIN or password, change it.

2026-10-17

SourceNext Member Data Leak (22,519,960 Records): Emails, Passwords and Addresses May Be Exposed — What Members Should Do

On October 15, 2026, SOURCENEXT CORPORATION announced that a third party had gained unauthorized access to member data it manages and that personal data of its registered members had leaked outside the company. According to the company, from around 10:00 on October 9 a third party misused a member data retrieval API to obtain member information; the company confirmed the unauthorized access at around 9:00 on October 13 and completed containment by 13:36 the same day. The data that may have leaked covers 22,519,960 records. The items are email address, password, name, name in katakana, address, gender, phone number, fax number, date of birth, company name, job title, department and system identifiers (subscribed services, registration date, login date and so on); the items differ by how each member registered. Credit card data is not stored in the affected system and is not included, the company says. In an update on October 16, the company said every member's password has already been disabled and the old passwords no longer work, and asked members to set a new one. An October 19 report attributes encrypted storage and confirmed decrypted exposure to the company’s spokesperson. The company's FAQ says it asked an independent outside security specialist to start a third-party investigation on October 16, that its Super Security and Virus Security products can still be used as before, and that data saved in 1Password is not held by the company and is not part of the leak. Separately, on October 27 and November 5 the company announced that a third party had gained unauthorized access to the provider of the email delivery service it used (a contractor), so email addresses and order information used for deliveries may have leaked (142,669 records, counted as distinct email addresses, in the November 5 second report; passwords, names, addresses, phone numbers and credit card information are not included). The company says this is a separate incident, unrelated to the October 15 one. In its second report of November 13 (including an interim report from outside specialists), the company corrected the period in which data was obtained to early morning (4 a.m. hour) on October 9 until about 1:40 a.m. on October 11 (its October 15 notice said from around 10:00 on October 9), said the record count of about 22.52 million matches the October 15 figure, that no specification returning credit card numbers was found, and that no secondary harm had been confirmed. The final cause and prevention measures are due around early December, together with its report to the Personal Information Protection Commission. This site's take: anyone who has registered with SourceNext should first change the password on any other service that uses the same email and password, then set a new SourceNext password through the official website opened themselves, and not use links or numbers in emails, text messages, calls or letters claiming to be SourceNext.

2026-10-15

Unauthorized Access to Some ConoHa WING (GMO Internet) Web Servers (426 Accounts): Data in Customers' Web Server Areas Affected, and What Site Owners Should Do Today

On September 20, 2026, GMO Internet, Inc. announced that on some hosting servers (web servers) of its ConoHa WING rental hosting service, a third party had gained unauthorized access to the web server areas of some customers and installed a malicious program. 426 accounts are affected, and the data concerned is 'data stored in customers' web server areas'. The access and installation began on September 3; the company detected it on September 16, and on September 18 identified the cause and scope and removed the programs. It says it has identified the cause but has not disclosed it. Member, contract and payment data are managed in a separate environment and were not leaked, it says. The notice does not say whether data in the web server areas was taken. Affected customers were contacted individually at their registered email address, and customers who were not contacted are not affected. There was no follow-up notice as of October 15. This site's take: first check whether you received an individual email and, if so, follow its instructions. Then treat the credentials kept in your web server area (the database password in wp-config.php, API keys in .env and so on) as read and change them, and look for files, administrators and scheduled jobs added since September 3.

2026-10-14

IDARE data breach (129,659 people): balances, transaction history and some ID document numbers leaked — what users should do

On October 13, 2026, Fivot Inc. announced that its cashless app IDARE had suffered unauthorized third-party access that leaked personal data. A vulnerability in outside software the company used for customer support and other work was exploited, and data in the company's database was obtained on multiple occasions between August 10 and September 27. The people affected are the 129,659 who had registered by September 27, including those who had closed their accounts. For everyone, the leaked data includes phone number, email address, date of birth, user ID, display name, account settings and status, balance, transaction history, and the name and expiry date on the IDARE card. For some people it also includes the name, address, gender, purpose of use and ID document number submitted for identity verification, the last 4 digits of the IDARE card number, the first 6 and last 4 digits of a credit card registered for top-ups, the last 3 digits of a bank account registered for top-ups, the activation code for the physical card, and annual income and employer details entered for LADDER, a lending service that closed in October 2021. Login passwords, images of ID documents and faces, My Number, full card numbers, security codes, PINs and full account numbers were not involved. The company says no fraudulent transactions have been confirmed and that multi-factor authentication is required to log in. In its second report on October 21, it said no fraudulent transactions had been confirmed as of that date and set out prevention measures with deadlines (October 30 and November 30). A third-party investigation by an outside specialist organisation is expected to be compiled by late November to early December, and the company says it will publish the report when it is complete. This site's conclusion: the leaked data alone cannot be used to log in or pay, but a message that correctly states your balance or recent purchases is not proof it is genuine. Do not act on messages claiming to be IDARE, a card company or a bank through the channel they arrived on, and never give anyone your password, PIN, security code or authentication code.

2026-10-14

SpeeCAN RAIDEN Breach (2026): Disaster-Alert Email Users and Scam Risks

On October 13, 2026, Arcadia Inc. announced that SpeeCAN RAIDEN, its mass-notification service for email and other messages, was accessed without authorization by a third party, and that contact names, email addresses, phone and fax numbers, staff and contract information, and the text of delivered messages stored as history may have leaked. The maximum counts are about 3,136,000 email addresses, about 105,000 phone numbers and about 15,000 fax numbers (all estimates, still under investigation). Arcadia saw suspicious activity at 16:30 on October 11, applied an interim block around 3:00 on October 12, and at 11:00 on October 13 shut down the services that had been the intrusion route (raiden3, and s2 for Raiden School). On October 14 it added NET119 and 119RAIDEN to the possible leak, and in its 11th update on October 16 gave figures per service: for NET119, personal data such as names, dates of birth and addresses linked to 9,020 email addresses (it confirmed that no sensitive personal data leaked); for 119RAIDEN, about 97,000 email addresses and other data. The suspended services were restored around 15:00 on October 15. Payment data is not handled. Municipalities have issued their own notices; Shizuoka City says it has established that email addresses of 34,336 registered residents and other data leaked, and has seen fake emails posing as a card company sent from the same domain as the real alerts, @raiden.ktaiwork.jp. In its 17th update on October 21, Arcadia said a malicious program sent 1,423,428 phishing emails from its system between 1:17 and 7:16 on October 13, that at least 869,575 of them went to addresses the company does not hold, and that an outside organisation will carry out a dark-web survey. It has also emailed clients and resellers about filing the reports to the Personal Information Protection Commission and the Ministry of Internal Affairs and Communications on their behalf. In its 20th update on October 22, it told clients they must use two-step authentication at login, to prevent a recurrence, and in its 22nd update on October 23 it asked Raiden School clients to do the same. In the report published with its 21st update on October 23, it says a configuration file was obtained through a vulnerability in the media server that publishes attachments, leaking a secret key used for logins between services, among other causes; that all services are within the scope of the possible leak; and that the count is still under investigation (9,020 of them for NET119). It has asked a third-party security organisation for a detailed investigation. In its 25th update (17:00, November 2) it said that, separately from the October 13 sending, suspected phishing emails were also sent externally from its system on October 22 and 23. It gives two causes: the mail-sending API account leaked during the October 11 to 13 intrusion and its password was broken by brute force and used from outside, and after the API integration was stopped, a URL parsing confusion vulnerability was used to abuse the API again. It says it stopped the API integration at about 6:30 on October 22 and fixed the vulnerability at about 10:30 on October 23, and that the unauthorized emails stopped. In the 26th update at 16:15 on November 6, it said it is resuming the API integration for external systems that was stopped in the 19th update; customers need to change settings to use it again, and those affected are being contacted individually. In its 27th update at 13:15 on November 19, it published preliminary results of an outside vulnerability assessment and a dark-web survey (the final report is expected in early December). According to the preliminary reports, no notable vulnerability with a significant effect on the safety of all its cloud services was found, and the directory path traversal vulnerability that it names as the direct cause of this intrusion was confirmed to have been fixed. It also says the survey found no confirmed instance of the possibly leaked personal data being published on the internet (that is, publication was not confirmed; the reports do not say there was no leak). Our conclusion: the sender cannot tell real from fake, so do not block the disaster-alert sender, and do not open links in emails asking you to confirm card or personal details.

2026-10-12

Unauthorized Access to Commune (166,505 Member Records, Counted per Community): Member Data from Corporate Communities Leaked — What Members and Operators Should Do

On October 9, 2026, Commune Inc. announced that its community services for businesses, Commune and Commune for Work, were accessed without authorization by an outside third party, and that member data in some communities leaked. The leaks occurred from about 18:00 on October 5 to about 21:00 on October 6, and from 13:17 to 14:36 on October 7 (Japan time). Its first notice gave about 307,000 members (an estimate of unique people) as the maximum possibly affected. In a follow-up on October 21, after a detailed investigation, it confirmed that 166,505 members were affected (the total of member IDs counted per community, so people in several communities are counted once for each; this includes communities run by the company and test/demo communities, and excludes accounts created by the attacker), and that 125,601 of them had data including email addresses leaked. For the others, the leaked data includes display names, profiles and private group memberships. For 144 members, passwords were changed to temporary ones without their action. No leak of the passwords themselves or of direct messages was confirmed, and the company does not hold payment data. It attributes the incident to invitation links for private communities obtained illegitimately and to impersonation of administrators. Client companies that run communities on the service have also published notices; JMAM said the names, addresses, ages and phone numbers in member profiles on its Toki Labo community also leaked. To prevent misuse of the leaked email addresses, Commune Inc. stopped all communities for emergency maintenance from 00:50 on October 10 and took measures such as making two-factor authentication mandatory for administrator accounts. On October 16 it announced that communities would reopen in stages, starting with clients that ask, in the web browser version only and with some features restricted (the app, new registration with an email address and “forgot password” resets remain unavailable). It says no new unauthorized access or leak was found during the maintenance or testing. The October 21 follow-up also says the company filed a preliminary report with the Ministry of Internal Affairs and Communications (Kanto Bureau of Telecommunications) on October 9, has begun consulting the police, found no programs, accounts or settings left behind by the attacker after analysing all logs, and is preparing a forensic investigation by a third-party organisation. This site's take: check the notice of the company that runs your community to see whether you are affected, and do not open links in emails that claim to come from the community.

2026-10-12

Japan's online ID checks move to IC-chip reading (April 2027): what changes, and how users and businesses should prepare

An amendment to the Ordinance for Enforcement of Japan's Act on Prevention of Transfer of Criminal Proceeds (promulgated 24 June 2025, in force 1 April 2027) ends, in principle, non-face-to-face ID checks that rely on images or copies of ID documents for bank accounts and other covered transactions. Reading the IC chip in a driver's license or My Number Card, and the card's electronic certificates (JPKI), become the main methods. In-person checks also change to presenting the document and having its IC chip read. Mobile phone contracts made online already switched on 1 April 2026; in-store contracts follow from April 2027. On 9 October 2026 the Financial Services Agency, citing the current situation of repeated unauthorized access and leaks of customer data that included driver's license images, asked financial institutions to move to IC-chip reading without waiting for the effective date. This site's conclusion: a leaked image can be reused by anyone, but IC-chip reading needs the physical card and its PIN. Users should check their two license PINs and My Number Card PINs now; businesses should stop collecting and keeping document images.

2026-10-11

Japan data breach statistics: 17,139 leak reports to the Personal Information Protection Commission in FY2025, and about 80% of those filed directly were human error

A statistics page on leak reports (rouei-tou houkoku) filed with Japan's Personal Information Protection Commission (PPC). Reports from businesses: 4,141 in FY2020, 5,846 in FY2021, 7,685 in FY2022, 12,120 in FY2023, 19,056 in FY2024 and 17,139 in FY2025. Reporting certain leaks became mandatory in April 2022, and leaks of sensitive data such as medical history must be reported even when only one person is affected, which pushed counts up. For reports filed directly with the commission in FY2025, the causes were handing documents to the wrong person (48.3%), sending to the wrong recipient (26.0%) and unauthorized access (9.4%). Our conclusion: the count is driven by documents handed or sent to the wrong person at hospitals, pharmacies and similar counters, so organizations should first add recipient checks. Large incidents affecting many people are mostly unauthorized access and call for patching internet-facing devices, multi-factor authentication and managing contractors. Updated each quarter when the PPC publishes.

2026-10-10

Baitoru breach (up to about 3.89 million email addresses): only emails leaked — how members can spot fake interview messages and job scams

On October 9, 2026, dip Corporation announced that on October 6 it had confirmed unauthorized third-party access to Baitoru and Baitoru NEXT, the job sites it runs in Japan, and that some member email addresses had leaked. The number of addresses that may have leaked is up to 3,885,771. The company says only email addresses leaked and that names, phone numbers, passwords and credit card details were not included. It attributes the cause to unauthorized access from overseas that exploited a flaw in the specification of part of its system. It blocked all access from overseas and modified the program. It has not confirmed any posting of the data online or any misuse. Affected members were told on the services on October 6 and are being contacted individually by email and other means. There was no follow-up notice as of October 10. This site's take: even if only email addresses leaked, they are known to belong to job-site members. Do not open links in messages about interview schedules or application confirmations; check in the official app you open yourself. Do not move to other messaging apps or answer offers of 'high pay, paid the same day'.

2026-10-10

Bookoff Member Data Leak (6,383,279 People): Names, Addresses, Emails and Password Hashes May Be Exposed — What Members Should Do

On October 9, 2026, BOOKOFF GROUP HOLDINGS LIMITED announced that a third party had gained unauthorized access to the member management system for Bookoff in Japan, provided by its subsidiary BOOKOFF CORPORATION LIMITED, and that member data had been leaked outside the company. According to its second report on October 13, member data was taken from outside between October 4 and 6. The count is 6,427,735 records by member number, or 6,383,279 people when member records registered with the same email address are counted as one person (212,371 of them former members). Those affected are app members, online store members and web members; people who only use a member card and never registered through the app or web are not included. The data that may have leaked is name, date of birth, gender, occupation, nickname, email address, phone number, postal code and address, password hash, point card number and member number (occupation and nickname were added by a correction on October 16), though not every item leaked for every member. Payment data such as credit card details, bank account details, text read from ID documents at in-store buybacks and ID document images from mail-in buybacks are not included. The company emailed affected members in stages from October 15 (sending to every address it could confirm as deliverable finished on October 22) and asks them to change their passwords for the official online store and app. On October 23 it announced a web lookup on the Bookoff member site that lets members sign in and check whether they are affected, and said it had opened a dedicated toll-free line on October 22. In its third report on November 6, it said an investigation with outside experts found that a third party had exploited an access-control problem in part of the system that handles member data; it is withholding technical details such as the system configuration and settings. According to the third report, the scope (services, people and data items) is unchanged from the second report, and from October 26 to 29 it also notified affected members individually through notices in the official app. No publication of member data, misuse of points or alteration of member data has been confirmed, and the company says it will fully compensate points if misuse resulting from the incident is confirmed. It plans to submit its final report to the Personal Information Protection Commission in early December. This site's take: anyone who registered through the app or online store should change the password through the official app or a website they open themselves, change it on any other service that shares it, and not open links in emails or texts claiming to be Bookoff.

2026-10-10

Malware on a Daiichikosho Contractor's PC (About 8.72 Million Records): Big Echo and Other Members' Names, Birth Dates and Phone Numbers May Have Leaked — What to Do

On October 8, 2026, Daiichikosho Co., Ltd. announced that a company to which it outsources the handling of personal information had reported that one PC used by one of its employees was infected with malware, and that Daiichikosho's customer information may have leaked. Personal data related to the outsourced work had been temporarily stored on that PC. The records concern about 8,631,000 customers who registered as members or made reservations at the company's stores (Big Echo, Mega Big, Karaoke CLUB DAM, Banana Club, B-GARAGE and DK Dining, after removing duplicates) and about 93,000 employees, about 8,724,000 in total. The items are name (registered name), gender, date of birth, email address and phone number. Passwords were not included, and the company says points cannot be used with this information alone. No actual external leak, misuse or impact on the company's own systems had been confirmed. A toll-free inquiry line opened on October 9. In an addition dated October 26, the company said it is contacting customers who may be affected individually, in turn, by SMS and other means, and published the sender numbers (NTT Docomo, au and Rakuten Mobile: 05036052572, which may appear as +815036052572; SoftBank: 247473). It says this contact does not mean a new leak has been found, and that no actual external leak or misuse resulting from the incident has been confirmed. It also says the sender number alone does not guarantee that an SMS is genuine. On November 6 it published the results of a forensic investigation by an outside specialist organisation: malware infection and unauthorized communication with an outside server were found on the device the contractor had been using, and the malware had a function to send information on the device to outside parties, but what information was actually sent, and how much, could not be identified. No leak or misuse of personal information resulting from the incident has been confirmed. No traces suggesting remote control were found, and the malware had already been neutralized when the investigation began. Individual notices to customers who may be affected continue. This site's take: do not open links in messages claiming to be Big Echo or DAM about coupons, membership renewal or points, or in texts claiming to be from Daiichikosho; check in the official app or a site you open yourself, and stop using your birth date as a PIN or password.

2026-10-10

JR East, VIEW Card and JR Kyushu Possible Email Leak (2026): What to Do

On October 9, 2026, East Japan Railway Company (JR East), VIEW Card Co., Ltd. and Kyushu Railway Company (JR Kyushu) each announced that the external service they use to send email to members had been affected by unauthorized access at a cloud service provider, and that they could not rule out that members' email addresses and other data had been viewed or obtained. The numbers are, at most, about 1.67 million eki-net members and about 390,000 Otona no Kyujitsu Club members (JR East); about 4.03 million email addresses of VIEW's NET users (VIEW Card); and, at most, about 1.3 million JR Kyushu Web members (JR Kyushu). For eki-net, VIEW's NET and JR Kyushu Web members only email addresses are involved; for Otona no Kyujitsu Club members, the member number, credit card expiry date and date of birth are involved as well. Names, addresses, phone numbers and card numbers are excluded. The cloud service provider has said that the outage which began early on October 7 was caused by a ransomware attack by a third party. In its fifth report on October 14, the provider said it had found no trace of data in virtual servers in the affected area being viewed or taken out, and concluded that no data leaked externally. On October 15, after receiving those findings, JR Kyushu announced that no leak of JR Kyushu Web members' email addresses had been confirmed. JR East's eki-net site also says that on October 15 the email delivery service company reported that it had concluded no personal data of eki-net members leaked (checked October 19). For Otona no Kyujitsu Club members and VIEW Card, this site could find no follow-up as of October 19 (checked on each company's site). In its seventh report on October 27, the cloud service provider said its investigation was complete and named the cause as a vulnerability in open-source software used in the authentication system of its customer management portal. Its conclusion that no data in virtual servers leaked externally is unchanged. This site's take: JR Kyushu said no leak was confirmed, and eki-net says it was told no personal data of eki-net members leaked. Even so, fake emails using this incident as a pretext may still arrive. Do not log in from links in emails; check through the official app or a bookmark you saved yourself.

2026-10-10

Unauthorized Access to Lawson ID (2,155,345 Records): Email Addresses and Names Leaked — What Members and App Reservation Users Should Do

On October 8, 2026, Lawson, Inc. announced that unauthorized third-party access to its account service Lawson ID, and to Lawson App Reservation (a service for reserving and paying for seasonal event products in the app), had leaked personal data. An investigation on October 7 found that Lawson ID was accessed without authorization from September 12 to 14 and App Reservation on September 17. The company confirmed leaks of 2,155,345 Lawson ID records (email address and name, plus gender, phone number, address and newsletter preference where these had been entered, for example when applying for a giveaway with Lawson ID) and 26 App Reservation records (name, phone number and part of the credit card number). The company says a system related to the Lawson app was misused, and that a security mechanism meant to show information to the user themselves in the app was accessed without authorization by a third party. Passwords are not among the listed items. As of October 8 no misuse or secondary harm had been confirmed, and on October 13 it added lawson_id@id.lawson.jp as a sender address for the individual notification emails. This site's take: Lawson ID holders should not open links in emails or texts claiming to be Lawson or offering points or coupons, and should check through the official app they open themselves.

2026-10-10

NewsPicks Data Breach (Card Holder Names and Last Digits, 361,598 Records): What Leaked Through a BI Tool and What Users Should Do

On October 8, 2026, Uzabase, Inc. announced that an admin tool used in the operation of its news service NewsPicks had been accessed without authorization by a third party, and on October 9 it gave maximum estimated counts. Its investigation report of November 18 says the entry point was a vulnerability in the BI (data-analysis) tool Metabase that could be exploited before login (CVE-2026-72898), which let the attacker bypass multi-factor authentication and impersonate an administrator, and that the unauthorized access ran from August 10 to September 28. The confirmed counts are lower than the October maximums: part of the card data used for web payments (card holder name, expiry date and the last 3 or 4 digits of the card number) 361,598; email addresses 322,531; job-level category 272,392; affiliation 64,572; names 58,754; and others. Full card numbers and security codes were never stored on its systems, and login passwords (including hashed ones) were not part of the data taken. No secondary damage has been confirmed. This site's take: a message that quotes your card's last digits, expiry date or employer is not proof that it is genuine. Do not open links, check through the official app or a site you open yourself, and keep an eye on your card statements.

2026-10-10

skyticket (Adventure Inc.) Data Breach (About 14.64 Million Records): Passwords, Refund Bank Details and Some Users' Card Data Exposed — What Users Should Do Today

On October 9, 2026, Adventure Inc. announced three separate incidents of unauthorized access, each by a different route, affecting its travel comparison and booking site skyticket. In the first, an administrative function was misused and used as a starting point to reach other servers and data stored in the cloud; about 14.64 million records leaked, including names (also as written in passports), dates of birth, email addresses, phone numbers, addresses and the remitter name used for bank transfers, and about 4.13 million of them included hashed member passwords. In the second, a vulnerability in a business management system was exploited, and 17,780 records (including duplicates, with more still being counted) containing refund bank account details leaked or may have leaked. In the third, a bus booking completion page could be displayed without logging in, and about 12,000 bookings were or may have been viewed. The company first said card numbers were not among the leaked data, but corrected this in a second notice on October 16: the card number, cardholder name and expiry date (for some, the number only; no security codes) of up to 6,140 people who registered or used a credit card to pay the "skyticket Premium" membership fee between February 2017 and June 2018 leaked in the first incident, along with member IDs, names and passwords for a welfare benefits service offered as a Premium perk. Passport images were not exposed, and as of the October 9 notice the only confirmed secondary harm was one unauthorized login to a member account (the second notice does not say whether the leaked card data has been misused). This site's take: members should change their password from the official site or app today, change it anywhere it was reused, check card statements from October onward if they registered or used a card for the Premium fee in that period, ignore messages about refunds, compensation or booking changes, and never give anyone a bank PIN or one-time code.

2026-10-07

Card-Stealing Program on the PhotoGoods (Daiko Printing) Payment Page: What People Who Paid Between August 6 and September 11 Should Do

On September 16, 2026, Daiko Printing Co., Ltd. announced unauthorized third-party access to PhotoGoods (photo-goods.com), the service it runs, and said a program able to illegally capture credit card data entered on the payment page had been installed. The program was in place from August 6 until it was removed on September 11. People who entered a card on the payment page in that period (including those who did not complete a purchase) may have had their card number, expiry date and security code exposed, along with name, address, phone number, email address and information derived from their member password (stored in a converted form). The company says it confirmed unauthorized access through system vulnerabilities and abuse of a file-upload function. The number of affected people and the actual scope are under investigation, and there was no follow-up notice as of October 7. This site's take: anyone who entered a card in that period should ask the card issuer to change the number, change the password on any other service that shares the PhotoGoods password, and ignore links in 'apology' or 'refund' messages.

2026-10-06

Asahi Kasei Therapeutics Possible Data Breach (2026): Who Is Affected and What to Do

On October 6, 2026, Asahi Kasei Therapeutics Co. Ltd., the pharmaceutical arm of Japan's Asahi Kasei group, announced that Pharma DIGITAL, its information site for healthcare professionals, had been hit by a cyberattack and that personal data in its member database may have been viewed or taken. The data covers about 514,000 healthcare professionals (name, facility name, facility address, job type, specialty and more), about 44,000 of them with email addresses and more in addition to those items, and about 700 company employees (name, email address, photo). The company learned of the access from the site's contractor on October 2 and shut the site down. It says it did not store credit card data or sensitive personal data such as medical history, and as of October 6 no misuse had been found. This site's take: expect fake emails posing as drug companies, academic societies or seminar invitations. Never log in from email links, and change any password you reused from this site.

2026-10-06

Daiwa Securities vendor breach (about 110,000 customers, 220,000 records): what may have leaked and what customers should do

On October 5, 2026, Daiwa Securities Co. Ltd., one of Japan's largest brokerages, announced that the server of a vendor whose service it uses to manage customers' online inquiries had been accessed without authorization. Names, email addresses, account numbers and other information about 110,000 customers, held in inquiry records, may have leaked; including inquiries that identify no one, about 220,000 records are involved. The access took place between about 8:33 p.m. on October 2 and 8:01 a.m. on October 3, and no unauthorized access to Daiwa's own systems was found. The company says this data cannot be used to access accounts or trade, including through online trading, and as of October 5 no fraudulent trades and no publication or spread of the data had been found. On October 6 the vendor side published its own notice: inquiry data stored in the environments of up to five client companies on the same server, up to 713,126 records counted per inquiry, may have been taken. Citing the same vendor, Citizen Watch (about 100,000 people), Sompo Japan (about 60,000 records counted per inquiry) and ORIX Life Insurance (about 26,500 records) have also announced that their customer data may have leaked. This site's take: expect fake messages that know your account number and your past inquiries. Never log in from links in emails or texts; sign in from a bookmark or the official app and check your message box and operation history there.

2026-10-06

Japan e-Tax Gift Tax Data Exposure (2026): Who Is Affected

On October 2, 2026, Japan's National Tax Agency (NTA) announced that gift tax returns and related documents of 79 people could be viewed by other users in MyPage on e-Tax, the national online tax filing and payment system. According to reports, this lasted from 8:30 on September 24 to midnight, and from 4:00 to 15:58 on September 25. Nineteen users may actually have viewed someone else's return, and personal information of 203 people in total — filers plus the donors and tax accountants named in the returns — may have been seen. The cause was a defect introduced by a September 24 update that expanded MyPage's gift tax information feature; it has been fixed. NTA regional bureau and tax office staff contacted affected people individually, and the 19 viewers were asked to keep the information confidential and delete it. No sign of saving or secondary harm has been found. The NTA says this is unrelated to problems with its new core system (KSK2). This site's take: affected people are being contacted by the tax office. For any call or text that uses this incident as a reason, follow the NTA's advice: hang up and call back on a tax office number you look up yourself. Developers should test, on every change, that requesting user B's data while logged in as user A is refused.

2026-10-06

infoQ survey site breach (894,082 records): what leaked and what members should do

On October 5, 2026, GMO Research & AI, Inc. announced that its survey site infoQ had been accessed by a third party without authorization and that members' personal data had been taken out. In its second report on October 14 it confirmed the number of records taken out as 894,082 (the first report said up to 948,498), and the final report of November 11 keeps that number. The items are name, name reading (furigana), gender, date of birth, email address, home address, phone number, encrypted password, member ID, and other registration data such as nickname and point balance. The company does not hold credit card data or My Number (Japan's national ID number). According to the final report, point exchanges made without the members' consent total 643 cases worth 2,955,000 yen (639 Amazon gift code exchanges worth 2,953,000 yen, 2 GMO Points, 1 Dot Money and 1 Eraberu e-GIFT), affecting 453 members, and the company will compensate them in full (credited to accounts when the service resumes on November 18). The cause was an intrusion exploiting a vulnerability in software used on its site; the investigation by a security firm was completed on October 20. The company invalidated all members' passwords on October 7 and plans to resume the service at 11:00 on November 18, when login will change from email address and password to the "1 Account" method, which requires Google-account authentication. This site's take: with birth dates and addresses included, convincing fake messages are easy to make. Change the password on any service that shares your infoQ password, turn on two-step verification for your email account, and do not open links in messages claiming to be infoQ before or after the reopening.

2026-10-06

MrMax app and online store breach (up to about 1.74 million people): names, emails and phone numbers leaked — what members should do

On October 6, 2026, MrMax Co., Ltd., a Japanese discount-store chain, announced that the servers of the MrMax app and online store it runs had been accessed without authorization by a third party, and that part of its members' personal data had leaked. Up to 1,735,154 people registered as members as of October 3, 2026 are affected. The items are member ID, name, email address and phone number (varying with what each member registered). The company says it confirmed that addresses, dates of birth, credit card data, passwords and purchase history did not leak. It noticed suspicious access on the evening of October 3, suspended the service immediately and blocked outside access the same day. The company says a third party misused a function of the software that makes up the service to get into the server. No harm from misuse of the data had been confirmed at the time of the notice. This site's take: expect convincing emails, texts and calls that use your name. Do not open their links, check in the official app or site you open yourself, and never give out passwords or card numbers.

2026-10-06

Osaka Metropolitan University ransomware attack (personal data of about 170,000 people leaked from a contractor's cloud storage): what students, alumni, parents and staff should do

Osaka Metropolitan University in Japan says a large-scale failure hit its virtualization platform in the early hours of October 2, 2026, taking down the campus network, OMU Mail, its websites, and its academic, finance, payroll and library systems. At a press conference on October 5 it said it had concluded the cause was a ransomware attack. Classes were cancelled from October 2 to 8, and in-person classes resumed at all campuses on October 9 (fourth notice). In its fifth notice on October 21, the university said the contractor that builds, operates and maintains its core systems had reported that a device at a company it subcontracts to was hit first. In its sixth notice on November 13, the university set out its findings. Signs show that a large amount of data, including data related to the university, leaked from the subcontractor's device and from cloud storage managed by the contractor. Right after that, the university's systems were accessed without authorization using the legitimate accounts (including system administrator accounts) and passwords that the contractor and subcontractor use for the work. The investigation firm also judged both intrusions to be by the same attacker. According to the contractor's additional report of November 12, the leaked information included important management information of the university (including administrator information for its systems) and personal data of about 170,000 students and staff, such as IDs, names, email addresses and dates of birth. Part of it was highly sensitive: about 1,400 people in total, including bank account numbers (about 20 people), health-related information (about 200), passport images (about 200) and passport numbers (about 1,000). Most of this was data from the system migration work done in fiscal 2021, and it had stayed in the cloud storage after the work was finished. The university says it regards keeping the data for so long, in storage used by many people at the contractor and subcontractor, as a serious problem. It says it has not confirmed a leak of personal data from its own information systems, but cannot rule one out because many systems were encrypted. It plans to contact each affected person individually once they are identified. News reports say about 500 servers stopped and much of the backup data was also encrypted. This site's take: check any message claiming to be from the university on the OMU Entrance page, not through links in emails or texts. If bank or passport data may be involved, watch for contacts that ask for PINs or pose as travel or identity-check procedures. Organizations should not leave migrated data with contractors, and should list the accounts their contractors and subcontractors use.

2026-10-06

Rakuten Drive breach (stored data of 15,382 accounts): what was accessed and what users should do

On October 6, 2026, the cloud storage service Rakuten Drive announced that a third party had illegitimately obtained the credentials of a management account for part of the systems the service uses, accessed the systems, and obtained and viewed information. Affected were the stored data (including photos and documents) of 15,382 accounts between January 29 and September 17, 2026; the account name, display name and profile image URL of 687 accounts on August 27; and, on the same day, the account name, display name, encrypted password, the string added during password encryption and profile image URL of 313 accounts. The service says no secondary damage has been confirmed and that it will notify affected users individually by email or other means. In an August 13 update about suspicious push notifications seen on July 30, the service had said that unauthorized third-party access to stored data had not been confirmed at that time. This site's take: unlike a password, stored files cannot be taken back. Check for a notice, treat any ID documents or contracts you stored as seen, change your password, and do not respond to messages, payment demands or threats claiming to be Rakuten Drive.

2026-10-05

Yakiniku King app breach (about 10.79 million records): names, phone numbers and emails leaked — what members should do

On October 5, 2026, Monogatari Corporation, which runs the Yakiniku King grill-restaurant chain in Japan, announced that a third party had gained unauthorized access to the member-management system of the official Yakiniku King app. Of 10,808,784 app registrations, 10,788,963 records were leaked: member number, name (the name registered in the app), email address and phone number. The company confirmed the unauthorized access on October 2, cut off communications and put defensive measures in place, and confirmed the leak on October 3. Login passwords, dates of birth, gender, postal codes and store-visit history including points were not leaked, and the company does not hold payment data such as credit cards. No publication or misuse of the leaked data has been found. On October 20 the company announced further measures: it said the intermittent unauthorized access by an outside third party began at 9:00 a.m. on October 2, and that in the first half of 2027 it plans to move the 11 official apps run by its group, including Yakiniku King, to a new system that does not hold names or phone numbers. It will keep collecting email addresses. It has reported the matter to the police and is proceeding with its report to the Personal Information Protection Commission. Details of the cause have not been published. This site's take: almost every app member is affected, and the most likely next step is emails, texts and calls posing as Yakiniku King with coupon, point or refund offers. Do not open their links; check in the official app you open yourself, and never enter card details.

2026-10-03

Abahouse data breach: order details may have leaked — how to handle fake refund emails

On October 2, 2026, Abahouse International Co., Ltd. announced that unauthorized access to its internal systems, believed to be by a third party overseas, may have leaked member IDs, names, addresses, phone numbers, email addresses, dates of birth, gender and order details (order date and time, product names, amounts and delivery addresses). Because it cannot fully identify the scope of data taken, the company emailed customers it judged may be affected based on purchase history and other records on October 2. It deletes member data one month after a member leaves, but keeps past order records for a period for legal and accounting reasons, and says it cannot rule out that those orders were accessed; former members received the same email. No count has been announced. Card numbers and security codes are handled by a payment processor, and no leak of them has been confirmed. The breach came to light when several customers reported suspicious refund emails that matched their real orders. In a follow-up on October 9, the company said the intrusion route had been cut off with no further spread confirmed, that it had filed a damage report with the police, and that no reports of financial loss had been received. The scope of data taken and the details of the cause are still being investigated with outside specialists. This site's take: a message that gets your order right is not proof it is genuine. Do not follow links or move to LINE from 'refund' or 'out-of-stock' emails; check your order history in My Page instead.

2026-10-03

If your Japanese driver's license data was leaked: what to do to prevent misuse (credit bureau alerts, reissue, where to get help)

A practical guide for people whose Japanese driver's license image or number was leaked by a company. The license number, name, date of birth and face photo cannot be changed by the holder, and a reissued license keeps the first 11 digits of its number (National Police Agency directive). At the same time, non-face-to-face identity checks for mobile phone and bank contracts are moving from sending document images to reading the card's IC chip (mobile phone online contracts from April 2026; transactions under the Act on Prevention of Transfer of Criminal Proceeds from April 2027, as scheduled). This site's take: there is no way to take leaked data back, so the core of the response is making sure you notice quickly if something is opened in your name. In practice that means registering an identity-fraud alert (honnin shinkoku) with all three Japanese credit bureaus (CIC, JICC and the Japanese Bankers Association's KSC), checking your own credit file, and ignoring messages that pose as the company that leaked the data. Reissuing the license and paid 'data deletion' services are low priority or useless.

2026-10-03

EPARK Relax & Esthe "PeakManager" data breach (about 22.18M records): health notes leaked too — what salon customers should do

EPARK Relax & Esthe Co., Ltd. announced that the database of PeakManager, the booking and customer-management system it provides to salons, was accessed without authorization and customer data was transferred outside. Its first notice (July 31, 2026) gave about 33 million records; after removing duplicates, its second notice (September 24) gave about 22.18 million records, which it says cannot be converted into a number of people. The leaked items are name and its phonetic reading, date of birth, gender, address, phone number, email address and a notes field where salons recorded handover notes for treatments, partly including health conditions and other sensitive personal information. The first notice also said encrypted passwords may have leaked and asked customers to change them. This site's take: PeakManager is each salon's own customer ledger, so people who never used EPARK can still be affected if they gave a salon their name or contact details. Do not respond to messages claiming to be from a salon or the company, and change your My Page password and anywhere you reused it.

2026-10-03

Lashinbang data breach: ID document numbers and payout bank details may have leaked (no ID images) — what sellers should do

On October 1, 2026, Lashinbang Co., Ltd. announced that unauthorized access to a service it operates, between September 14 and 16, 2026, may have leaked names, addresses, phone numbers, email addresses, dates of birth and occupations, along with the type and number of identity documents, the bank name, branch, account number and account holder entered when applying for a buyback (when customers sell items to the shop), images of buyback consent forms, and buyback and order details. The company says no credit card information or passwords leaked and that it does not collect My Number (Japan's individual number). In an addendum on October 9, it added that images of identity documents, including driver's licences, did not leak. The notice also gained a section saying the people affected are those who received an individual email from the company. As of October 10, 2026, the count and the cause have not been announced. This site's take: an account number and holder name alone cannot be used to withdraw money, but do not respond to contacts that use your account details, ID number or real buyback details to look genuine. Never give anyone a PIN, login or authentication code, and if your ID document number leaked, consider a self-declaration with Japan's credit bureaus.

2026-10-03

Murauchi.com data breach (7.7 million records): names, addresses and phone numbers leaked — past customers should watch for scam calls and mail

On September 15, 2026, Murauchi.com Co., Ltd. announced that unauthorized access, which began with the exploitation of a vulnerability in part of its web system, led to 7,716,811 records of customer personal data being taken out (the first notice was on July 24). The data includes names, addresses and phone numbers, plus email addresses, dates of birth and gender for some people. Card and other payment data and login IDs and passwords are kept in separate systems and were not affected. The company has not said how many years of data were involved or whether former members are included. This site's take: the main risk is that real names, home addresses and phone numbers leaked together. Assume you may be affected even if you bought from the shop only once, years ago, and never hand over personal data or money in response to calls, mail or texts claiming to be from the company, an online mall or a card issuer.

2026-10-03

Seicomart app breach (about 575,000 members): names, addresses and birth dates viewed — what members should do

On September 29, 2026, Seicomart Co., Ltd., which runs the Seicomart convenience-store chain in Japan, announced that a third party had gained unauthorized access to the server holding member data by way of the server behind its Seicomart smartphone app. Its fourth notice on October 5 said the affected accounts are 574,647 of the Club members who have registered with the app, and that people who left the Club Card program by September 24 are not included. The items viewed are surname and given name, gender, date of birth, address, phone number, email address, and the dates the person joined and left the Club Card program. Password data and purchase history were not leaked, and the company does not hold credit card data. From October 5 the company is telling every app member, through the app's notices, whether they are affected. It has ended the app and web functions for new sign-ups, viewing and changing member details, and changing registered cards; requests now go through stores or a form. The cause has not been disclosed. This site's take: what was exposed is a set of personal details that cannot be changed, and the most likely next step is convincing emails, texts and calls that pose as the company. Check the app's notices to see whether you are affected, do not follow links or instructions in such messages, and stop using your date of birth as a PIN or as an answer to identity checks.

2026-10-03

E-store ShopServe data breach (final report: about 23.36 million people): what buyers, shop owners and affiliates should do

In its final report of October 16, 2026, E-store Co., Ltd. said a third party exploited a vulnerability in an application on the servers of ShopServe, its service for building online shops, and sent database contents out between May 21 and August 1, 2026. About 23,356,000 people are affected (buyers and members, shop operators and affiliates combined; an approximate figure after removing duplicates), of whom about 2,096,900 had part of their card data included. 7,858 shops are affected (including current and former ShopServe shops). The leak includes buyers' names, addresses, phone numbers, email addresses and workplaces; member IDs and encrypted passwords; cardholder names, the first 6 and last 4 card digits and expiry dates; and the credentials of shops and affiliates. Full card numbers and security codes were not held and were not affected. The final report corrects the second report: shops' mail system and FTP IDs and passwords, and bank account details of the accounts E-store transfers money to (payout accounts), were confirmed not to have leaked. No secondary damage had been reported. This site's take: most buyers shopped on each store's own site without ever hearing the name ShopServe. Even if you cannot tell which shop it was, treat messages that quote your real order details or the last four digits of your card with suspicion, check your card statements, and change reused passwords. Shop owners and affiliates should change their admin or affiliate passwords and turn on two-step verification.

2026-10-03

TEMAIRAZU Unauthorized Access (2026): Guest and Hotel Guidance

On September 28, 2026, Temairazu, Inc. announced unauthorized access to its TEMAIRAZU Series, a system hotels and ryokan use to manage bookings from many sources in one place. From late at night on September 21, guests of properties using the system began receiving suspicious messages via messaging apps such as WhatsApp, by email and by SMS. The messages appeared to know booking details and, under pretexts such as advance check-in or keeping a reservation valid, pushed recipients to external websites to enter card details or pay. In its second report of October 7 (English version October 8), the company listed the information that may have been viewed or obtained by a third party: guest names, telephone numbers, email addresses, accommodation property names, check-in dates, check-out dates and accommodation charges. It does not retain credit card information or login credentials for booking sites. In a timely disclosure to investors on October 9, it put the number of people whose booking information is involved at up to about 4.45 million and said it had commissioned an external security firm to investigate. In its final report of November 20 (the firm's final report is dated November 17), the company revised the number of people whose information may have been viewed or obtained by a third party to up to about 1 million; it says this does not mean all of their information was confirmed to have been viewed or obtained. According to notices from hotels using the system, the cause was a security problem in part of an installed product the company provided in the past, fixed on September 26. The final report says a third party abused part of the application's functions (a probing attempt on August 26, the intrusion on September 21), that no trace of administrator privileges being obtained and no malicious program planted for re-entry was found, and that the TEMAIRAZU admin-screen credentials of some hotels may have been obtained and have been changed or invalidated. This site's take: people who booked through travel sites may be affected too. If a message claiming to be your hotel asks you to re-enter card details or pay, refuse even if the details are correct, and check through the booking site's official app or the phone number on the hotel's official website.

2026-10-03

Yamato and Sagawa Data Breaches (2026): Affected Users and Response

Yamato Transport found unauthorized access to its Kuroneko deferred-payment service on September 28, 2026, and Sagawa Express found unauthorized access to its parcel tracking service on September 30. On October 1-2, both said personal data may have leaked. These are separate incidents, and neither company mentions a connection. In its fourth notice on October 16, Yamato said data had been taken: about 5.26 million records of deferred-payment users (name, address, phone number, email address, item details and more, from October 1, 2018 to September 28, 2026), about 50,000 records of delivery-address information of some users, and about 4,100 records of participating shops. Billing amounts, outstanding balances and employee names were not found to have been taken. In its fifth notice on October 23, Sagawa said names, addresses and phone numbers of senders and recipients of parcels it handled from June 21 to September 30, 2026 (about 100 days), among other data, may have leaked, and gave the maximum count as about 53.23 million records (duplicates included; not the number of people). Parcels sent with handwritten waybills are not included. Neither breach includes credit card data or passwords. Yamato restarted the deferred-payment service on October 9 and extended payment deadlines by 17 days; Sagawa restarted its parcel tracking service on October 23. As its sixth notice of November 13 announced, it restarted the tracking API and two delivery-address change services on Monday, November 16, according to its FAQ updated that day. The FAQ lists four services as still stopped (round-trip delivery booking, golf round-trip delivery booking, the product return-and-refund service and Kaishu-kun); online booking for Hikyaku parcel delivery, which the sixth notice listed, is not in that list, and the FAQ does not say it restarted. This site's take: with Sagawa, you can be affected just by having received a parcel, even if you never used the company yourself. Assume fake missed-delivery notices and payment demands may now carry your real name and address, the fact that you received a parcel, or what you bought. Do not open links in such messages; check in the official app or in the order history of the shop you bought from.

2026-10-03

Yellow Hat data breach (up to about 1.8 million people): names, phone numbers and emails may have leaked — what members should do

On August 28, 2026, Yellow Hat Ltd., a Japanese car-parts and car-service retailer, announced that its online work reservation system, used to book jobs at its stores, had been attacked by a malicious program, and that the names, phone numbers, email addresses and member numbers of up to 1,801,499 people may have leaked. The company detected the attack on the morning of August 18, cut the system off from outside connections and shut it down. Credit card data, passwords and vehicle information are not held in this system, so the company says they were not leaked. Separately, in April 2026, the group company 2rinkan Yellow Hat had a different breach that exposed data on about 3.18 million people, including app passwords. This site's take: what may have leaked is exactly the data needed to contact you directly. Do not reply to calls, texts or emails about bookings, inspections or apologies; check through the official website or the store instead.

2026-09-30

CAMPFIRE Unauthorized Access: 225,846 Unique User Records at Risk — Actions for Users and Developers

According to CAMPFIRE, a GitHub credential issued by an employee was misused by a third party; information visible on GitHub was then used to obtain credentials for a cloud environment the company uses for internal business operations, and part of its management area was accessed. Names, addresses, phone numbers, email addresses and bank account details in 225,846 unique affected-user records (project owners, supporters, partners) may have leaked; credit card data was not involved. The service platform runs in a separate environment and no misuse or tampering was found there. Users should watch for messages about refunds or payout account confirmation and check bank statements. Developers and operators get two lessons. Customer data also lives in internal business environments even when production is well protected. And work tokens can end up on machines the company doesn't manage, so organization settings must limit how long a token stays valid and what it can access.

2026-09-30

Medica Shuppan Ransomware Attack (About 641,000 People): What Medical Readers, Authors and Publishers Should Do

According to Medica Shuppan Co., Ltd., it detected a system failure on March 13, 2026 that turned out to be unauthorized access involving ransomware. Its May 13 investigation report says the starting point was a third party entering the internal network with legitimate account credentials. No definitive evidence was found that personal data was taken out, but the possibility cannot be fully ruled out, so data of about 641,000 people (may include duplicates) is treated as 'at risk of leakage'. The data includes readers' names, contact details and email addresses, authors' bank account numbers and employees' HR records. The company does not hold credit card data. Emails impersonating the company have also been seen. This site's take: a specialist publisher's customer list is a list of medical professionals with their workplaces, so check any message about study materials, seminars, academic societies or manuscript fees on the official site you open yourself, not via a link. Authors should watch for messages that mention their account number to seem genuine and then ask for a PIN or online banking details.

2026-09-30

Cariteco (Meitetsu Kyosho) Ransomware Attack: Possible Driver's Licence Data Leak and What Members Should Do

On July 2, 2026, Meitetsu Kyosho Co., Ltd. disclosed unauthorized access to its servers and a system outage detected on June 23, saying an investigation found traces of unauthorized access by ransomware. On August 4 it said it could not rule out a leak of the information members wrote on their application forms for its car-sharing service Cariteco — name, address, date of birth, phone number, email address, driver's license information and, for some members, credit card data — covering both current and former members. No count has been disclosed, and the company says no leak or misuse has been confirmed. This site's take: license data cannot be changed, so, as in the Times Car case, register a fraud alert with Japan's three credit bureaus and check your credit file. Two points are specific to this case: with ransomware, a possible leak can come to light only after the service has been restored; and some of the company's individual notices were undeliverable. Former members who have moved should contact the company rather than wait for a letter.

2026-09-30

APORITO Online Store (RIZAP) Possible Card Data Leak: What Customers and Online Shops Should Do

According to RIZAP Co., Ltd., a third party planted a malicious script on its APORITO Online Store, and the names, addresses, phone numbers and email addresses — plus card numbers, expiry dates and security codes — of people who placed an order or entered information between May 1 and August 5, 2026 may have been sent outside. The company found a suspicious outbound-transmission program on August 5 and closed the store that day; as of August 18 the store remained closed and the investigation continued. It says no misuse or actual leak has been confirmed. This site's take: with the security code in scope, watching statements is not enough; ask your card issuer to replace the number. The lesson for e-commerce operators is that not storing card data ('non-retention') does not stop a malicious program from being planted in the input page. On top of the five vulnerability measures required by Japan's Credit Card Security Guidelines, have a way to detect changes to your payment page.

2026-09-29

Times Car data breach (6,628,007 records with names and addresses, traces of about 1.46M ID-document images being sent out): checking My Page and what members and former members should do

In its fifth notice on October 23, 2026, Times Mobility Co., Ltd. said the outside forensic investigation had ended and published final counts. In the Times Car web system, traces of attacker access and external transmission were found for 6,628,007 records of name, address, date of birth, phone number, email address and driver's license information. Of the identity-document images, which were stored encrypted, 1,464,800 showed traces of being sent out (the company had earlier said about 1.6 million might have leaked) and 891,602 were accessed with no trace of being sent out. Hashed passwords were sent out in 4 cases. In the related Times Club web system, where unauthorized access was also found, 19,510 Times Club card numbers, 135,436 linked-service IDs and 28 credit card last-four-digit records, among others, showed traces of being sent out (the company does not hold full card numbers or security codes). The cause was the exploitation of a vulnerability in the web system. The company will give a payment worth 3,000 yen to people whose images were sent out (details and method still being decided), and since 17:00 on October 23 has shown each person's leaked items on My Page. This site's take: first check your own items on My Page. If your document images were sent out, register fraud alerts with the credit bureaus and check your credit file; everyone should ignore contacts posing as the company. Former members can inquire through a dedicated form.

2026-09-19

The Gyazo Breach (About 23.62 Million Records): User Data and Image Metadata Leaked — What Users Should Do Today

A vulnerability in Gyazo's image upload server was exploited, leaking about 23.62 million user records and metadata on about 490 million images, mostly uploaded before January 2019. This site's view: change your password and stop reusing it — that is the minimum. What is easy to miss is that the leak covers information about the images rather than the images themselves: text read from screenshots (OCR), photo location data and upload IP addresses. If a screenshot showed a secret, revoke that secret.

2026-09-11

Japan's Four Major 2026 Data Breaches (KDDI, Aflac, Digital Agency, Sakura): Different Ways In, the Same Fix — Better Detection

KDDI (ISP mail platform, about 12.23 million people), Aflac Japan (about 4.4 million), Japan's Digital Agency (about 246,000 records) and Sakura Internet (up to about 1.36 million accounts). The ways in had nothing in common, yet KDDI, Aflac and Sakura all listed stronger detection in their remediation plans, and the Digital Agency case was caught through an anomaly in volume. This site's view: stop assuming intrusions can be fully prevented, and invest in watching volume and time, the only signals left when an attack looks like legitimate use.

2026-09-11

VPN Appliances Are the Main Way In for Ransomware: Remote Access Defense After Japan's Digital Agency Breach

A VPN appliance connects the internet to an organisation's internal network, and in Japan it is how attackers got in in roughly two thirds of ransomware cases where the route is known. The Digital Agency's GSS incident followed the same shape: in through a VPN vulnerability, then a maintenance operator's account used to reach a large volume of files. This site's view: only keep a VPN appliance if you can keep patching it, and defend it with three things: patch speed, narrow privileges after an intrusion, and detecting bulk access.

2026-09-04

How 2026 Breaches in Japan Got In: More Through Valid Credentials Than Vulnerabilities (A Cross-Case Analysis)

Classified by entry path, the major Japanese incidents disclosed in August 2026 skew toward credential-led intrusion rather than exploited vulnerabilities. The shared trait: the victim's own servers were untouched and the way in was a legitimate account on an outside service. This site's conclusion: flawless vulnerability management stops none of this, so the focus has to shift toward credential lifetime and scope, and an inventory of the vendors and SaaS that can reach your data.

2026-08-18

When Your Web Hosting Provider Is Breached: What Customers Should Do

A provider-side compromise cannot be blocked by customer settings, so the defense shifts from prevention to limiting how much you can lose. The 10 September investigation results established the part that matters most: unauthorized access to the sales management system occurred between April 2023 and March 2026, the affected hosting accounts rose from 583 to 951, and some initial passwords were not hashed. This site's view: treat everything on shared hosting as readable, push secrets, credentials and backups outside the provider, and change any initial password you are still using today.

Critical2026-07-18

Tsurugi Handa Hospital ransomware (2021) — an unpatched VPN CVE and backups encrypted along with production

The way in, per the expert committee's report, was an internet-facing VPN device left unpatched against a known vulnerability (CVE-2018-13379), reachable with leaked credentials. Short passwords, no account lockout, and users holding admin rights made it easy to spread to other machines in the hospital (lateral movement). Decisively, the primary system and its backup were on the same network and both were encrypted. A backup that isn't isolated and offline can't be relied on for recovery. EMR recovery took about two months. Defend by patching internet-facing VPNs fast, revoking leaked/reused credentials, and keeping isolated, offline, 3-2-1 backups.

Critical2026-07-18

Osaka General Medical Center ransomware (2022) — a contractor's VPN as the way in, and hospital BCP

The way in was not the hospital itself but a meal-service contractor's remote-maintenance VPN device, which was unpatched and reachable using leaked credentials, the investigation committee found. Because the hospital and contractor were constantly connected, and because servers/PCs shared passwords, users held broad admin rights, EMR servers lacked antivirus, and the network wasn't segmented, the encryption spread across the EMR system. Outpatient care, surgery, and emergency intake were restricted; full recovery took over two months. Defend by treating contractor links as your own attack surface: patch internet-facing VPNs, end credential reuse, least privilege, segment, and build a medical BCP (paper fallback, tested restore).

High2026-07-07

7pay fraud (2019): the disclosed cause assessment and account protections

7pay suffered unauthorized account access in July 2019. The August 1 company statement assessed credential stuffing as likely and recorded 808 affected people and ¥38,615,473 as of July 31 at 17:00, including unauthorized top-ups and use. It had not found cases where reset functions were a direct cause. Separate that assessment from general advice on authentication, recovery and alerts.

Critical2026-07-07

Benesse Data Leak (2014) — Why an Insider Couldn't Be Stopped, and the Least-Privilege Defense

A dispatched systems engineer at an outsourced group company used legitimately granted database access to copy customer data in bulk, transfer it to a personal smartphone, and sell it to data brokers. The monitoring software blocked writes to USB storage but did not block transfer to a smartphone (MTP). Up to ~35 million records leaked. Defend by minimizing privilege (least privilege / need-to-know), closing every exfiltration path with DLP, detecting bulk access, and extending oversight all the way to contractors and sub-contractors.

High2026-07-07

Capcom Ransomware (2020) — Why an Old VPN Device Was the Way In, and the Double-Extortion Defense

The way in was an old backup VPN device that had been left running at a North American subsidiary after newer units replaced it. From there the network was breached, data was stolen, and then ransomware encrypted systems (double extortion). Up to ~390,000 people's personal data was potentially exposed (no payment-card data). Capcom refused to pay, restored from backup, and disclosed transparently. Defend by decommissioning unused gear, patching edge devices, and covering both theft and encryption (segmentation, detection, backups).

Critical2026-07-07

Coincheck NEM Heist (2018) — How ~$530M Was Stolen, and the Key-Management Defense

The entry point was reported to be spear-phishing / malware aimed at employees, which stole the private key of an internet-connected hot wallet; ~523 million XEM (~$530M at the time) was then moved out in a single transfer. The core failure was keeping a huge, instantly-spendable balance in an online wallet with no multisig, so a single stolen key moved almost everything. Defend by keeping important keys offline or in a dedicated key store (HSM/KMS), minimizing the hot balance, removing single points of failure (multi-approval), and detecting and stopping abnormal bulk operations.

Critical2026-07-07

KADOKAWA / Niconico Ransomware (2024) — Why It Spread Company-Wide, and Network Segmentation & BCP

The way in was described as phishing that stole an employee's credentials; from there the internal network was breached and ransomware ran, taking down many of the group's services (including Niconico) for months and leaking ~250,000 people's data. Reporting and analysis attribute the company-wide spread to systems of very different criticality sharing the same network, reportedly with too little segmentation. Defend by segmenting the network by criticality, using phishing-resistant authentication, and preparing business continuity (BCP) and recovery.

High2026-07-07

Takufile-bin Data Leak (2019) — Why Plaintext Password Storage Is Fatal, and the Hashing Defense

A server vulnerability was exploited for unauthorized access, and ~4.8 million records (names, emails, login passwords, dates of birth, including withdrawn customers) leaked. The decisive failure was that login passwords were stored unencrypted, in plaintext. Once leaked, they were immediately usable and could be used for account takeover on other sites where people reused them. Defend by storing passwords as a one-way salted hash, holding no data you don't need, patching vulnerabilities, and preparing for reuse (2FA).