What went wrong today, on the record
Thursday, November 12, 2026 · UTC
Recalls and Failures

Japan's Nitori says up to 37.62 million customer records may have leaked

The intruder was inside for about three weeks before detection. Addresses and emails are exposed. Passwords and card numbers are not, the company says.

Failure Analyst
References:
Share on X
Stands on 14 placed sources from 2 publishers.
Nitori Holdings said up to 37.62 million customer records may have leaked.[1] Nitori is a major Japanese furniture and home accessories retailer.[2] Unauthorised access to its systems was the cause.[3] Three weeks inside Nitori detected the unauthorised access on 6 November.[4] The attacker likely had access from the middle of October.[5] That is about three weeks between entry and discovery. The company blocked the access once it was found.[6] What was exposed The exposed data includes customers' email and home addresses.[7] Login passwords and credit card information were not compromised.[8] What customers face An email address joined to a home address is enough to write a convincing fake message. Nitori warned customers of possible phishing and scam attempts.[9] It will contact those affected by mail or email.[10] It has notified the Japanese authorities.[11] A second Japanese leak the same day The same report carried another disclosure. Sega reported that around 2.2 million customer email addresses were leaked.[12] That leak came from a compromised system at a third-party contractor.[13] No fraudulent use of the Sega data has been confirmed.[14]
Proof14 sources · 2 publishers · signed
What this stands on
  1. Nitori Holdings stated up to 37.62 million customer records may have leaked. · thestar.com.myMalaysia
  2. Nitori is a major Japanese furniture and home accessories retailer. · bleepingcomputer.com
  3. Unauthorised access caused the possible Nitori customer record leak. · thestar.com.myMalaysia
  4. Nitori detected unauthorized system access on November 6 2026. · bleepingcomputer.com
  5. The attacker likely had system access since mid-October 2026. · bleepingcomputer.com
  6. Nitori blocked the unauthorized access after detection. · bleepingcomputer.com
  7. Exposed Nitori data includes customer email and home addresses. · thestar.com.myMalaysia
  8. Nitori login passwords and credit card information were not compromised. · thestar.com.myMalaysia
  9. Nitori warned customers of possible phishing and scam attempts. · bleepingcomputer.com
  10. Nitori will contact affected customers via mail or email. · thestar.com.myMalaysia
  11. Nitori notified Japanese authorities about the incident. · bleepingcomputer.com
  12. Sega reported around 2.2 million customer email addresses were leaked. · thestar.com.myMalaysia
  13. The Sega leak came from a compromised third party contractor system. · thestar.com.myMalaysia
  14. No fraudulent use of Sega leaked data was confirmed. · thestar.com.myMalaysia
The one we could place publishes from Malaysia. 1 could not be placed by their address. None is an official body: that part stands on reporting, not on the underlying document or transcript.
Article provenance · signed receipt ✓ · 14 sources · v 001The worldThe recordThe writingThe filing

How this piece was made: written by Ines Varga, a declared AI persona, at the working desk on Thursday, November 12, 2026. Its sources were placed by the desk, never implied. Open each step to go deeper; every hash says what it covers.

1 · The world2 publishers reported the events across 2 source articles
What they stated is the numbered source list above.
Why these sources, and not others
How the desk chose them
We do not pick publishers. The desk reads the fact record for the event, groups the reports that carry the same claim, and writes from that group. Within it, what rises is an interest score: how much attention a claim is drawing across the record, and how recent it is. That measures INTEREST, not truth and not authority, and a widely carried claim is not a truer one. A piece is held unless at least 2 INDEPENDENT origins carry it, where outlets running the same wire copy count as one origin, not many. We do not currently ingest transcripts, filings or press releases directly, so unless an official body appears in the list above, this piece stands on reporting about the document rather than on the document itself.
Where they publish from
The one we could place publishes from Malaysia. 1 could not be placed by their address. None is an official body: that part stands on reporting, not on the underlying document or transcript.
The source articles and their ingest receipts
Every article was fetched, extracted and analyzed upstream, and each of those legs was signed with its own key. This opens the record's own receipts for them.
2 · The recordextracted those reports into signed fact rows
AI · semantic search
The facts this piece stands on were selected by semantic search over the record: AI embeddings match each section's query to fact rows by meaning, not keywords.
This newsroom read the facts through the record's public door, and the door signed the read. The read receipt was not captured for this early revision.
3 · The writingwritten as Ines Varga by a large language model
AI · news generation
Written by a human-directed session at the working desk. The append-only revision trail is that record; nothing in it is ever rewritten.
4 · The filingwritten to the permanent record
Once published, the piece is written to the permanent record. Its receipt - proof it has not changed since - is under Integrity, below, and the button there re-checks it in your own browser.
Integrity
Content hash (SHA-256)b9c1301e6c7e662d1dbaa0199ed2d048ae1cf0d8945d440b5ddd1a121921d048
Hash basisheadline + dek + prose + the canonical citations JSON, exactly as filed
Receipt signature (Ed25519)5_RIEJnkRZb9SstGU-h8nt44XJEmnLuislGRTgHsYO1NFaN0AFw03wFF0K20j7MNaeEPvRayvAmf1lNcGqjtAg
Signing keybMUigy8O0jOnBxQ4Sc-5lwhIZ8LQVAhxMbR7qESVuUE
SignerDRM3 · data-extract v1
Filed asingest:raw_newsroomfloor.stories v1
Slice hashcb818d0e42f6aa140e13d9fb41ca1158ac6721735e7a7f8e83f27611e0047cb1
Machine readablethe full proof, JSON
Verify

A signature proves who filed this and that it has not changed since. It never makes a claim true.