
In the Iris Ohyama data breach, Iris Ohyama says a third-party cloud service behind Iris Plaza may have exposed personal data on about 7.7 million people. The person count is still an estimate, the cloud vendor is unnamed, and the only published detection clue is a suspicious file.
Key takeaways
- About 7.7 million people may be affected: up to 5.8 million Iris Plaza members and former members, plus 1.9 million non-members, with the record count still open.
- A suspicious file in an unnamed third-party cloud triggered detection; SIMPLE STYLE and Iris Tech Service sites were suspended on October 28, 2026.
- Active-member passwords are described as encrypted, with no scheme published; former members have no passwords stored.
- Credit card data was not in that cloud, and no misuse was reported as of November 5, 2026. No perpetrator or direct attacker contact has been reported.
What did the Iris Ohyama data breach confirm?
Iris Ohyama has confirmed that customer data held for its Iris Plaza shopping platform may have been accessed inside a third-party cloud service. The company puts the possible exposure at about 7.7 million people.
That figure breaks into up to 5.8 million registered members and former members, plus 1.9 million non-members. Exposed fields can include full names, postal addresses, phone numbers, email addresses, gender, dates of birth, and account passwords. The combination varies by individual.
The 7.7 million figure is not a finished record count. Iris Ohyama is still determining how many records were exposed and how many people that represents.
Systems came down on October 28, 2026. The first notice went out on October 29, the same day Japan’s Personal Information Protection Commission and the police were notified.
As of November 5, the company reported no misuse or financial loss.
Reporting does not say whether affected people were notified directly or whether the suspended sites were restored.
Where did the Iris Plaza data sit?
The exposed records lived in an external cloud service used by the Iris Plaza online store.
The company says it found a suspicious file there, suspended Iris Plaza and related systems, and confirmed unauthorized access by a third party. On October 28 it also suspended SIMPLE STYLE and the Iris Tech Service Co., Ltd. sites for home appliance subscriptions and furniture and appliance delivery and installation.
The identity used for access, objects read, and any data copied out remain undisclosed. So do the cloud provider, access path, and any vulnerability.
A suspicious file shows that someone could write in that store at some point. It is weak proof of the entry path or a bulk download.
Responders should anchor an identity timeline on the file’s earliest time: sign-ins, new keys, OAuth grants, role changes, and MFA or recovery edits. Object reads require data-event logging, which Iris Ohyama has not described.
What does "encrypted passwords" fail to prove?
Active Iris Plaza members had passwords stored in encrypted form. The company did not name the scheme.
Former members are different: Iris Plaza says it stores no passwords for them, so they can appear in the name-and-address set with no password field.
Encrypted does not distinguish a one-way hash from reversible ciphertext. A sound password store uses a slow one-way function with a unique salt and named work factor. Reversible encryption adds a key, whose location matters.
Until Iris Ohyama states the algorithm, salt handling, work factor, key custody, and whether that material lived in the accessed tenant, the need for a forced reset and session revocation remains open.
Who is in the 1.9 million non-member group?
The reporting does not define non-members beyond people whose data sat in that cloud without a stored member password.
Those fields support targeted phishing, phone scams, and identity checks elsewhere without a password or card number. Notice and fraud monitoring must reach beyond current members.
Credit card data was not stored in the affected cloud service, the company says. That narrows card fraud tied to this store, but the identity file remains usable for fraud.
What should security leads take from the timeline?
Iris Ohyama has not identified the perpetrators. A spokesperson told BleepingComputer it had received no direct communication from the attacker when asked whether a ransom had been demanded. Reporting confirms no ransom demand, named malware, or intrusion path.
If a customer file sits in a vendor cloud, check which identities can read customer objects and whether reads are logged long enough to reconstruct them. Establish where password verifiers and encryption keys sit, and how member, former-member, and guest rows are keyed to avoid double-counting.
A periodic cloud configuration review and a SaaS penetration test answer those checks before a file appears that the company did not place there. An e-commerce penetration test that stops at the storefront misses the tenant holding the customer file.
FAQ
Was credit card data stolen in the Iris Ohyama breach?
No credit card information was stored in the affected cloud service, according to Iris Ohyama. As of November 5, 2026, it reported no misuse or financial loss.
How many people were affected by the Iris Plaza breach?
About 7.7 million people: up to 5.8 million current and former members, plus 1.9 million non-members. The record and person counts are still being reconciled.
Were Iris Plaza passwords stored in plaintext?
The company says active-member passwords are encrypted and former-member passwords are not stored. Without the algorithm, salt, work factor, or key location, encrypted does not show whether passwords resist offline cracking.
Did the company name the cloud provider?
No. Iris Ohyama has not named the provider, access vector, or any vulnerability. It found a suspicious file in the external cloud used by Iris Plaza.
If your customer file lives in a vendor cloud, agent::offense can test that tenant the way an intruder would, starting with identity paths and object access. See our cloud and container security testing.