Yaamlabs

Threat intel

Nitori breach may expose 37.62 million customer records

Japanese retailer Nitori says an intruder reached a server holding up to 37.62 million personal records. No passwords or cards, but plenty for phishing.

Nitori Holdings, one of Japan's largest home-furnishings and furniture retailers, says that up to about 37.62 million records of personal information held on its servers may have been exposed to an outside intruder. It confirmed the unauthorised access on November 6, 2026, blocked it, and announced the incident three days later. A third-party investigation placed the intrusion between the middle and the end of October, so the attacker was likely inside for several weeks before anyone noticed.

The records cover people who ordered through Nitori Net and official Nitori shops on online marketplaces, along with some corporate accounts. Exposed fields reportedly include names, email addresses, postal addresses, phone numbers, dates of birth and membership details. Nitori says login passwords and payment card data were not on the affected server and were not taken. That is worth having, but it does not make the breach harmless: a real name, address and date of birth is enough to build convincing fraud, and Nitori has already warned customers to expect phishing that uses exactly this data.

What we know and what we do not

Nitori describes the figure as "up to 37.62 million records," an upper bound that may fall as the investigation cross-checks duplicate entries. It is not clear whether that number counts individual people or individual data records, and the company says the count of distinct customers is still being worked out. So read 37.62 million as the ceiling on records at risk, not as a confirmed number of victims.

The dates are firmer. Nitori detected and blocked the unauthorised access on November 6, 2026, external specialists reviewed the logs and traced possible access to the mid-to-late October window, and the company published its notice on November 9. The investigation into scope and any secondary damage is continuing.

The exposed fields differ by customer. For individual members, reporting lists the membership number, name with its furigana reading, email address, postal address, phone number, date of birth and gender. For corporate members, it lists the company name, department and representative names, the corporate address and phone number, and contact person details. Passwords and card numbers were held elsewhere and, Nitori says, were not reached.

The one thing nobody has published is how the attacker got in. Reporting says the intruder reached an internal network server, but no vulnerability, exploited product or access route has been named, and Nitori has not said whether stolen credentials or a software flaw was the cause. There is no CVE to patch and no single technique to block here. Anyone presenting a neat "the attackers did X, so do Y" story about this breach is guessing, so the honest lessons are about how the data was held and how the response is handled rather than about the break-in itself.

Why a breach like this matters even without stolen passwords

A leaked email address with no password still lets an attacker write a message that quotes your real name, home address, phone number and birthday. That specificity is what turns a generic scam into a believable "there is a problem with your Nitori order" or "confirm your delivery address" mail. Nitori has told customers it will never ask for passwords, card numbers or PINs by email or phone, which is the line to hold onto when a message asks for any of them.

The same fields feed problems beyond phishing. A name, address and date of birth is the raw material for opening accounts in someone else's name and for talking a support desk at another company into a password reset. And if a customer used their Nitori email and password on other sites, the leaked email tells an attacker which accounts are worth trying with passwords pulled from older breaches. The absence of passwords in this leak limits the direct damage; it does not remove the identity risk that the rest of the data carries.

What to do

If your details might be in this breach:

  • Treat any message that mentions Nitori with suspicion for the next few months, especially one that quotes your real name, address or birthday to seem genuine. Do not click links or open attachments in it.
  • Reach Nitori only through its official site or customer desk, never through a link or phone number supplied in an unexpected message. Nitori will not ask for a password, card number or PIN by email or phone.
  • Turn on multi-factor authentication (MFA, a second login step such as an app code on top of your password) for the email account tied to your Nitori membership and for any bank or shopping account that could be reached from it.
  • If you reused the Nitori email and password anywhere else, change that password on those other accounts now and stop reusing it. The email alone points attackers at your other logins.

If you run a large store of customer records, this breach is a prompt to check your own setup before you are the one writing the notice:

  • Put the server holding the customer database on its own network segment and watch it closely. Alert on bulk reads and exports, and on an application account suddenly pulling far more rows than its normal daily pattern. A weeks-long intrusion that touches tens of millions of records should trip something.
  • Hold less, and hold it for less time. Fields like date of birth and gender should exist only where a real process needs them, and old order records should age out on a schedule rather than sitting in the live database for years.
  • Keep passwords and card data off the systems that hold everything else, as Nitori's split did here. That separation is why this leak did not include credentials.
  • Write the breach-response and customer-warning playbook before you need it: who decides, who reports to the regulator and police, how affected people are contacted, and the phishing warning you will send so customers know what a real message from you looks like.

A hard year for customer data in Japan

Nitori is not an outlier. Japan's National Police Agency counted 123 ransomware cases in the first half of 2026, its highest half-year total since it began keeping the figure, and reporting through October described a run of disclosures at well-known Japanese companies. Nitori itself had a smaller incident in September 2022, when attackers used email and password pairs stolen from other services to log into about 132,000 app accounts, a reminder that both reused passwords and large central data stores keep drawing attackers. Holding less personal data, for less time, is the one defence that keeps working whatever the entry point turns out to be.

If you keep a large customer database, the practical work is in the detection and segmentation above and in a response plan you have actually rehearsed. That is the ground our security operations and compliance and audit readiness work covers. Open the chat and Yaali, our AI agent, will pass your question to the engineer who would do the work.


Sources: SC World on the Nitori breach, The Star: 37.62 million Nitori records at risk, BleepingComputer on the Nitori breach, SmartScope on the Nitori notice, Mynavi on the 2022 Nitori app credential-stuffing attack, Nippon.com on Japan's record 2026 ransomware cases.

Back to the blog, or read this post on the full site.