Iris Ohyama - A Suspicious File in the Cloud, 7.7 Million Customers at Risk, and an Online Store That Went Dark
20 minAudio
Got something to say to this podcast? Send a voicemail, and you might hear yourself on the next episode! Japanese home goods company Iris Ohyama (online store operator Iris Plaza) found a suspicious file in an external cloud service on 28 October 2026, shut its online store and related systems, and confirmed unauthorised third-party access. Police and Japan's Personal Information Protection Commission were notified on 29 October. On 5 November the company said about 7.7 million people could be affected: about 5.8 million current and former members (name, address, phone, email, gender, date of birth and password, where held) and about 1.9 million non-members such as guest-checkout customers and campaign entrants (name, address, phone, email). The company says data "may have been viewed or acquired"; it has not confirmed data was taken. Some data, including passwords, was encrypted (method not disclosed). Card data was not stored in the service. No misuse has been confirmed, no attacker contact received and no claim of responsibility seen. The cloud provider and the cause have not been disclosed. The online store remained offline for more than two weeks with no reopening date; marketplace storefronts kept trading. Lessons: guest data is customer data; delete data you no longer need; avoid concentrating all customer data in one unmonitored service; plan for extended outages; and stop password reuse. Visit www.kinsoft.com.au to talk through your security and IT needs. Sources: Iris Ohyama notices (29 Oct and 5 Nov 2026); BleepingComputer (8 Nov 2026); The Register (9 Nov 2026); eSecurity Planet (8 Nov 2026); Netshop Impress (9 Nov 2026).
Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.
Transcript
From the show. Tap a time to play from there.
So next time you buy something online and click continuous guest to protect your privacy, honestly, just don't bother. Yeah, it's pretty much a complete illusion at this point. Right. I mean, you are essentially wearing a fake mustache to the cash register while, you know, handing the cashier your actual driver's license to keep in their back room forever. Which is such a wild image, but technically that's exactly what's happening. We like to think. that opting out of creating an account makes us like digital ghosts. But
today we're looking at a multimillion dollar corporate disaster in Japan that proved just how permanent your guest footprint really is. Welcome to the deep dive, by the way. Glad to be here. And yeah, this case completely shatters that comforting illusion consumers have. And from an industry perspective, it really highlights a systemic kind of. catastrophic flaw in how modern retail infrastructure manages data retention. To unpack all of this, we're diving into a really detailed IT and security briefing from Tech Talks
with Kinsoft. And that actually references some reporting from Bleeping Computer. Right. Highly reputable sources in the InfoSec world. Exactly. So our focus today is a massive cyber incident involving Iris Oyama. And for those of you who aren't familiar, this is not... some niche boutique. They are a massive Japanese manufacturer and retailer. Yeah, they're huge. We're talking home appliances, furniture, pet supplies. Right. They are a total pillar of everyday commerce. They're running this massive online operation out of Sendai called Iris Plaza. So we have a retail
giant, a devastating breach, and a timeline that basically acts as a masterclass in what happens. when the hidden systems running our economy suddenly turn against the companies relying on them. It really is a masterclass. The briefing strips away all the usual corporate PR speak and shows us the raw mechanics of an active incident response. Okay, let's unpack this. Because the catalyst for that response wasn't like a blaring siren or a ransom note popping up on a screen. No, not at all. On October 28th, The company's IT
team found what the source refers to simply as a suspicious file sitting in an external cloud service they use. Which, you know, sounds incredibly vague to the average person. Yeah, I think when people hear suspicious file, they picture a Word document with a weird title on their desktop. Right, exactly. Like, do not open dot doc. Yeah. But in a highly secure corporate cloud environment, how does the system even flag a file as suspicious? I mean, what is it actually doing? Or were you talking about a massive malware payload? Usually,
large companies use something called file integrity monitoring. Okay. The system mathematically maps out every known authorized file on a server. So if a brand new file suddenly appears or an existing file is altered, it triggers an alert immediately. Wow. So it's basically a tripwire. Exactly. And in these types of cloud breaches, that suspicious file is rarely traditional malware. It's usually a web shell or some anomalous executable script. So an attacker finds a vulnerability
in the website's code and they drop this tiny script into a hidden directory somewhere. Right. It essentially acts as a backdoor, allowing them to send commands remotely. Wow. Yeah. It's not the end goal. It's the beachhead. Finding that file isn't the beginning of the attack. It is the forensic proof that an unauthorized actor is already inside the environment. Setting up camp. Exactly. And their reaction to finding that footprint is what makes this case study so wild to me. Because they didn't just isolate the affected server or quarantine the directory.
They initiated what we can really only call the nuclear option. Yeah, they went all the way. They completely severed the primary Sendai -based online store from the internet. They blocked all external access routes. And then... Purely as a precaution, they pulled the plug on a totally separate fashion store and other group service sites. What's fascinating here is that to a board of directors, that absolute shutdown looks like a catastrophic overreaction. Right, because I have to look at this from a business perspective. You find one rogue script in a cloud container, and your immediate reaction is to completely
nuke your primary revenue engine. It sounds crazy. It does. For a massive retailer that relies on daily high -volume transactions, Taking down multiple storefronts just in case sounds like, I don't know, burning down your entire house to kill a spider. It really does. There's always this intense screaming tension between commercial pressure and cybersecurity logic. Because the executives just want to keep the lights on. Exactly. But from an incident response perspective, Iris Oyama's reaction is actually the gold standard
of containment. Wait, really? The gold standard. Yeah, because of a mechanical concept called lateral movement. Look at it like the physical world. If a burglar breaks into your retail store, you lock the front doors and call the police. The damage is localized to that one building. Right. But in a networked digital environment, boundaries are permeable. Exactly. If an attacker breaches a low -level web server, they don't just stay there. They use that access to hunt for administrator credentials or map out the broader network architecture. Oh, I've heard of this. It's called privilege escalation, right?
Yes, spot on. You have to assume they are actively hunting for the keys to the kingdom. So the separate fashion store wasn't necessarily breached yet, but because it likely shared administrative infrastructure with the compromised system, it was highly vulnerable. Ah, okay. So every second you leave the network active, just to save a few dollars in sales, you are giving the attacker more time to dig deeper, extract more databases, or, God forbid, deploy ransomware across the entire ecosystem. You're choosing a guaranteed painful financial loss today. to prevent a limitless existential
loss tomorrow wow so shutting everything down immediately is the only way to freeze the crime scene exactly severing the connection gave their forensics team a frozen snapshot to analyze without the attacker actively interfering okay that makes sense but when they finally cracked open those cloud logs a week later on november 5th what they found completely destroyed that illusion of anonymous shopping we were talking about at the top of the show it really did the company revealed the scale of the exposure and The sheer volume is just staggering. We are talking about
7 .7 million people caught up in this. A massive chunk of the population. Yeah. And the breakdown of that 7 .7 million is where we start to really see the systemic failures and how the modern retail industry handles our data. Absolutely. Let's dig into the mechanics of that breakdown. So out of the 7 .7 million, about 5 .8 million were registered members. The data exposed included names, addresses, phone numbers, email addresses, genders, dates of birth, and passwords. Standard,
very sensitive profile data. Right. But the source highlights a very critical detail here. That 5 .8 million included former members. People who had actively terminated their relationship with the brand. Yes. Now, the source notes that former members didn't have stored passwords anymore, which implies some level of automated data purging happened when they closed their accounts, right? Right. The password field was likely wiped. But their names, physical addresses, emails, and birthdates were still just sitting there in the
primary cloud environment. It begs the question of why a company is holding on to the detailed personal demographics of someone who specifically asked to leave. It's a huge liability. But here's where the systemic flaw... becomes glaringly obvious. The remaining 1 .9 million affected people were non -members. Almost 2 million people. These are people who never created an account in the first place. They just entered promotional campaigns or used the guest checkout feature. Nearly 2 million people swept up in a massive data breach for a platform they actively chose
not to join. Mechanically speaking, how does this even happen? I mean, as a consumer, you assume guest checkout is a temporary session. You put the item in the cart. You give them a shipping address. They run the credit card. And once the toaster ships, that session dissolves. That's the logical assumption. Right. So why is a guest's physical address sitting in the same vulnerable database as a 10 -year loyal subscriber? Because from a database architecture standpoint, a transaction is a transaction. When you use guest checkout, the backend system still
has to generate a unique primary key to track your order, your shipping logistics, and your payment status. Okay, so the frontend makes you feel like a ghost. Exactly. The user interface makes you feel like a transient ghost, but on the backend, your data is written into the exact same relational database tables as the registered users. They just flip a binary flag in the database that says account creation false, so it doesn't prompt you to log in next time. Yes, but the actual data retention is identical. It's a complete mirage. Wow. And companies keep this data for
a multitude of reasons, right? Like returns processing, legal compliance, warranty claims. Sure. Those are the official reasons. Yes. But the biggest driver is analytics. Marketing departments want to track longitudinal consumer behavior. They constantly fight IT departments over data minimization because they view every single data point as valuable. Right. Data is the new oil, as they say. The Kintzoff briefing actually specifically references Australian privacy principles as a baseline here, which basically dictate that you
should destroy or de -identify personal information that you no longer need. Which is best practice globally, really. Right. And de -identifying meaning stripping out the names, emails, and street addresses. So the company just retains the raw, anonymous statistic that, say, a toaster was sold in this zip code on a Tuesday. Which is mathematically useful for their sales analytics, but... totally useless to a hacker. Exactly. Yet companies fundamentally fail to do this because cloud storage is just incredibly cheap. And writing complex engineering scripts to automatically
scrub guest data after, say, 90 days is expensive. It takes time and money they don't want to spend. So the result is this massive liability. It really proves that old cybersecurity adage, every record you keep is a record you can lose. It is the absolute truth of the industry. And the onus is entirely on the consumer to protect themselves, but the system's designed to hoard their data, regardless of the choices they make. Now, we know exactly who was in this database. 7 .7 million people, ranging from active shoppers to transient guests. A huge pool of victims. But what makes
this case study so tenuous is what the company actually knows about the threat actors themselves, or rather, the complete void of information they have. Yeah, the terminology used in their public disclosure is... incredibly cautious. And it points to a pretty terrifying reality of modern IT outsourcing. Right. The source notes that Iris Oyama stated the data may have been viewed or acquired. They haven't actually confirmed that a single record was formally exfiltrated. They just don't know. They don't know how many
records leaked. They also told Bleeping Computer they haven't received any direct communication from the attackers. No ransom demand. No extortion email. Furthermore, no hacker group has publicly claimed responsibility for this on any of the usual dark web leak sites. This is exactly what we call the fog of war in incident response. The fog of war. Yeah. When you lack absolute visibility into your own systems, you are paralyzed. The source also mentions that the passwords were encrypted, but the company entirely declined
to disclose how they were encrypted. This feels like a massive distinction that they are just glossing over. Oh, absolutely. I mean, if I'm one of those 5 .8 million members, I want to know the mechanism. Are we talking about standard two -way encryption or were they hashed and salted? That technical distinction is everything. If they were just encrypted, that means there is a master decryption key sitting somewhere on a server. Oh, no. Yeah. If the hackers stole the key along with the database, the passwords are essentially... plaintext. But if they were
hashed using a strong modern cryptographic algorithm, it means the passwords were run through a one -way mathematical function. Okay. So the database just stores a string of gibberish. If a hacker steals a hashed database, they can't just reverse it. They have to spend an enormous amount of computing power trying to guess the original passwords to see if they produce the same gibberish. Exactly. Okay. And the fact that the company isn't specifying their cryptographic method does not inspire confidence in the security community.
Yeah, that admission speaks volumes. And to add to this fog of war, the name of the cloud provider where this all happened remains unnamed in the briefing. And the attacker's initial entry method is entirely undisclosed. They don't know or they won't say. They're right, how the hackers got past the perimeter in the first place. How the hackers got past the perimeter in the first place. This raises an important question. And it brings us to a concept called systemic concentration risk. Okay, concentration risk. Yeah, think about the architecture here. A major retail giant put
their absolute crown jewels, the entire historical customer base of 7 .7 million people, into a single external cloud service. Which, you know, runs counter to everything we are told about the cloud being this highly distributed, resilient environment. Logically, if the administrative access to that specific cloud tenant is compromised, Geographic distribution doesn't matter. You've still created a single point of failure. Yes. This perfectly illustrates the flaw in the shared responsibility model of cloud computing. How
so? Well, when you outsource your primary data storage to a third -party vendor, the vendor secures the physical hardware, sure. But you are responsible for securing the access and the beta. Right. You're also entirely reliant on that cloud provider's logging mechanisms to tell you what happened. Ah. And if the attacker is sophisticated, the first thing they do after gaining privileged escalation is wipe the egress logs. Exactly. The records that show data actually leaving the network. So the company is staring
at a suspicious script. They know an unauthorized person was in the server, but because the logs are compromised or just insufficient, they have no mathematical way to prove whether the attacker downloaded the 7 .7 million records or just looked around and left. Ambiguity is agonizing. You have to assume the worst and notify 7 .7 million people enduring massive reputational damage without even knowing for sure if the data is actually in the hands of criminals. That is brutal. Now, there is a tiny silver lining noted in the source
material. No credit card data was stored in that specific compromised cloud environment. Which is a huge relief. Huge. And so far, there have been no confirmed reports of financial damage to the customers. But this absolute lack of visibility? This digital fog of war forced Iris Oyama into a brutal, ongoing operational nightmare. Right, because the consequences of hitting that nuclear containment option we discussed earlier, they don't just magically resolve in 48 hours while you wait for the forensics team to figure it out. Not at all. According to the Kinsoft briefing,
at the time this report was published, Iris Oyama's primary online store had been offline for more than two weeks. Two weeks, and modern retail is an eternity. Two full weeks of zero transactions through their bespoke digital storefront, with absolutely no date set to reopen. Try to quantify the financial hemorrhage of a multi -week indefinite outage for a company of this scale. It's staggering. And they vowed that they would only turn the servers back on when the root cause is definitively found and fixed. But if you are struggling with
cloud visibility and missing logs, finding that definitive root cause can take months. Easily months. Meanwhile, orders placed before the shutdown were delayed. Customer service queues were overflowing. The business effectively ground to a halt. This is the true price of containment. It is the ethical thing to do, but it requires a business to have immense operational resilience just to survive it. The source does mention one fascinating structural advantage that acted as a lifeline for them. While their own platform was totally dark, their storefronts on third -party marketplaces kept
trading. Which is a brilliant example of decoupled IT architecture saving a business from total ruin. It's like the digital equivalent of your flagship restaurant burning down, but because your supply chain and inventory are completely decoupled from your physical dining room, you can just route your ingredients to third -party food trucks across town and keep selling. That's a great way to put it. Because they utilized external sales channels connected via API that didn't rely on their internal compromised cloud, revenue didn't drop to absolute zero. It proved
that relying on a single monolithic platform is incredibly dangerous. Modern businesses have to architect their operations, assuming their primary channel will eventually go down. Absolutely. Looking at the entire lifecycle of this event, this tech briefing really exposes the systemic vulnerabilities that we all just blindly accept as normal. I mean, we've distilled five masterclass lessons from the source for our listeners today. Let's run through them. First, guest checkout is still customer data. As nearly 2 million people learn the hard way, avoiding an account doesn't
prevent aggressive data hoarding. Second, retention is inherently risky. Right. If you don't need it, destroy it or de -identify it. Keeping four more members' details creates unnecessary targets. Exactly. Third is concentration risk. You have to know where your crown jewels are stored. Putting the entire customer database in one poorly logged cloud environment creates a catastrophic single point of failure. It blinds you when things go wrong. Fourth, containment has a price. You have to plan for the financial hit of doing the ethical
thing. Shutting down means being prepared to survive weeks of zero primary revenue while searching for a root cause. And finally, passwords. The company had to warn customers about reusing passwords elsewhere. Because we don't know the cryptographic strength of those passwords, millions of users are now vulnerable to credential stuffing. Where hackers use automated bots to test those breach passwords across thousands of banking and email portals in seconds. Which is exactly why multi -factor authentication is no longer a best practice. It is a mandatory secondary barrier. It mitigates
the risk of systemic password reuse. It really changes how you view a simple online transaction. I mean, think about it. You think you're just buying a toaster on a Tuesday. You punch in your address, you check out as a guest, and you assume the interaction is over. But mechanically, you are leaving a permanent, indelible digital footprint in a cloud server. Right. A footprint that might end up in the hands of an undisclosed threat actor years after the fact, simply because a corporation didn't want to spend the money to scrub their own archives. It forces a broader
philosophical question about the future of digital commerce, really. How so? Well, we've built an entire global economy on the premise that data hoarding is inherently valuable. But as these breaches become more frequent and the containment costs become more devastating, that calculus has to shift. I mean, retaining old data is exactly what exposed millions of former members and guest users in this specific breach. It makes you wonder if the current data model is fundamentally broken. So what does the alternative look like? I mean, if we can't trust the current model of corporate
retention, where do we go? Well, think about this. What if, in the near future, the ultimate luxury a company can offer you isn't a highly personalized, algorithm -driven shopping experience based on years of your stored behavior? Okay, I'm listening. What if the new gold standard for consumer trust is verifiable, mathematically proven cryptography, like zero knowledge proofs, that guarantees the company has completely forgotten you exist the very second your transaction is over? Wow. A guaranteed, mathematically enforced
vanishing act. I love that. Moving away from the idea of trusting a company to protect your data to demanding an architecture where they simply don't possess it in the first place. Exactly. Because the only truly secure record is the one that no longer exists. What a phenomenal place to leave it. Thank you so much for joining us on this deep dive. To all of you listening, stay curious, take a hard look at your own digital footprint, and we will catch you next time.
Got something to say to this podcast? Send a voicemail, and you might hear yourself on the next episode! Australian online retailer Who Gives A Crap told customers on 7 November 2026 that their information was accessed...
Got something to say to this podcast? Send a voicemail, and you might hear yourself on the next episode! Last week in tech, 7 to 14 November 2026. Microsoft's November Patch Tuesday (10 November) fixes well over a...
Got something to say to this podcast? Send a voicemail, and you might hear yourself on the next episode! Chainalysis disclosed on 30 October 2026 that an external actor using "offensive agentic techniques" accessed...
Got something to say to this podcast? Send a voicemail, and you might hear yourself on the next episode! NSW Health reported unauthorised access to its Oral Health Fee For Service Scheme website on 29 October 2026;...
Got something to say to this podcast? Send a voicemail, and you might hear yourself on the next episode! Last week in tech, 30 Oct to 6 Nov 2026. US tech stocks sold off hard on Thursday 5 November: the Nasdaq Composite...