Latest / Decrypted: The UK Cyber Briefing / Manchester Airports: the master key was sitting in the browser all along
Transcript
- 0:03This is Decrypted. Monday, the thirty-first of August.
- 0:07Manchester Airports: the master key was sitting in the browser all along.
- 0:14Manchester Airports Group's data breach, first disclosed on 27 August, has got bigger and clearer this week.
- 0:23A group called FulcrumSec, which is trying to extort the company, has claimed responsibility.
- 0:29It's published sample records that go well beyond the "mostly email addresses" M A G described at the time.
- 0:37And it's said exactly how it got in: airport-specific credentials for the marketing platform Iterable, left e
- 0:45xposed in client-side JavaScript.
- 0:47M A G hasn't disputed the technical claim.
- 0:51It's only disputed the scale.
- 0:53BleepingComputer independently validated at least one sample record against a traveller's own booking history
- 1:01. And the company says it refused to pay a ransom.
- 1:04Next. The key wasn't stolen, it was published.
- 1:10So what does "exposed in client-side JavaScript" actually mean?
- 1:15Here's the plain-English version.
- 1:18When your browser loads a website, it downloads the code that runs the page.
- 1:24And that code is fully visible to anyone who opens developer tools, a feature built into every browser.
- 1:30If a developer embeds an A P I key in that code, so the page can talk to a third-party service, they haven't
- 1:38hidden the key. They've published it.
- 1:40To every visitor, indefinitely.
- 1:43It's the digital equivalent of taping the stockroom key under the till, and calling the shop secure because
- 1:51customers aren't supposed to look under there.
- 1:53FulcrumSec says the credentials it found unlocked a consolidated customer export.
- 1:59Booking references. Fast Track purchases.
- 2:03Terminal and arrival times.
- 2:05Parking dates. And roughly 200,000 records tied to travel still to happen in 2026.
- 2:13Think about what that means.
- 2:16Combine a name with an upcoming flight date and terminal, and you have everything needed for a convincing "yo
- 2:22ur booking has a problem" phishing message.
- 2:25No payment card data has surfaced in samples reviewed so far.
- 2:30That's the one piece of good news in an otherwise uncomfortable update.
- 2:33And finally. Rebuilding trust needs more than a statement.
- 2:38The Secure by Design lesson here isn't about M A G's competence relative to peers.
- 2:44Plenty of sites do this. It's that a credential embedded in anything shipped to a browser should be treated a
- 2:51s public from the moment it's written, not from the moment someone notices it.
- 2:56The fix is architectural, not procedural.
- 2:59Third-party A P I calls that need a secret should be brokered server-side.
- 3:05The browser talks to your own backend, and the backend holds the real key.
- 3:10Where a client genuinely needs to call a service directly, the token issued should be short-lived, scoped to
- 3:17the minimum action required, and rotated automatically.
- 3:21That way, finding it in a page's source code buys an attacker very little.
- 3:25Secret-scanning in the build pipeline would have caught this before it reached a single browser.
- 3:30Run it before code ships, rather than after a researcher emails you.
- 3:35And if you're a UK organisation running customer-facing marketing or booking integrations, this is worth an
- 3:42afternoon. Check your own bundles, rather than assuming it's someone else's mistake.
- 3:48That was Decrypted. The written version and every source are linked in the show notes.
- 3:53Thanks for listening.