A breach that started in someone else's cloud
Japanese manufacturer Iris Ohyama, the operator of the Iris Plaza shopping platform, disclosed that personal information on roughly 7.7 million people may have been viewed or taken from an external cloud service it uses. That number describes the data sitting in the compromised environment — not a confirmed leak of 7.7 million individual lives. Iris Plaza has said the actual number of records accessed and people affected is still under investigation, and as of its 5 November 2026 update it had received no reports of misuse or financial loss tied to the incident.
The company found suspicious files in the cloud service on 28 October 2026, shut down its online store the same day, and confirmed unauthorized access by a third party the next day. Store shutdowns spread across group-affiliated sites while the investigation runs. BleepingComputer
Timeline: from suspicious file to dark storefront
The sequence, per the company's own notices, is short and fast-moving. On 28 October, staff discovered the suspicious file in the external cloud service and moved immediately: the Iris Plaza online store — the storefront called SIMPLE STYLE — and related systems went offline. On 29 October, Iris Plaza confirmed third-party unauthorized access and published its first public notice. Japan's Personal Information Protection Commission and the police were notified the same day.
A week later, on 5 November, the company published a second report with the number that turned a regional incident into an international headline: up to approximately 7.7 million people's information may have been exposed. The first notice had disclosed the intrusion; the second quantified it. That gap — one day from discovery to disclosure, eight days from disclosure to scope, is the shape a lot of incident timelines take, and the final report, when it comes, is what will close the remaining gaps: entry method, attacker identity, and how many records were actually taken rather than merely at risk.
Who was affected: members, ex-members, and shoppers who never signed up
The affected data breaks into two populations, and the second one is the part that should get security teams' attention.
The first group is roughly 5.8 million registered members, including people who have already cancelled their accounts. Their potentially exposed fields include full names, physical addresses, phone numbers, email addresses, gender, dates of birth, and account passwords. What was exposed varies person to person depending on what each registered; notably, passwords are excluded for former members, since the company says it doesn't hold them for cancelled accounts.
The second group is roughly 1.9 million non-members: guest checkout buyers, campaign applicants, and other people who handed Iris Plaza their name, address, phone number, and email address without ever creating an account. They never set a password to worry about, and they're the least likely to hear about this breach through normal account-notification channels.
Anyone in either group can check their status through the company's contact center at 0120-108-824 (toll-free, weekdays and Saturdays, 9:30–17:00 Japan time) or by email at [email protected].
Passwords, encryption, and the credit card question
Iris Plaza says passwords and some other fields were stored in encrypted form, which is the right answer and an incomplete one: the company has not disclosed which encryption scheme it uses, so "encrypted" is currently a claim, not a verifiable control. If you registered an Iris Plaza account, assume your password belongs in the "may have been exposed despite encryption" bucket until more detail emerges, which mostly matters if you reused it anywhere else. Change it everywhere that matters.
What didn't move, according to the company: credit card information was not stored in the affected cloud service. That takes one nasty scenario off the table and is the single most reassuring sentence in either notice. It also illustrates why data-location inventory beats data-existence panic, the cards were presumably elsewhere, on infrastructure that wasn't breached.
One quiet detail from the second report deserves flagging: used-up data stayed in the cloud. Former members' records, kept after cancellation, sat in the same external service as active members' data and are now part of the exposure scope. The security reporting in Japan picked up on this sharply, and it's a fair prompt for any data-management team to run its own inventory: what do we still keep for people who left, where does it live, and what access does the outside service holding it have? Keeping departed customers' data that long isn't proven to have caused this intrusion, nobody has established a causal link. But it enlarged the blast radius, and that's within the company's control in a way the attacker isn't.
Company data breach examples keep trending toward the vendor's cloud
Add Iris Plaza to the running list of company data breach examples where the compromised system wasn't the victim's own data center at all, it was a third-party cloud service holding customer records. The pattern has been repeating across Japan and beyond. Burger King Japan's app-server breach exposed over 11 million records through a web server, and coverage of incidents like the Chainalysis agentic AI intrusion keeps hammering the same point from the other direction: perimeter assumptions are obsolete.
The lesson that recurs in the analysis of vendor-held data trails is that your customer data's risk profile is defined less by your own hardening than by wherever the data actually rests and who else can reach it. Iris Plaza's case is almost a textbook diagram of it: the retailer did the visible things right, fast shutdown, prompt regulator notification, public notices, and the exposure still scaled to millions because the vulnerable asset was rented.
For anyone building corporate threat assessments, the concrete questions this case raises are unglamorous: Which external cloud services hold personal data? Whose inventory includes ex-customers and non-account holders? Who audits the vendor's access paths, and on what schedule?
What Iris Plaza is telling customers to do
The company's guidance, echoed in the Japanese security press, comes down to three things. If you used your Iris Plaza password anywhere else, change it on those other services now. Watch for fake emails, SMS messages, phone calls, spoofed sites, and social accounts impersonating the company or related organizations, breach data reliably feeds follow-on scams within weeks. And remember the negative test: Iris Plaza says it will never ask you for passwords or authentication codes, so any message that does is fraudulent no matter what it claims about this incident.
Verification advice travels with that: don't click links inside notification emails, because sender addresses can be spoofed. Check announcements directly on the company's official site, and reach the contact center through the independently published number above.
Where this lands
BleepingComputer and CyberInsider reported the disclosure in early November; Iris Plaza published its second report on 5 November 2026, and a final investigation report, scope of actual access, entry method, likely attacker, is still outstanding. The store remains offline and group-affiliated services remain suspended while the inquiry continues, with the regulator and police already engaged. Readers wanting the affected-population figures or the discovery-to-disclosure dates will find both laid out above; the open thread from here is simply the closing report, and whether Iris Plaza's vague "encrypted" claim survives scrutiny once the company explains itself. Watch the company's own notices rather than the rumor cycle for that, in this case, the official page has been the most accurate source anyway.