KEEP IN TOUCH
Subscribe to our mailing list to get free tips on Data Protection and Cybersecurity updates weekly!
A large customer database can be one of a retailer’s most valuable business assets. It can also become one of its greatest cybersecurity liabilities when attackers gain access.
Japanese furniture and home furnishings retailer Nitori disclosed on 9 November 2026 that up to 37.62 million records of personal information held on its servers may have been leaked following unauthorised access to one of its systems. The Nitori data breach potentially affects individual customers, corporate members and people who placed orders through its online channels.
The company detected the intrusion on 6 November and blocked the attacker’s access. Subsequent analysis indicated that unauthorised access may have occurred from mid to late October, showing why detection speed can be just as important as the eventual containment of a breach.
When organisations discuss a data breach, attention naturally falls on how many records were affected. The time between initial compromise and detection deserves equal scrutiny.
Nitori said its investigation found evidence suggesting third-party access may have occurred before the incident was discovered on 6 November. The company is continuing to investigate the precise timeline, entry route and affected scope.
Even a relatively short period of undetected access can give an attacker time to explore systems, identify valuable databases and extract information. This makes monitoring important not simply for detecting known malware, but also for identifying unusual access patterns, unexpected data transfers or abnormal account behaviour.
For organisations, the lesson is that preventing every intrusion may be unrealistic. Detecting suspicious activity quickly can materially reduce how much an attacker is able to accomplish after gaining access.
The scale of the Nitori data breach is striking, but the affected data differs depending on the customer relationship.
For individual members and purchasers, potentially exposed information includes membership numbers, names, email addresses, postal addresses, telephone numbers, dates of birth and gender. Corporate records may include company and department names alongside representatives’ and contact persons’ details. Order information from Nitori’s online shops may also have been accessed.
Importantly, Nitori stated that login passwords and credit card information were not included in the information potentially leaked.
That distinction reduces some immediate risks, but it does not make the incident harmless. A breach does not need to contain payment card numbers or passwords to create meaningful opportunities for fraud.
One of the most significant secondary risks following the Nitori data breach is targeted phishing.
Names, contact information, membership details and purchasing information can give attackers context that makes fraudulent messages appear credible. Instead of sending a generic phishing email, a criminal could potentially impersonate a retailer, delivery company or e-commerce platform while referring to information that makes the communication feel familiar.
Nitori specifically warned customers that potentially leaked information could be misused for impersonation emails, phishing scams or suspicious telephone calls. It also reminded customers that it would not request passwords, credit card numbers or PINs through email or telephone conversations.
This demonstrates why organisations need to consider secondary harm when assessing a data breach. The immediate compromise may be over, while opportunities for social engineering can remain for months or longer.
Large retailers collect information for legitimate reasons, including fulfilment, membership programmes, customer service and e-commerce. Over time, however, those separate activities can create substantial repositories of personal data.
The cybersecurity concern is not simply each individual field. It is what those fields reveal when combined. A name paired with an address, telephone number, date of birth and purchase history provides considerably more context than an email address alone.
This makes data minimisation relevant to cybersecurity as well as privacy. Organisations should periodically consider whether historical information still needs to be retained, whether different datasets need to remain connected and whether access privileges remain appropriate.
A smaller and better-segmented data environment cannot eliminate cyber risk, but it can reduce the amount of information available if a system is eventually compromised.
Nitori said it blocked the attacker’s access, addressed identified vulnerabilities and strengthened its monitoring. It is also working with external specialists to determine the cause, intrusion route, impact and whether secondary harm occurred.
Those actions highlight an important difference between incident containment and security assurance. Closing the known entry route prevents the attacker from continuing to use that particular path. It does not automatically prove that other weaknesses are absent.
Following a significant data breach, organisations should use findings from forensic investigation to examine similar systems, access controls, authentication mechanisms and privileges elsewhere in the environment.
Vulnerability assessment and penetration testing can complement this process by looking beyond the vulnerability already discovered and identifying other attack paths before another threat actor finds them.
Nitori has reported the incident to Japan’s Personal Information Protection Commission, police and other relevant authorities. The company also said affected customers would be contacted by email or post.
Communication matters because customers need practical information about what was exposed and what suspicious activity they should watch for.
Organisations should therefore prepare breach communications before an incident occurs. Cybersecurity teams may focus on containment and forensic work, while management and privacy personnel need to determine what customers, regulators and other stakeholders should be told.
Clear responsibilities reduce the risk of confusion when decisions must be made quickly.
The Nitori data breach demonstrates why organisations handling large quantities of customer information need both preventive cybersecurity testing and established data protection governance.
Privacy Ninja’s Vulnerability Assessment and Penetration Testing services help organisations identify exploitable weaknesses in applications and systems before attackers can take advantage of them. Testing can also provide practical visibility into attack paths that routine security monitoring may not reveal.
Our DPO-as-a-Service supports organisations with their ongoing PDPA responsibilities, providing a dedicated data protection contact, maintaining essential policies and practices, and helping coordinate the data protection aspects of incidents involving personal information.
Combining technical assurance with clear governance helps organisations prepare not only to prevent breaches, but also to respond effectively when prevention is not enough.
The Nitori data breach stands out because of its potential scale. Up to 37.62 million personal information records may have been exposed, and investigations into the precise extent and cause remain ongoing.
Yet the wider lesson is not simply about record numbers. Customer information that appears ordinary in isolation can become highly useful for phishing and impersonation when combined. An intrusion that remains undetected can also give an attacker valuable time inside an environment.
For organisations, effective data breach preparation therefore requires more than blocking attacks at the perimeter. Strong monitoring, appropriate access controls, data minimisation, vulnerability testing and prepared incident procedures all contribute to reducing both the likelihood and impact of a compromise.
The strongest response to a breach is not merely closing the door the attacker used. It is understanding why that door was open, determining what happened while access was available and checking whether another route remains.