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

Quest Apartment Hotels - 1.5 Million Guest Records, and the Attacker Who Never Touched Quest's Systems

Sep 1, 202621 minAudio

Got something to say to this podcast? Send a voicemail, and you might hear yourself on the next episode! Quest Apartment Hotels - 1.5 Million Guest Records, and the Attacker Who Never Touched Quest's Systems A deep-dive into Australia's biggest hospitality breach of 2026 - and the vendor-ecosystem attack pattern behind it. On Monday 17 August 2026, Quest Apartment Hotels - 160+ properties, founded in Melbourne in 1988, majority-owned since 2017 (and fully since 2022) by Singapore's The Ascott Limited - identified unauthorised access to a database system. The entry point wasn't Quest's own network: the company says access arose "from a vulnerability through a third-party service provider" holding Quest guest data. Two days later, on 19 August, Quest disclosed publicly and emailed affected guests under the signature of Ascott Australasia managing director David Mansfield. What was taken: records predating June 2025 - full names, email addresses and contact details, street addresses in some records, and a small number of dates of birth. No financial or payment card data. Quest hasn't published a number; ACS Information Age reports more than 1.5 million records were potentially involved. What we don't know: the vendor's identity, the specific vulnerability (no CVE published), and how the attacker got in - Quest has declined to answer. No threat actor has claimed responsibility and no ransom demand is public. The response: containment and remediation completed before disclosure; OAIC, ACSC and other authorities notified; external cyber and privacy advisers engaged; all affected guests contacted. In this episode: Why the vendor ecosystem is now the preferred way in - and how this breach follows Origin Energy, Partnered Health and Lifeline in a bruising winter for Australian data holders - The phishing second wave: why names + contact details + dates of birth are "the raw ingredients for convincing phishing and identity fraud" (Kash Sharma, BlueVoyant) - Five lessons for Australian businesses: map the vendors that touch your customer data; treat data retention as attack surface; know your Notifiable Data Breaches obligations; contract for security before the incident; and warn customers about branded scams that follow Visit www.kinsoft.com.au to talk through your security and IT needs. Sources: ABC News (19 Aug 2026); Information Age / ACS (19-20 Aug 2026); The Register (19 Aug 2026); Cyber Daily (20 Aug 2026); SmartCompany; Australian Cyber Security Magazine; Quest Apartment Hotels statement; 7NEWS.

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 this custom deep dive crafted entirely for you. Today, our mission is to explore this massive, honestly, incredibly revealing data breach involving Quest apartment hotels. Oh, yeah. A huge one. Right. Like they have been an absolute staple of the Australian, New Zealand and Fijian travel landscape since what? 1988. Yeah. And we are looking at an incident where over 1 .5 million guest records were just exposed. We're pulling our insights today primarily. from a phenomenal, really in -depth report by Tech

Talks with Kinsoft. So, OK, let's unpack this, because the real paradox we are trying to solve today is, well, this. How does a massive modern company suffer a catastrophic data breach when the attackers never even touch the company's own IT systems? I mean, it really is the defining security puzzle of our era right now. Yeah. And that's exactly why this isn't just a story about a single hotel chain, even one as massive as Quest, which was fully acquired by the Ascot Limited a few years back in 2022. Right. This is a critical case study for you, for anyone listening, really, because your data is currently

just floating across the modern vendor ecosystem. Out there. Exactly. Every time you interact with a business, your personal information doesn't just sit in some isolated, impenetrable silo. It gets passed along to this sprawling, often completely invisible web of third party vendors. So to really understand how this happens, I want you to imagine that you have just built the ultimate fortress. Like you have outfitted your house with a state of the art security system. The best money can buy. Exactly. You've got. Biometric

locks on the front door, laser trip wires in the hallway, reinforced glass on every single window. You have spent an absolute fortune making sure absolutely nobody is getting through your front door. Right, and you feel completely safe because you control that perimeter. Your whole IT budget went entirely into building those walls. But then, you know, you have a contractor coming over to fix the plumbing. You need them to do their job, obviously, so you hand them a copy of your key to get in. And what does the plumber do? Weaves it in the truck. They leave that key sitting right on the dashboard of their unlocked truck while they go inside a cafe to grab lunch.

So the thief walking down the street, they don't need to break down your reinforced door. They don't need to hack your expensive alarm system or bypass the biometrics. They just reach right through the window. Right. They just reach through the open truck window, pick up the key from the dashboard, stroll up to your fortress and literally just walk right in. And suddenly millions of dollars in corporate security infrastructure are rendered. completely useless by a single vendor's oversight i mean the strongest front door in the world simply does not matter if your

partner leaves the side door wide open yeah and that brings us to the actual timeline of how this uh this side door breach played out for quest and the speed of it is honestly breathtaking compared to how these incidents usually drag on for months oh absolutely So on Monday, August 17th, unauthorized access is officially identified. But to your point, the attacker didn't breach Quest's servers. They compromised a third -party service provider. An unnamed vendor, yeah. Yeah, an unnamed vendor running a database that just

happened to hold Quest's desk data. The side entrance. So once that vendor systems were compromised, the threat actor essentially had a clear, unobstructed hallway straight into those guest records. The fortress walls were entirely... But here's the pivot that really stands out. By Wednesday, August 19th. Which is incredibly fast. Literally just 48 hours later. Quest had apparently contained the incident. published a detailed statement on their website, and their managing director

for Australasia, David Mansfield, was already sending direct emails to the affected guests. That's right. Like people were waking up to these notifications overnight. That is a massive operational pivot in just two days. It is an incredibly rapid response, and they deserve credit for that. But to truly understand the gravity of what happened between that Monday and Wednesday, we have to look closely at the scale and the specifics of the data that walked out the door. Okay, let's get into it. So we are talking about historical records dating from before June 2025. The data

fields include full names, email addresses, contact details, and in some cases, physical street addresses and dates of birth. Wow. Now, there is a massive caveat that Quest was very quick to establish, which is that no financial information or payment card details were involved. OK, hold on. Let's pause on the numbers for a second before we get into the actual data itself. I actually read a headline from a secondary news site claiming one. 1 .7 million records were stolen. Ah yeah I saw that too. So why the discrepancy? Are we actually sure how much data is floating around

out there? Well the 1 .7 million figure was circulating early on. The most thoroughly sourced figure we have comes from the Australian Computer Society's Information Age, which puts the count at around 1 .5 million guest records. Okay, 1 .5 million. Right. And it's a vital distinction in the industry to differentiate between raw database records and unique individuals. Like one person might have multiple overlapping records if they stayed there a lot. But however you slice the data, we are talking about well over a million people whose personal details have been compromised.

I have to challenge the severity of this, though. Like you mentioned Quest confirmed zero financial data was involved. No credit cards, no banking details, no payment histories. Right. Nothing like that. So why is this considered such a massive deal for the listener? I mean, if a hacker doesn't have my credit card number, isn't this just a digital nuisance? They get my name and my email. Annoying, certainly, but. Is it actually a crisis? Well, if we connect this to the bigger picture, it is absolutely a crisis, just a completely different kind of crisis than the one we have

been trained to fear. Kash Sharma, the Asia -Pacific managing director at the security firm Blue Voyant, breaks this down perfectly in the Kinsoft report. He explains that names, contact details, and dates of birth are not harmless trivia. They are the raw ingredients for highly convincing identity fraud and targeted phishing campaigns. The raw ingredients. I love that analogy. It's like a thief breaking into your house and raiding the pantry. Exactly. They don't have the fully baked cake yet, meaning they don't have direct immediate access to drain your bank account.

But they have the flour, the sugar and the eggs to bake one themselves. That is the exact mechanism at play. Let's look at how we usually spot a scam. You get a generic email. The formatting is slightly off. There are spelling errors and it addresses you as. Dear customer. Yeah, straight to the trash. Right. Your brain instantly flags it as suspicious and you hit delete. But now, put yourself in the shoes of someone receiving a phishing email powered by this specific database. The email knows your full legal name. It knows your date of birth. It has your home street address

sitting right in the footer. And it references a specific time you stayed at a Quest property before June 2025. That changes the psychology entirely. If I get an email that says, urgent, we noticed an overcharge on your recent stay at this specific property. Please click here to claim your refund. And it verifies my identity using my actual home address. My guard is totally down. Most people's would be. I would probably click that link. Because the attacker has successfully hijacked the context of trust, they are no longer

just blasting out generic spam hoping someone clicks. They are crafting a hyper -specific narrative that aligns perfectly with your lived reality. Right. They can send fake Quest -branded booking confirmations, loyalty program verifications, or even urgent security alerts asking you to reset your password, which, of course, just hand your password directly to them. That is terrifying. And we have to consider how broad this net really is, because you're saying I could have booked a room through an aggregator like Expedia, Wotif, or Booking .com. I might never have once visited

Quest's actual website or spoken to their front desk, but because they service the room, my data ends up in this vendor's database, and now it's just in the wind. Exactly. The supply chain of data means you don't even need a direct relationship with the company to be caught in their breach. And this introduces the concept of the second wave. The second wave. Yeah, the true devastating harm of a breach like this almost never happens on day one. On day one, the data is simply extracted and sorted. The real damage arrives weeks, sometimes

months later, as a secondary wave of branded phishing. Wait, why the delay? Why not attack immediately while the data is fresh and they just stole it? Because attackers are strategic. If they launch fake Quest emails on August 20th, right when Quest is warning everyone about a breach, the victims are on high alert. I thought that makes sense. The attackers wait until the news cycle fades, until people have completely forgotten about the warning email they got from David Mansfield. When that second wave hits in late September or October, the urgency of the initial breach is gone, and the phishing trap is infinitely more effective. Here's where it

gets really interesting to me. We know how the data is weaponized. We understand the mechanics of the phishing. But we have absolutely no idea who is doing the weaponizing. The criminal side of this story is a completely blank page. The silence surrounding this specific incident is perhaps the most unsettling part of the entire Kinsoft report. It is entirely a ghost town. The third party provider. Unnamed by Quest. The specific vulnerability they use to get into this system. There is no published CVE. And that's

rare. Right. For anyone unfamiliar with the term, CVE stands for Common Vulnerabilities and Exposures. It is basically the cybersecurity industry's official public catalog of known software flaws. When a piece of software is broken, it gets a CVE number so everyone knows to patch it. But there's nothing here. There is no CVE here. No threat actor has jumped onto a dark web forum to claim responsibility for the hack and there have been no public ransom demands. Major news outlets like the ABC and the Register have repeatedly asked questions and they are just getting crickets.

We need to look at why that absence of a CVE is so crucial. When there is no known software flaw being exploited, it usually means the attackers didn't need to write complex code to break down a digital wall. The plumber's key. Exactly. It heavily implies they just walked in through an open door. They likely used social engineering against an employee at that third -party vendor. Or, you know, they bought stolen administrative credentials on the dark web. They logged in as an authorized user. Wow. That is why Quest Fortress didn't trigger any alarms. The system saw someone

using the plumber's key and assumed everything was totally fine. And that silent, stealthy approach perfectly reflects the shifting tactics in the broader cyber landscape. The report notes this Quest incident did not happen in a vacuum. It is part of what Kash Sharma calls a bruising winter for Australian data holders. The pattern is undeniable. Over just a few months, we saw the Origin Energy breach affecting around 900 ,000 customers. We saw the Pardoned Health breach. We saw the Lifeline staff data breach. A bruising winter indeed. It feels relentless. But how do

those incidents connect to Quest? Are they all using the same broken software? Not necessarily the same software, no, but they're all victims of the exact same architectural flaw. What Sharma identified is that attackers are actively abandoning the heavily fortified front doors of massive corporations. Right, because it's too hard. Yeah, they know companies like Quest, Origin, Energy, and Lifeline have enormous multi -million dollar security budgets. Yeah. It is too hard and too expensive to hack them directly. So instead,

the attackers map out the target's vendor ecosystem. They look for the weak link. They hunt for a smaller, less resourced third -party provider, maybe a marketing analytics firm, a booking engine, or a specialized HR software that just happens to hold the data for these giants. They strike the soft underbelly. Precisely. They strike where security budgets are lower and visibility is at its absolute weakest. Which means, for you listening, the entire concept of a security perimeter has completely fundamentally changed. It is no longer a wall around an AUKUS building. It is

a sprawling, invisible web of contracts. Yep. And recognizing that this vendor ecosystem is the new battlefield, we need to transition into how businesses and individuals actually survive this reality. The Kinsoft report explores several core themes. And honestly, even if you aren't running a multinational hotel chain, understanding this dynamic changes how you should view your own digital footprint. The first glaring reality we have to confront is that in the eyes of the public, the vendor's breach is your breach. It

feels incredibly unfair from a business perspective. I mean. Quest's internal IT team didn't fail. Their servers weren't compromised. No, they weren't. But Quest's logo is the one plastered across all the headlines. They are the ones wearing the reputational damage and the loss of consumer trust. And they are the ones facing regulatory scrutiny from the Office of the Australian Information Commissioner, the OAIC. Because accountability cannot be outsourced. You can hire a vendor to manage your databases. You can outsource your server hosting to the cloud. But the trust your customer placed in you when they handed over

their personal details. That remains entirely your responsibility. So if a company is ultimately holding the bag for their vendors, it completely reframes the conversation around data hoarding. Like we mentioned earlier that the stolen data was entirely from before June 2025. It was historical data just sitting there. Just waiting. But wait, we've been told for a decade that data is the new oil, right? Companies are instructed to collect everything, keep everything forever, use it for AI training, use it for targeted marketing. Are

you saying the fundamental business model of the last decade is now a massive security flaw? What's fascinating here is the tension between marketing and security. Marketing departments want to keep a 10 -year -old booking record because they might want to send that customer a promotional email someday. Right. But security teams look at that 10 -year -old record and see nothing but liability. Storage might be incredibly cheap, but the cost of losing that data is astronomical. As the source material bluntly states, personal information cannot be reset like a password.

Right. Like if a hacker steals my Netflix password, Netflix forces a system -wide reset, I type in a new one, and the crisis is over. five minutes. But if they steal my date of birth and my home address, I can't exactly call up the government and say, hey, I need a new birthday. Mine got leaked in a vendor breach. No, you can't. And that permanence is why data retention is an attack surface. The longer you hold on to data you don't actively need, the wider your attack surface becomes. The golden rule for modern organizations has to be. If you do not actively need that specific

piece of data to serve the customer today, delete it. Delete it. Every gigabyte of unnecessary historical data sitting in a vendor's bucket is a loaded weapon pointing directly back at your brand. So if a marketing department refuses to let go over that old data and a vendor eventually gets compromised, who actually steps in to hold them accountable? That brings us to the regulatory reality, the Notifiable Data Breaches Scheme, or NDB. Right. The NDB scheme is the legal framework governing this exact scenario in Australia. If

you are a business with over $3 million in annual turnover, or even a smaller business operating in specific sensitive sectors like health providers, this law applies to you. You have a strict legal obligation to assess suspected breaches and formally notify both the OAIC and the affected individuals. Just to give you context on the sheer scale of how often this is happening, the OAIC received over 1 ,200 breach notifications last year alone. Let that sink in. That is more than three times a day, every single day of the year, that an

Australian company had to put their hand up, contact the government and say, we lost our customers' data. It is a staggering volume. But this is exactly where the Kinsoft report praises Quest. When you are one of those 1 ,200 companies having a very bad week, the playbook matters. Quest detected the issue on Monday and disclosed it by Wednesday. Which we said is huge. And crucially, they did not bury the notification in dense legal jargon designed to protect the company's liability. They sent direct plain English warnings to their guest. They explicitly included scam warnings

so customers knew what to look out for. It's the gold standard for incident response. But ideally, you want to solve the problem before you ever have to draft that plain English apology. which means we need to talk about how companies actually manage these vendors. This raises an important question. When is the right time to secure your vendor contracts? I'm going to guess it is definitely not after a journalist calls you asking about a data leak. Definitely not. The time to establish your defenses is during the procurement phase, before the contract is

ever signed. Quest noted in their statement that they are working closely with their provider on remediation. But the source material emphasizes that you cannot rely on trust. Nope. You must bake security directly into the legal agreement. You need to establish audit rights, mandate strict breach notification deadlines, and legally require minimum security controls. What does an audit right actually look like in practice, though? It means you have the contractual authority to demand proof that the vendor is doing what they promised. You can demand to see their SOC 2 compliance

reports, which are independent audits of their security practices. You can require them to undergo regular penetration testing, where ethical hackers try to break into their systems to find flaws before the bad guys do. If you wait until a breach happens to ask how a vendor secures your data, the data is already gone. And once the data is gone, we arrive at the final and I think most proactive strategy for dealing with the public. We talked about the devastating second wave of branded phishing. How does a company actually stop that from working? You have to fundamentally

change how you communicate with your customers. You have to tell them exactly what you will and won't ask for in the future. Immunizing the customer base. So if Quest sends an email stating, we will never email you asking you to confirm your password, and we will never send you a direct link to input credit card details for a past stay, they instantly blunt the weapon the attackers just stole. Exactly. When the customer receives that highly convincing, hyper -targeted fake email a month later, it contradicts the rules Quest established. The customer remembers the warning, they pause, and they don't click the

link. It empowers the individual, shifting them from being a passive victim of a data breach to an active participant in their own digital defense. So, what does this all mean for you? When we step back and look at this entire timeline, the rapid Monday to Wednesday response, the theft of the raw ingredients for identity fraud, the completely silent threat actors bypassing the fortress, and the absolute critical necessity of wrangling your vendor contracts, the core takeaway for anyone operating in 2026 is crystal

clear. Yep. Your company's security perimeter is only exactly as strong as the least secure vendor holding your data. It absolutely does not matter how thick your vault door is if the guy you hired to polish the vault has a habit of leaving the combination on a sticky note. on his desk. That is the inescapable architectural reality of the modern vendor ecosystem. And for you, the listener, whether you are managing risk for a massive corporation or just trying to manage your own personal life online, this entire incident reinforces the absolute necessity of critical

thinking. Absolutely. Quest contained this specific incident swiftly and their playbook was solid. But the genie is permanently out of the bottle for those 1 .5 million records. That data is out there circulating in the dark, which means you must question every unexpected digital interaction. You have to. If an email creates a sudden sense of urgency, if it asks you to verify something, even if it has your actual home address and your exact date of birth paused, close the email, go directly to the company's verified website yourself. Never trust the context provided in

the message. It is all about keeping that guard up constantly. But I want to leave you with a final lingering question to ponder on your own. We talked extensively about how personal data, your legal name, your date of birth, your physical history cannot be reset like a password. Yet we generate so much of this highly sensitive data every single day just to exist in modern society. Building on the report's point that this data is unchangeable, what happens when our digital footprint inevitably outlives the companies that initially collected it? That's a scary thought. Right. Will the digital ghosts

of our old hotel stays, our long -canceled software subscriptions, and our forgotten online purchases become permanent, unchangeable liabilities? Are they just sitting in unknown, bankrupt vendor databases? waiting to be weaponized decades from now, it is a wild, unsettling thought to navigate. Thank you so much for joining us on this deep drive. Stay curious, stay vigilant, and always watch out for those side doors.

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