Skip to content
PodSubs
ShowsPeopleGuestsJobsNewsEvents
More
BlogPodCred
Menu
ShowsPeopleGuestsJobsNewsEventsBlogPodCredNetworksSign in
Join nowSign in
  • Shows
  • People
  • Jobs
  • News
  • More
    • Guests
    • Events
    • Blog
    • PodCred
    • Networks
    Join nowSign in

Tech Talks With Kinsoft

Tech Talks With Kinsoft artwork

Manchester Airports Group - 8.7 Million Travellers, and the API Keys Sitting in Plain Sight

Sep 3, 202621 minAudio

Got something to say to this podcast? Send a voicemail, and you might hear yourself on the next episode! Manchester Airports Group - 8.7 Million Travellers, and the API Keys Sitting in Plain Sight A deep-dive into the largest known customer data breach at a British airport operator - and the claimed entry vector any developer could have spotted. On 27 August 2026, Manchester Airports Group (MAG) - operator of Manchester, London Stansted and East Midlands airports - disclosed that an unauthorised third party had stolen customer data from its commercial systems: car park bookings, lounges, Fast Track and Wi-Fi sign-ups. Roughly 8.7 million customers were affected. For most, the exposure was an email address; parking, lounge and Fast Track customers also lost phone numbers, UK postcodes and vehicle registration plates. No payment data was held in the affected system, and no airport operational systems were touched - flights ran normally. On 30 August, extortion group FulcrumSec claimed the attack to BleepingComputer: ~86GB stolen, entry via API credentials for third-party marketing platform Iterable allegedly exposed in client-side JavaScript, plus ~200,000 records about upcoming travel. Those claims are unverified - but BleepingComputer independently validated sample data against one traveller's real purchase history, and the samples were far richer than MAG's disclosure: booking references, prices, parking dates and historical spend. In this episode: - The confirmed facts versus the criminal's claims - and why the distinction matters - MAG's response: containment, ICO notification within UK GDPR's 72-hour window, suspending Manage My Booking, and contacting every affected customer - Why postcode + number plate + parking dates is near-perfect phishing bait - Four lessons for Australian businesses: your marketing SaaS stack is attack surface; never ship API keys in client-side code; data minimisation decided this breach's severity years in advance; and assume the true scope is worse than your first assessment Visit www.kinsoft.com.au to talk through your security and IT needs. Sources: BleepingComputer (27 and 30 Aug 2026); Infosecurity Magazine (27 Aug 2026); Security Affairs (30 Aug 2026); MAG data-security incident page; TTG Media (28 Aug 2026, ICO confirmation).

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.

Be honest with me for a second. Have you ever been sitting at a terminal waiting for a flight? Maybe your data connection is just a little spotty and you trade your email address for 30 minutes of free airport Wi -Fi. Oh, yeah. I mean, everyone does it. Right. You just you click a little box. You agree to some terms of service. You definitely didn't read. And boom, you get your connection. Exactly. It's just a reflex at this point. Yeah. And it feels like the most harmless transaction in the world. Right. Like a totally fair trade. But today we're going to look at how that exact

everyday scenario just became part of the largest known customer data breach at a British airport group. It really is. kind of the perfect modern trap because we hand over these little pieces of ourselves, you know, an email here, a phone number there, maybe our zip code at the cash register without a second thought. Because the individual pieces feel completely worthless. Right, exactly. But when you aggregate millions of those harmless transactions in one database, you create this incredibly tempting target. And

you often hand that target over to the systems with the weakest security. Which is terrifying. And our source material today is a really fantastic breakdown from Tech Talks with Kinsoft. They did this full deep dive into the recent Manchester Airports Group data breach. It's a great piece of reporting. It really is. And our mission today isn't just to report on a hack. We really want to deconstruct how a basic, totally preventable web development mistake ended up exposing the

data of 8 .7 million travelers. Yeah, because this isn't just about... an airport in the UK. No, not at all. This is about how your personal data is handled by basically every business you interact with online. Okay, let's unpack this. We've got 8 .7 million records exposed. What actually happened here? So we're looking at the Manchester Airports Group, or MAG, and they run three major airports in the UK. That's Manchester, London Stansted, and East Midlands. So we are talking about tens of millions of passengers passing through these hubs every single year.

And to really understand this breach, we kind of have to understand the architecture of a modern airport. Right. Because it's not just, you know, airplanes and baggage claims. Exactly. It's not just runways and radar and air traffic control. Yeah. An airport today is essentially a massive shopping mall and hospitality venue. That just happens to have a runway attached to it. That's a great way to put it. They're essentially running all these multiple disparate businesses under one roof. Like they sell car park bookings, access to VIP lounges. Fast track passes so you can

jump the security queue and, of course, the free Wi -Fi in exchange for your email. Right. And that structural division is really the firewall of this entire story. So late this past August, MAG disclosed that an unauthorized third party had accessed and stolen customer data. But this is key. They didn't touch the actual flight stuff, right? Exactly. They didn't touch the aviation security systems. They didn't touch air traffic control. Check -in systems were completely untouched. Oh, wow. Yeah, flights ran normally the whole time. The attackers purely targeted those ancillary

commercial systems we just mentioned. You know, the parking, the lounges, the Wi -Fi. Which is just wild to think about. It's like spending millions on laser grid bank vault doors to protect the cash, but then leaving the customer ledger sitting on a card table in the lobby with the front doors propped open. Yeah, that's actually a really good analogy. The focus of their security was heavily skewed toward operational safety. Which, you know, makes sense for an airport. Sure. Obviously, you want the planes to be safe. Right. But it left the commercial side vulnerable.

Now, to Mac's credit, once they realized the commercial systems had been compromised, their initial response was entirely orthodox. By the book. Completely by the book. They contained the access, restricted the affected systems, brought in specialist cyber advisors, and they notified the authorities. Under the UK's GDPR privacy rules, you have 72 hours to notify the information commissioner's office. And they hit that deadline. Okay, so they were on it. They were. They even temporarily suspended their online manage my booking service just as a precaution.

So on paper, they did exactly what they were supposed to do. Initially, MAG came out and framed this as mostly a leak of email addresses from those Wi -Fi signups. Like they admitted a smaller group of people, the ones booking parking or fast track passes, lost a bit more like phone numbers, UK postcodes and vehicle registration plates. Right. But they were very quick to assure everyone that no payment data, no credit cards and no bank details were compromised. Right. And if the story ended right there, it would be a textbook, you know, medium severity corporate

breach, a bad day at the office. but managed well and mostly just an inconvenience. Right, but it didn't end there. No, it didn't. The situation escalated dramatically just a few days later. A group calling themselves FulcrumSec reached out to journalists at Bleeping Computer to claim responsibility for the attack. And this is where things get messy. Very messy. And this is where we have to carefully separate corporate disclosures from unverified criminal claims. FulcrumSec claims... They didn't just grab a few emails. They claim they stole 86 gigabytes of data. Wait, 86 gigabytes

of purely text -based data? That is an astronomical amount of information. It's massive. Because text files are tiny. Like, to get to 86 gigs, you are talking about millions upon millions of incredibly detailed rows of data. Yeah, it's huge. It gets much worse. They also boasted that they were holding onto roughly 200 ,000 records of future travel. Future travel, like flights that haven't happened yet. Exactly. We're talking dates, times, and bookings for the rest of 2026

linked to identifiable people. Oh, my God. Yeah, think about the real -world implications of that for a second. If criminals hold a database of future travel, they know exactly when hundreds of thousands of people will not be home. Oh, I didn't even think about that. Right. They know when executives are out of the country. They know when properties are vacant. It transforms a digital privacy breach into a literal physical security threat. That is terrifying. And the craziest part, Fulcrumsec actually claimed they might withhold releasing those specific future travel records out of a sense of, quote, restraint

to prevent real world harm. Oh, how generous of them. The moral compass of an extortion syndicate holding your data hostage. Yeah, it's quite the spin. It's such a bizarre psychological flex. But here's where it gets really interesting for me. It's the how. How did they get all this data? Because according to the attackers, they didn't use some, you know, sophisticated zero day exploit. No, they didn't. They didn't shatter a firewall or brute force a password. They claim they got in using API credentials for a platform called

Iterable. Right. So Iterable is a third party marketing and customer engagement platform that MAG was using. It's a software as a service or sauce tool. Yeah. And an API credential, an application programming interface key. is essentially a digital VIP pass. Okay, a VIP pass. Yeah, it allows two separate pieces of software to talk to each other and share data automatically without a human having to do anything. But the criminals claim these digital VIP passes weren't stolen in a sophisticated heist. They claim these API keys were left sitting in plain sight. In client -side

JavaScript? Yes. I just want to make sure I'm understanding the underlying logic here. Is this the digital equivalent of taping your house key to the front door next to a neon sign that says spare key here? What's fascinating here is the fundamental difference between server -side operations and client -side code. Because your analogy is spot on. Okay, break that down for me. So when you build a website, there are things that happen on the server. Think of the server as the locked room in the back of a restaurant where the chef cooks and the faif is kept. Yeah. You, the customer,

you never see that room. Right. But the client -side code, that's the menu. That's the visual stuff that is sent directly to your web browser so you can view and interact with the page. And anyone can look at the menu. Exactly. You can right -click on almost any web page right now, select View Page Source, and just read the code. So if a developer places an API key, which is a secret password, meant to authenticate access to a massive database of customers into client -side JavaScript, They are quite literally serving that secret password to every single person who

visits the website. That is staggering. I mean, I'm trying to wrap my head around why a developer would ever build it that way in the first place. Usually, it's a matter of convenience, speed, or just a misunderstanding of how third -party tools should be integrated. Like they're just rushing to get it done. Yeah, imagine a marketing team wants a widget on the website to collect emails for a newsletter. A developer writes a quick script to send that email directly from the user's browser straight to the iterable database. Okay. But to do that, the browser needs the key to open the door to iterable. So they put the

key in the script. It works perfectly, functionally speaking. The email gets stored. But security -wise, it's a fatal design flaw. But how does a hacker even find that? Like, are they just sitting there right -clicking on... Thousands of websites all day hoping to spot a password in the code. Oh, not at all. It's completely automated. Really? Yeah. Hackers use bots automated scripts that scour the Internet 24 hours a day, seven days a week. These bots download the client side code of millions of websites and scan them specifically for strings of text that match the

format of an API key. So it's instantaneous. Basically. Once the bot finds one, it flags it. Tests it to see what privileges it has. And then the attackers move in to extract whatever data that key can access. It requires almost zero manual effort on the part of the criminal. Wow. So it's prioritizing convenience over security and just leaving the door wide open for automated looting. Exactly. Now, I know MAG hasn't officially confirmed this specific entry vector yet. They haven't confirmed the 86 gigabytes or the 200

,000 future travel records. But Bleeping Computer didn't just take the hacker. word for it did they no they didn't they actually got their hands on a data sample to verify the claims okay what did they find bleeping computer reviewed a 21 gigabyte data sample of Manchester customer exports, and they managed to validate one traveler's record against their actual real -world purchase history. And it was a match. It was a perfect match. Fast -track purchases, booking and arrival times, the specific terminal, amounts paid, purchase references. Which completely blows Meg's initial,

it's mostly just email addresses framing out of the water. Yeah, it really does. This verified data went so far beyond that. I mean, it included booking references, product selections, prices, discounts. exact parking dates and times, historical spend, and marketing engagement data. The picture of the customer was deeply, uncomfortably rich. It really was. And this raises an important question about the nature of the data itself. Security commentators pointed out something crucial about UK postcodes, which were included in this breach.

Right, because they're different from U .S. zip codes. Very different. In the U .K., a full postcode doesn't just point to a general neighborhood or a massive geographic zone like a U .S. zip code often does. It narrows the location down to roughly 15 addresses. Fifteen. That is basically your exact house. Basically, yeah. Okay, but let me push back on this for a second. Let's play devil's advocate here. How does a license plate or postcode actually help a hacker? Like, unless they are physically at the airport waiting by my car, I just don't see them. leverage. MAG

confirmed no payment or bank data was compromised. So what? What is the actual tangible threat here if they don't have my credit card? That's a great question because we are so conditioned to think about fraud. You know, someone draining your bank account or maxing out your credit card behind your back. Right. But we connect this to the bigger picture. This isn't a fraud story. This is a phishing story. The threat isn't physical theft of your vehicle. It's psychological manipulation of you. Manipulation? How? Okay, so think about

a standard spam email. Dear sir, your account is locked. Right, I delete it instantly. Exactly, because it's generic and your brain recognizes it as a low -effort scam. But now, imagine you're on a beach in Spain and you receive an email that says, there is an issue with the vehicle registered as your exact license plate. Oh, man. You're car -cark booking at Terminal 2 on the 14th of August. requires immediate revalidation to avoid impound fees. Please click here to confirm your payment details. And it includes your exact historical spend, your correct booking reference,

and the specific terminal. See, if I had done an email saying my car was getting towed from Terminal 2 while I'm on vacation, all critical thinking goes out the window. I'd absolutely click that link in a total panic. And that is the exact physiological response they rely on. It triggers an immediate cortisol response. Yeah, you aren't asking, is this a scam? You're just asking, oh, no, did my parking payment fail? Is my car being towed right now? Precisely. Armed with highly contextual data, a scammer creates a scenario that completely bypasses your prefrontal

cortex, the logical, critical thinking part of your brain. Oh. You click the link. You go to a fake page that looks exactly like the airport's payment portal. And that is when you hand over the credit card. Highly contextual data makes phishing almost impossible to spot, even for extremely vigilant people, because it leverages trust. It uses true information to validate a lie. That feels like a massive wake -up call because if Macrae's core IT wasn't re -breached, but they still lost 8 .7 million records, how do companies even begin to plug these holes?

The source material breaks this down into some really hard lessons for the digital age. And it seems like the first major takeaway is that a company's marketing stack is its real attack surface. Absolutely. We often think of cybersecurity as protecting the main servers, the payment gateways, the core infrastructure. The big stuff. Right. Yeah. But every single booking widget. Every email marketing platform, every customer engagement tool, these are all doors into a company's customer relationships. And they're usually managed by marketing, not IT. Exactly. If your marketing

department is plugging in third -party Thos tools without rigorous security audits from the IT department, you are vulnerable. This is actually known as shadow IT. Shadow IT. Yeah. Marketing buys a tool to make their job easier, they integrate it quickly, and security never even knows it exists until it's breached. So the marketing department is accidentally leaving the doors unlocked because they just want the customer experience to be frictionless. But there has to be a technical fix for this specific API key issue, right? Like how do you integrate these

tools without leaving the key under the mat? There is a very standard fix. The cheapest security control in this entire story would have been managing those API keys properly. Instead of putting the key in the user's browser, the client side, you use a server side proxy. Okay, how does a server -side proxy work? In plain English. Just explain the mechanics of that for us. Sure. Instead of your web browser talking directly to the iterable marketing database using the secret key, your browser talks to the airport's secure server. Okay. The secure server, behind

closed doors, uses the secret key to talk to iterable, gets the result, and passes it back to your browser. The key never leaves the locked room. Ah, I see. So the customer never sees the key. They only ever see the result of the action. Exactly. And furthermore, you implement what are called scoped keys and rotate. What are those?

Okay, so even if Hacker manages to steal the valet key, they can't drive the car on the highway or steal the valuables in the trunk. They can only do the very specific limited task the key was designed for, like log in an email address. Exactly. And then you combine that with rotating keys, which means the lock changes automatically every few hours or days. Oh, that's smart. Right. So even if a bot scrapes your key, by the time

the hacker tries to actually use it to extract a database, the key is already dead. If those basic architectural rules had been followed, this breach simply wouldn't have happened. It's frustrating because the solutions are so readily available, but I feel like we should talk about data minimization, too, because MAG did actually do something right here that saved them from a total catastrophe. They did. The ancillary system that was breached simply wasn't allowed to store credit card data. The decision to not store that data alongside the parking and marketing profiles was likely made years ago during the

system's design phase. And thank God for that. Truly. That is the core tenet of data minimization. You cannot lose what you do not keep. If you don't need a piece of data to run a specific service, just do not store it. Because if it had been storing credit cards alongside postcodes, emails, and license plates, the damage would be orders of magnitude worse. Oh, it would be game over. It would be one of the worst breaches of the decade. However, we shouldn't let them off the hook entirely here. Fair enough. Because

under global privacy frameworks like the GDPR in the UK or the notifiable data breaches scheme in Australia, losing an email combined with a postcode and a license plate is still legally considered a significant compromise of privacy. It still counts. It definitely counts. It requires mandatory reporting and carries serious regulatory weight. Which naturally leads into the PR fallout of this whole event. Because MAG came out fast and framed it as mostly just email addresses, they really downplayed the severity early on. They did. And I understand the fog of horror

is real in a cyber incident. You don't always know what you've lost on day one. But the credibility cost of that early framing was brutal. It was. When you communicate early in a crisis, you have to leave room for the story to grow. Because when richer data samples surfaced in the hands of criminals a few days later and were verified by independent journalists, Mag's initial reassurances looked either incompetent or deceptive. Right. If you tell your customers it's just emails and then hackers drop a file with their home addresses and upcoming vacation dates, you lose trust instantly.

Exactly. Over -reassurance costs you credibility exactly when you need it most. So what does this all mean? When we look at this whole story, from the Wi -Fi login to the extortion demands, the underlying theme is that a company's security is only as strong as its marketing department's newest widget. That's the reality we live in. And there is this massive irony here. Companies spend millions of dollars guarding the front door, you know, the payment processors, the core infrastructure, the flight operations. But they leave the side window, the marketing data, the

engagement metrics wide open because they view that data as low risk. And as we've learned today, hackers don't need your credit card to ruin your week. They just need enough context to trick you into giving it to them yourself. The illusion of harmless data is just that it's an illusion. Context is a weapon. Let's do a quick recap. We started with a simple airport Wi -Fi login and followed that thread to an exposed API key sitting in plain sight in a web page's source code, just waiting for an automated bot to scrape it. That single, easily preventable architectural

error resulted in 8 .7 million compromised records, giving cybercriminals a treasure trove of highly contextual data parking dates, license plates, postcodes. It is an absolute masterclass in why every piece of seemingly harmless data matters and why the line between client -side convenience and server -side security is so critical. It really is. And, you know, it's worth reiterating the practical advice MAG gave their customers through all this. What was that? Legitimate companies will never contact you out of the blue asking

for car details, banking information, or passwords. Right. If you get an email about your parking validation or a delayed flight or an impound fee and it demands immediate payment, stop. Breathe. Let the cortisol pass. Exactly. Don't click the link in the email. Never click the link. Go independently to the official website. Type the URL in yourself. And log into your account there, especially when the phishing email looks exactly like a real receipt and knows exactly what terminal you parked in last Tuesday. Independent verification is

literally your only defense against highly contextual phishing. It really is. Verifying the source takes maybe 10 extra seconds, but it neutralizes the entire threat. Well said. Thank you for joining us for this deep dive. We love unpacking these hidden mechanics of the digital world with you, but we want to leave you with a final lingering thought. Think about this one. The next time you're checking out online and you see that little box asking if you want to receive marketing updates or the next time you're sitting at a gate and you trade your personal email for 30 minutes of free Wi -Fi, ask yourself, how many invisible

third -party doors are you opening to your personal life just to save $5? Think about it. See you next time.

Open the transcript file

Hosts and Guests

Nobody is credited on this episode yet.

Credit the people on this episode

Be the first to rate this episode

More episodes

All episodes
  1. Iris Ohyama - A Suspicious File in the Cloud, 7.7 Million Customers at Risk, and an Online Store That Went Dark

    Nov 19, 202620 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...

    Credit the people on this episode

  2. Who Gives A Crap - A Marketing Supplier Breached, Six Days to Tell the Client, and Customer Data That Didn't Need to Be There

    Nov 17, 202619 minAudio

    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...

    Credit the people on this episode

  3. Last Week in Tech - An Outlook Zero-Day That Leaks Your Password Hash, Chrome's Eighth Exploited Bug, and Nvidia Without Jensen Huang

    Nov 15, 202621 minAudio

    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...

    Credit the people on this episode

  4. Chainalysis - From "Non-Sensitive" to "All Users": How a Breach Notice Changed in Five Days

    Nov 12, 202619 minAudio

    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...

    Credit the people on this episode

  5. NSW Health - A Dental Voucher Website, Four Gigabytes Taken, and the Providers Whose Details Were Exposed

    Nov 10, 202623 minAudio

    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;...

    Credit the people on this episode