Up to 37.62 million
Nitori Holdings, a major Japanese home furnishings retailer, has disclosed a significant data breach that could affect as many as 37.62 million customers. An investigation confirmed that an unauthorized third party gained access to company systems between mid- and late October 2026. The compromised information includes the email and home addresses of Nitori Group members and online store customers. While the company has assured that sensitive financial data was not exposed, the sheer scale of the breach creates a substantial risk of follow-on phishing and social engineering attacks against the affected individuals.
The breach was first confirmed on November 6, 2026, following a third-party investigation into suspicious activity. The attackers managed to gain unauthorized access to a database containing customer records. The initial access vector for the breach has not been disclosed, but such incidents often result from phishing attacks against employees, exploitation of a web application vulnerability, or the compromise of a third-party service provider.
The primary data types exposed were customer email addresses and physical home addresses. The loss of this combination of data is particularly concerning, as it enables threat actors to craft highly convincing and targeted phishing campaigns, both digital (email) and physical (malicious mailings).
Without details on the initial vector, we can surmise common attack paths for large retail breaches:
T1506 - SQL Injection) or a flaw in an e-commerce platform plugin, to gain access to the underlying customer database.T1566 - Phishing), allowing the attacker to log in and exfiltrate the data.T1567 - Exfiltration Over Web Service).For the 37.62 million affected customers, the primary risk is being targeted by sophisticated fraud schemes. Attackers can use the stolen name, email, and home address to create personalized phishing emails that appear to be legitimate communications from Nitori or other trusted brands. These emails could trick victims into revealing more sensitive information, such as passwords or financial details.
For Nitori Holdings, the breach represents a major blow to customer trust and brand reputation. The company will incur significant costs related to the investigation, customer notification, and potential regulatory fines under Japan's Act on the Protection of Personal Information (APPI). The incident also highlights the ongoing trend of large-scale attacks targeting customer data held by major retailers.
Organizations can hunt for similar breach activity using the following indicators:
Database Audit Logs' OR 1=1; --Inbound Traffic Filtering (D3-ITF).User Behavior Analysis.Use a Web Application Firewall (WAF) to detect and block common web attacks like SQL injection.
Implement Database Activity Monitoring (DAM) to audit and alert on unusual access to sensitive customer data.
Train employees to prevent credential compromise via phishing, which is a common precursor to large-scale data breaches.
To defend against web application attacks that often lead to retail data breaches, Nitori and other e-commerce companies must deploy a properly configured Web Application Firewall (WAF). The WAF should be placed in front of all online store web servers to inspect incoming HTTP/S traffic for malicious patterns. It should be configured with rulesets to block common attacks like SQL Injection (SQLi) and Cross-Site Scripting (XSS). This provides a critical layer of defense by preventing attackers from exploiting vulnerabilities in the website's code to access the backend customer database. Regular tuning of the WAF is necessary to minimize false positives while blocking real threats.
Detecting the exfiltration of 37 million records requires analyzing how resources like databases are accessed. By implementing a Database Activity Monitoring (DAM) or User and Entity Behavior Analytics (UEBA) solution, an organization can establish a baseline for normal database access. The system would learn that a typical web transaction reads one or two customer records, while an administrator might query a few dozen. An alert would be triggered if a single account—be it a service account or a user account—suddenly queries and exports millions of rows from the customer table. This deviation from normal access patterns is a strong indicator of a breach in progress and can enable security teams to intervene before the data leaves the network.
Unauthorized access to Nitori's systems occurs over a period in mid- to late October.
Nitori confirms the data breach following a third-party investigation.
Nitori Holdings publicly discloses the data breach.

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.
CyberNetSec.io uses automation to assist source monitoring, deduplication, observable extraction, and structured intelligence generation. Published analysis follows human-defined editorial standards and adds defensive context including MITRE ATT&CK, D3FEND, STIX, and Sigma where applicable. Read our editorial policy.
Help others stay informed about cybersecurity threats
Every tactic, technique, and sub-technique used in this threat has been identified and mapped to the MITRE ATT&CK framework for consistent, actionable threat language.
Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.
Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.
Structured threat data is packaged as a STIX 2.1 bundle and can be visualized as an interactive graph — relationships between actors, malware, techniques, and indicators.
Sigma detection rules are derived from the threat techniques in this article and can be converted for deployment across any major SIEM or EDR platform.