BigCommerce - One Stolen App Key, Hundreds of Stores, and the Plugin You Forgot You Installed
13 minAudio
Got something to say to this podcast? Send a voicemail, and you might hear yourself on the next episode! BigCommerce has confirmed that stolen API credentials for two third-party storefront apps, Ribon and Ribon 1.5, were used to take shopper data from merchant stores and inject malicious scripts into a small number of storefronts. BigCommerce says its own platform was not breached. Who's involved. BigCommerce, founded in Sydney in 2009 and now operated by Nasdaq-listed Commerce.com, hosts online stores for tens of thousands of businesses and supports more than 1,200 third-party apps. Ribon and Ribon 1.5 are run by Be A Part Of, a Fastr company. Several retailers have notified customers; UK retailer Master of Malt is the only one to publish a detailed account so far. Timeline (UK time, per Master of Malt as reported). 13 September, 17:21 - unauthorised use of the Ribon app key begins. 16 September - Ribon's developers become aware of the misuse. 17 September - BigCommerce confirms the compromise, uninstalls the apps from affected stores, and the key is revoked. 18 September - BigCommerce notifies merchants; Master of Malt emails customers. 19 September - the UK ICO opens a case. From 21 September - major security-press coverage. What was exposed. Shopper names, email addresses, phone numbers and shipping addresses, pulled page by page through BigCommerce's own interfaces. Not exposed, per BigCommerce and Master of Malt: passwords and payment card data. BigCommerce says the credentials were compromised "due to a Fastr system compromise." Unknown: total merchants and shoppers affected, how Fastr was breached, and what the injected scripts did. No CVE is involved and no group has claimed the attack. A different BigCommerce app was compromised in 2024 to skim ZAGG customers' cards. Lessons. Audit your store's installed apps and remove anything unused or unowned. Grant apps the minimum permissions they need. Monitor for unusual bulk API reads. Ask vendors how they protect the keys they hold for you and how quickly they'll notify you of a breach. Under Australia's Notifiable Data Breaches scheme, a breach that starts at a third party can still be your obligation. Warn affected customers about targeted phishing. Visit www.kinsoft.com.au to talk through your security and IT needs. Sources: BleepingComputer; SecurityWeek; TechRadar; GBHackers; CyberPress; Shopifreaks; Born City; Emery Reddy; Digital Commerce 360.
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.
Welcome to the Deep Dive. You know, today we have a really fascinating and honestly a pretty terrifying reality of online shopping to explore with you. Yeah, terrifying is definitely the right word for this one. Right. Because we're looking at how a single stolen digital key from like this completely obscure third -party app ended up compromising hundreds of online stores. Hundreds. Hundreds. And it really changes how you look at the websites you buy from every day. Totally. So our core mission today is to break
down this massive supply chain cyber attack. We are pulling all our info from a really detailed tech talk that Kinsoft gave recently back on October 2nd, 2026. Yeah, the Kinsoft breakdown was incredibly thorough. They really laid bare how these attacks actually happen in the wild. Okay, let's unpack this. Think of this situation like installing a state -of -the -art bank vault security system on your house, but then giving a master key to the guy who waters your plants once a year. Oh, that is a perfect way to look
at it. Right. And then when his pocket gets picked, your vault is suddenly, you know, wide open. Exactly. I mean, we so often think of cyber attacks as these brute force hacks against giant tech companies, right? Like hackers hammering down the front door of some massive corporation. Like in the movies. Yeah. Exactly, like the movies. But the reality is just much stealthier. It relies entirely on these trusted vendors that we, frankly, forget we even hired. Which brings us to the scene of the crime. To really understand how
this happened, we first have to grasp just the massive scale of the platform that was targeted. Right, because scale is everything here. Yeah, and the specific side door that the hackers actually used. So the platform at the center of this is BigCommerce. BigCommerce, yeah. And for those who don't know, it's a massive SaaS e -commerce platform. We are talking tens of thousands of businesses across, I think, 150 countries. Yeah, it's huge. Started in Sydney back in 2009, and now it's U .S. headquartered under the NASDAQ
-listed Commerce .com. It's an absolute giant. Right. So it's not some rinky -dink operation. It's enterprise -grade. But the thing about BigCommerce is its ecosystem. It has over 1 ,200 third -party apps that merchants use for, you know, reviews, shipping, pop -ups. Because the main platform can't do absolutely everything for everyone. They have to allow these plugins. Exactly. And that leads us to the specific vulnerable apps in this Kinsoft report. They were called Ribbon and Ribbon 1 .5. Right. Ribbon. Yeah. They're these storefront optimization tools run by a
company called Be A Part Of, which is a faster company. And this is where the mechanism of the attack gets really interesting. Because the attackers didn't breach the stores themselves. No. And they didn't breach BigCommerce either. Right. Wait. So the main platform was completely secure. Completely secure. The attacker has essentially just found an authorized VIP pass lying on a third party's driveway and walked right through the front door? Well, what's fascinating here is how the architecture of the modern web basically requires this exact vulnerability to exist. Wait,
requires it? Yeah, I mean, these apps like Ribbon, they absolutely must have access to store data to function. You can't optimize a storefront if you can't see the customers or the inventory. Right. OK. Yeah, that makes sense. But that required access transforms every single minor developer, every small widget maker into a high value target for hackers. They stole an API credential, a key directly from the app developer. And that key let the app talk to the store on the merchant's behalf. Wow. So they just bypassed the giant
vault doors completely. Entirely bypassed. OK. So now that we know how they got the keys, let's look at the timeline. because the Kinsoft talk laid out exactly how long they roamed the halls completely undetected. And this is the part that really shocks people. It's wild. They used a UK retailer, Master of Malt, as the main case study here. So Sunday, September 13th, at exactly 5 .21 p .m. UK time, that is when the unauthorized use of the ribbon key begins. Sunday evening. Classic time to launch an attack because security
teams are often understaffed or, you know, just offline for the weekend. Right. They're at home watching TV. So the hackers are in. But the ribbon developers, the guys who actually own the key, they don't even notice the misuse until Wednesday, September 16th. Three full days later. Yeah. And then it takes until Thursday, September 17th for BigCommerce to officially confirm the compromise, uninstall the apps and revoke the key. So from Sunday to Thursday, the attackers just had free reign. Free reign. By September 18th, BigCommerce
notifies the merchants. Master of Malt immediately emails their customers. September 19th, the UK Information Commissioner's Office opens a case. And by the 21st, you know, the tech press, bleeping computer, security week, they're all over it. But during those four days, the damage was already done. Yeah, let's talk about the damage because they didn't just look around. The hackers used that VIP key to inject malicious scripts, right? Yes, exactly. And they started pulling customer records essentially page by page. Right. They automated it. And they got names, emails, phone
numbers, shipping addresses. I mean, pretty much everything except, thankfully, passwords and payment cards. Yeah, that's a crucial point. The passwords and payment info are stored in a separate, completely uncompromised system. So the hackers couldn't touch that. Okay, but still, four entire days feels like an eternity in digital time. I mean, if someone was manually pulling files from a physical filing cabinet for four days straight, someone would tackle them. You'd hope so, yeah. Why is this so invisible in the digital space? Well, it comes down to
how API calls work. Automated API calls can very easily mimic legitimate app behavior. How so? So an e -commerce platform processes billions of requests a day, right? It's just a constant stream of background noise on the internet. Right, just massive traffic. Yeah. So when the attackers use an authorized key to ask for data, the system just says, oh, it's ribbon asking for data, like always. The extraction was paginated. They just blended right into that background noise, which
makes bulk data extraction incredibly hard to spot until it's just way too late. That is deeply unsettling. And there are still so many unknowns, right? Like the Kinsoff talk pointed out, we don't even have a total victim count. No, we don't. We don't know exactly how Faster was compromised in the first place or what all the injected scripts actually did. Or who's even responsible. And, you know, Faster hasn't really commented on the specifics yet. Right. So this Master of Malt
timeline is terrifying, but it's really just one symptom of a much wider disease. We need to zoom out. Absolutely. This isn't just a big commerce problem. No, exactly. This affects the entire internet economy. This same vulnerability applies universally to any hosted platform. Shopify, WooCommerce, Wix, Squarespace, they all use these third -party apps. Yeah, they all rely on that exact same plug -in architecture. And there's precedent for this. The Kinsoft talk highlighted that this happened back in 2024 with a totally different big commerce app that targeted Zag
customers for payment skimming. Yep. The methodology is already out there and proven to work. And this brings up a huge legal reality, which is just brutal for the merchants. For example, looking at the Australian Notifiable Data Breaches Scheme under the Privacy Act. This part is so frustrating for business owners. It is. Because if you are a merchant, the fact that a third -party app caused the breach literally does not matter. It is your obligation to assess the damage and notify your customers. You hold the relationship with the customer, so you hold the liability.
So what does this all mean? I mean, it places just a monstrously heavy burden on small business owners. You pay for a massive platform like BigCommerce or Shopify specifically so you don't have to be a cybersecurity expert, right? Right. You're outsourcing your security. Yeah. But then you are still legally left holding the bag when some random third -party plug -in fails. If we connect this to the bigger picture, it really highlights the ultimate paradox of software as a service. The paradox. Yeah. You buy into these platforms
for the security and the ease of use. But the very minute you start customizing it with plugins and widgets to make it work for your specific business. Which you have to do. Which you have to do. You actively dilute that security. You are handing out copies of your house keys to every contractor who walks by. Man, that is bleak. Okay, so knowing this terrifying ecosystem exists, how can a merchant possibly defend themselves? And, you know, what should consumers do if they get caught in the crossfire? Well, the Kinsoft source actually laid out a pretty solid defense
playbook for the future. Four actionable steps for merchants. Okay, let's go through them. What's step one? Step one is to relentlessly audit your installed apps. If you aren't using an app anymore, delete it immediately. That removes the unused digital keys from circulation. Makes sense. Don't leave spare keys under the mat if you don't need them. What's step two? Step two is enforcing least privilege. When you install an app, you need to give it the absolute minimum permissions required to do its job. Here's where it gets really interesting because I love this analogy.
It's exactly like downloading a simple flashlight app on your phone and it suddenly asks for access to your GPS location and your photo gallery. Exactly. Why does a flashlight need your photos? It doesn't. Right. And we need to start saying no to greedy e -commerce apps the exact same way. If a pop -up widget wants access to my entire customer database, that's a red flag. Huge red flag. But a lot of merchants just click accept all to get the install over with. Yeah, guilty as charged sometimes. Okay, step three. Step three is you have to actively watch for bulk
access. Don't rely on the vendor to tell you something is wrong. Merchants need to check their platform logs for apps that are suddenly, you know, reading thousands of records out of nowhere. Looking for that spike in the background noise. Precisely. And the final step, step four, is asking your vendors awkward questions in writing. Awkward questions. Like what? Ask them straight up how they store their API credentials. Ask them what their guaranteed timeline is for breach notification. If they can't answer, maybe don't use their app. That's really good advice. Get
it in writing. But what about the consumers, the people whose data was actually stolen in this ribbon breach? For consumers, it's all about hypervigilance regarding phishing. The attackers have your name, your phone number, and your physical shipping address. But not the credit card. Not the credit card. But they can use that physical address data to send highly convincing targeted phishing messages, like a text saying, hey, your package to 123 Main Street has been delayed. Click here to pay a $1 redelivery fee. Oh, wow.
And because it has my real address, I'd probably click it. Exactly. They use the stolen data to build trust, and then they steal your credit card on the fake landing page. That is so sneaky. But I will say that Kinsoft Talk did have some praise in all this darkness. They highlighted Master of Malt as essentially the gold standard for how to respond to something like this. Yeah, Master of Malt handled it beautifully. They notified their customers the exact same day they found out, right? Same day. They reported it to the regulator immediately, and they published incredibly
detailed technical follow -ups so other companies could learn from it. That level of transparency is rare. It is. And this raises an important question about how we view security. Because Master of Malt wasn't careless. They didn't do anything wrong. They were just a victim of modern web architecture. Right. They just used a tool that everyone uses. Exactly. So the ultimate lesson here is that perfect prevention is basically impossible now. You can't perfectly secure a system that relies on 100 external vendors. You
just can't. No. So making sure you have perfect response and absolute transparency like Master of Malt did, that is really the only true defense we have left. Wow. Okay. So for you listening, I think the big takeaway here is that the next time you click install on some quick, easy widget for your online business, or honestly, even if you just buy a bottle of spirits from an indie retailer online, there is a massive, totally invisible web of third -party vendors holding your data. A massive web. Security truly is only
as strong as the weakest link in that chain. It really makes you wonder about where this is all heading. I mean, if our entire digital economy relies on thousands of small, potentially vulnerable plugins having these master keys to massive platforms, are we inevitably moving toward a future where major platforms just ban third -party developers entirely? Oh, wow. Just shut them out. Yeah, like effectively destroying the open plug -in culture we currently rely on just to build these secure monolithic walled gardens where data never
leaves the main platform. Because at a certain point, the liability might just be too high. That is a wild thought to end on. It would completely change the Internet. Well, definitely something to chew on. Thanks for joining us on this deep dive. Stay vigilant out there 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! Japanese home goods company Iris Ohyama (online store operator Iris Plaza) found a suspicious file in an external...
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;...