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

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; Cyber Security NSW declared a major incident, announced 4 November. Police estimate about 4GB was taken, including significant personal identification information about third-party providers (dentists). NSW Health says no patient data has been impacted "at this time". Investigation: Strike Force Civic (NSW Police Cybercrime Squad), with the AFP assisting and contact with the FBI and US DHS; police say suspects appear to be offshore. Cause: not disclosed. Affected numbers: not published. A claimant using the alias ByteToBreach has posted an unverified claim of about 70GB and 100,000 documents, reported by Cyber Daily; police say they have received no demands. Lessons: supplier data matters, "isolated" is only reassuring if you know what is on the system, and have a disclosure plan ready. Visit www.kinsoft.com.au to talk through your security and IT needs. Sources: ABC News (4 Nov 2026); Cyber Daily; Medical Republic; Tech Insider AU.

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.

Imagine the FBI, the U .S. Department of Homeland Security and like international cybercrime syndicates all going to war over a subsidized root canal. Yeah, it sounds completely absurd. Right. It sounds like the setup to a strange techno thriller, but I mean, it is exactly what is playing out right now. Welcome to the Deep Dive. Glad to be here for this one. So today our mission is to dissect this massive stack of sources, internal government statements, police briefings and cybersecurity

threat reports regarding a major incident out of Australia. We're looking at the New South Wales health dental voucher website breach. Which on the surface sounds incredibly niche and, well, low stakes. Exactly. Because what starts in these notes as a seemingly mundane administrative hiccup. very quickly spirals into a global investigation. We want to understand how a low stakes web portal became the center of a massive discrepancy in the official narrative of what was actually stolen.

It really is a textbook case of how modern cyber warfare operates. I mean, it doesn't always announce itself with the targeted spectacular attack on the Pentagon or a massive banking collapse. Right. No explosions. Yeah, exactly. More often than not, it starts out quietly. Usually through the side door of regional health services. To set the stage here based on the sources, the core facts we're looking at begin on Thursday, October 29th, 2026. On that day, NSW Health internally

reported unauthorized access to a very specific system. It's the Oral Health Fee -for -Service Scheme website. And just to clarify for you listening, this is a system that handles vouchers for subsidized dental care in that specific Australian state. But those services aren't delivered directly by the government in some state run clinic. Right. They're delivered through third party providers. Yeah. Private independent dentists out in the community who accept these vouchers. Precisely. And almost immediately upon detecting this unauthorized

access, the authorities were alerted. The matter was handed straight over to the State Crime Command's Cybercrime Squad in Australia, and they launched an active investigation under the operational name Strike Force Civic. Okay, let's unpack this. Because to really understand the severity of this breach, we first have to look at the incredibly suspicious timeline between when the government knew they had a problem and when the public was actually told about it. The gap there is pretty staggering. It is. You mentioned the breach was detected on October 29. But the public... And

get this, according to our notes, even the new South Wales health minister himself, a man named Ryan Park, didn't hear a word about it until days later on November 4. Yes, almost a full week of absolute silence. And during that week of silence, behind closed doors, cybersecurity NSW had formally escalated this to a major incident. Wait, so it met the emergency triggers? It did. It actually met the specific triggers laid out in the state's emergency cyber plan. See, this is the part of the timeline that drives me crazy.

The emergency triggers were met. They knew it was a major incident. But keeping everyone in the dark, it's like coming home to find a burglar in your house and the police telling you to just sit on the couch and pretend you didn't notice them just so they can follow the burglar back to their boss. I have to ask you, is this standard practice? Why keep the public in the dark for nearly a week if those emergency triggers were already hit? Well, it's a great question. And your burglar analogy is actually incredibly accurate here. To answer it, you have to look at this

through the lens of live law enforcement rather than public relations. Okay, how so? When a breach like this happens, you have to remember that a cyber crime scene is incredibly fragile. The police specifically asked NSW Health to control when the breach went public to delay that disclosure because Strike Force Civic's investigation was live. So they were actively watching the hackers? Exactly. They were tracking the threat actor's lateral movement and monitoring their exfiltration nodes. Okay, hold on. Let's translate those terms

for a second. Lateral movement, that's like the burglar getting into the kitchen through a window and then checking all the hallway doors to see if they can get into the bedrooms and the safe, right? That is a perfect analogy, yeah. Lateral movement is how hackers pivot from the initial point of entry to deeper, more sensitive parts of a network. And exfiltration nodes are simply the digital drop points where the hackers are sending the stolen data. Oh, I see. Often, if you announce to the world, hey, we know you're in our system, the threat actors immediately

cover their tracks. Oh, they just wipe everything and vanish. Right. They drop their connections. They wipe the server logs. They destroy the evidence and they vanish. Law enforcement wants that delay so they can monitor the network traffic in real time, see exactly where the data is being sent, and map the attacker's infrastructure. Just to identify the individuals involved before the hackers know they've been spotted. Exactly. I hear that. But using my burglar analogy again, it creates a massive tension. I mean, if you're running a business or a health department, you

are legally required to tell people their house is being robbed. It creates an agonizing tension for organizations. Think about it from a compliance standpoint. Businesses and government agencies have strict notifiable data breaches obligations. By law, in many jurisdictions, if personal data is compromised, you are on a very tight clock to notify the people affected so they can freeze their credit and protect themselves. But then you have the cybercrime squad sitting across the table saying, shh, don't say anything. Exactly. Saying, if you tell the public now, you ruin

our only chance to catch the syndicate. It is a delicate, high -stakes balancing act between legal transparency and criminal justice. And that delayed timeline definitely makes sense if the police are actively tracking the culprits. But it raises an immediate glaring question for me as I look at these sources. What exactly were the police trying to protect and what was actually stolen? Which is where the official story starts to completely fracture. Yes, because when you look at the notes we gathered, we enter this

intense fog of war where nobody seems to agree on the basic facts. The fog of war is the perfect term for it. In the initial aftermath of a cyber incident, the information landscape is totally chaotic. And the numbers you hear on day one are rarely the final numbers you see on day 30. Well, let's look at the numbers we do have. So the official police estimate, the number they put on the record to the press, is that about four gigabytes of data were taken from the server. OK. But then an unverified attacker pops up online using the alias Byte to Breach. And according

to reports by Cyber Daily, this attacker claims they didn't steal four gigabytes. They claim they stole 70 gigabytes of data. Yeah, that is a massive jump. Comprising roughly 100 ,000 documents, which they say they got through a misconfigured subdomain. Right, four gigabytes versus 70 gigabytes. It is a staggering difference. Before we even get to the size difference, you have to explain that entry point. What exactly is a misconfigured subdomain and how does it lead to a breach like this? Think of the main NSW Health website as

the heavily guarded front door of a fortress. It's got the best locks, the security cameras, the alarms. Right. But a health department is massive, so they create subdomains, like smaller specialized offshoots of the main website for specific tasks. For example, a portal just for dentists to upload vouchers. Oh, I see. Like a side door. Exactly. A misconfigured subdomain is like a forgotten service entrance in the back alley that someone left propped open during renovation. The IT department might have spun up the subdomain

for a specific testing phase or a specific vendor and simply forgot to apply the same rigorous security protocols that protect the main site. Wow. And hackers just find that. Yeah. Hackers run automated scanner 24 -7 across the entire internet just looking for these exact propped open back doors. That makes sense. But it still doesn't explain the math. How can the police say the hackers walked out with four gigabytes, but the hackers are claiming they walked out with 70 gigabytes? That is a 66 gigabyte discrepancy. Like, is someone just outright lying? Well, it

usually comes down to a mix of technical reality and hacker economics. Technically, the police may be looking at the size of the highly compressed database files that were exported. Oh, so zipped files are tiny. Exactly. When data is compressed for storage, it's very small. And but when the hacker unzips that data to read it, especially if it contains thousands of raw PDF invoices, scanned dental licenses or image files, that uncompressed data footprint explodes in size. Four gigs of compressed text can easily become

tens of gigs of readable files. So the police are weighing the tightly packed suitcase and the hackers are measuring the clothes once they are thrown all over the bed. That's it exactly. But there's also the economic angle. Hackers operate in a marketplace. Byte to Breach is trying to sell this data. Oh, so they inflate the numbers for marketing. Yeah. If you are selling stolen goods on the dark web, you are absolutely going to inflate your claims to make the cash sound more valuable. Claiming 70 gigabytes and 100 ,000 documents is a marketing tactic to drive

up the asking price from identity brokers. That is wild to think about hackers having their own marketing spin. But it's not just the volume of data that's disputed in our notes. I want to point out a glaring contradiction in how the official government sources are describing what was inside that data. Oh, the PII issue. Yes. On one hand, you have the Cybercrime Squad commander, the person leading the police response, going on the record to say that a, quote, significant amount of personal identification information about third party providers was taken. A significant

amount of PII. Which is a very strong, very specific legal phrase in the cyber world. PII, things like driver's licenses, tax file numbers, banking details, is the absolute goldmine for identity theft. Right. But then out of the other side of the government's mouth, you have eHealth NSW, the administrative body, minimizing the whole thing. Their public statement described the stolen data as just a, quote, small number of details about providers that were potentially sensitive. Yeah. How can it be both a significant amount of PII. And a small number of details. Who is

spinning the truth here? What's fascinating here is that you are watching two entirely different institutional mandates collide in real time. You are watching crisis PR go head to head with law enforcement realities. So eHealth is just trying to stop a panic. Exactly. eHealth NSW is in crisis management mode. Their primary goal is to prevent public panic, maintain trust in the health system, and minimize reputational damage. So they use soft, mitigating language. Small number. potentially sensitive. Downplaying

the severity so people don't grab their pitchforks and demand resignations. Right. But the cybercrime squad, they don't care about eHealth's PR problem. They are building a criminal case. If they see even a few gigabytes of driver's licenses, tax file numbers, or business banking details belonging to dentists, they have to call it what it is, a significant amount of PII. Wow. So they're categorizing evidence for a judge. Exactly. So it's not necessarily that one side is outright lying, but they are framing the exact same data

through radically different lenses to serve their own institutional goals. But what about the patients? If you're listening right now and you live in that area, your first thought is your own medical records. The official statements emphasize that no patient data has been impacted. Ah, but you have to read the fine print. Listen closely to the specific wording authorities use in these situations. They didn't just say patient data wasn't impacted. They said no patient data has been impacted, quote, at this time. At this time.

I saw that highlighted in the notes. It feels like a massive caveat. It is the classic institutional hedge. At this time is the ultimate get out of jail free card for corporate and government communications. Because they might find something tomorrow. Exactly. It means, based on the server logs we've had time to review in the last 72 hours, we haven't seen patient data leave the building. But cyber forensics takes months of combing through millions of lines of code. So they could realize next week that patient data was swept up too. Yep. They might look at a different server next week,

track the hacker's lateral movement, and realize actually patient data was impacted. It allows them to sound definitive today without legally perjuring themselves tomorrow when new evidence surfaces. Okay, so if we assume for a moment that patient data is theoretically safe, at least, you know, at this time, and the primary focus of the breach is squarely on these third -party providers, the dentists themselves, we have to look at why these specific professionals are being targeted and who is doing the targeting.

Because the profile of the response does not match the profile of a small -time local hacker missing around in their basement. Not even close. Here's where it gets really interesting. According to the police, the suspects appear to be located entirely outside of Australia. They've also confirmed this isn't some automated AI script just guessing passwords. There are human hands on keyboards actively navigating the system. But despite this being an attack on a regional health website in one Australian state, the Australian federal police are assisting. More than that, local police

are actively in contact with the FBI and the U .S. Department of Homeland Security. Which is a massive escalation of resources for a voucher website. That's what I'm saying. If you look at this on paper, it's like calling in an international SWAT team to investigate a local pharmacy break -in. If this is just a regional NSW... Dental scheme. Why are the FBI and Homeland Security getting involved? What do they care about a few dentists in Sydney? Because cybercrime is fundamentally borderless. The Internet doesn't care about municipal jurisdictions. When an attack hits government

infrastructure, even an isolated server for a seemingly low stakes dental scheme, the tactics, the malicious code, the IP addresses and the exfiltration methods often reveal the fingerprints of established, highly organized international cyber syndicates. Exactly. So the FBI isn't there for the dentists. They're there for the hackers. Precisely. The FBI and Homeland Security track these global syndicates constantly. If a threat actor group based in, say, Eastern Europe or Southeast Asia uses a specific exploit on a server

in New South Wales today, there's a very high probability they are going to use that exact same exploit on a hospital in Chicago or a water treatment plant in Texas tomorrow. Wow. So it's like a beta test for them. Right. International law enforcement agencies share intelligence because a breach in one country is often the beta test for an attack in another. That makes total sense. They're tracking the weapon, not necessarily the specific victim. But there's another detail in our notes that feels like a missing puzzle piece. OK. The police explicitly stated that

they have received no ransom demands. Nobody has sent an encrypted email asking for millions of dollars in Bitcoin. Why go through all the trouble of infiltrating a government server, extracting all this provider data and then crickets? Well, a lack of a ransom demand early in an investigation can imply several different and frankly troubling things about how the dark web economy operates. Option A is that they are just waiting. Waiting for what? Sometimes attackers exfiltrate the

data. secure their backdoor access so they can't be kicked out, and then take their time parsing and analyzing what they've stolen. They want to calculate exactly how much the data is worth and how much pain it will cause before they send the ransom note. They want maximum leverage. Okay, so a delayed shakedown. What's option B? Option B is that their motive isn't extortion. It's commerce. The hackers who break into the system often called initial access brokers, have no intention of talking to the NSW government.

They just want to sell the data directly? Exactly. Instead, they take that 4 gigabytes or 70 gigabytes, and they immediately break it into packages and sell it on the dark web forums. Identity brokers will pay top dollar for verified PII of high -income professionals. Oh, because dentists have great credit scores and business loans? Think about it. A dentist's identity is incredibly valuable. They have excellent credit scores, business banking lines, and high loan approval rates. The hackers don't need a ransom from the

government if they can just quietly sell the database to other criminals for a guaranteed profit. That is terrifying. It is. It's like stealing a car and stripping it for parts to sell to a dozen different shop shops before the owner even knows it's missing from the driveway. And then there's option C, which is that the motive isn't purely financial at all. Sometimes state -sponsored actors like... Hackers working for foreign intelligence agencies will target regional infrastructure just to map the network, test the response times of the local authorities or find weak links. Weak links that could eventually

give them a bridge into more critical classified government systems. Exactly. Now, there is no direct evidence in the sources pointing to state sponsored activity here. But when the FBI and Homeland Security get involved, you can guarantee they are running down every single one of those possibilities. Which provides a really harsh reality check. We have an incredibly sophisticated, potentially international attack levied against a relatively small provider database. So what does this all mean? It's a huge shift in tactics. Well, authorities really went out of their way

to reassure the public by stating over and over again in these press releases that the compromised server was an isolated server. They promised that no other NSW agencies were affected. No clinical services were at risk. I want to push back on that reassurance. They keep bragging that it's an isolated server. Doesn't that mean their security architecture actually worked? They successfully contained the blast radius? If we connect this to the bigger picture, relying on the phrase isolated server to calm the public is a bit of a sleight of hand. How so? Yes, from

an architectural standpoint, having segmented networks is good security hygiene. It means the fire didn't spread from the garage to the rest of the house. But an isolated server only provides genuine reassurance if you know exactly what is on it. Right. If you put all your most valuable jewelry in a lockbox and the lockbox is completely isolated from the rest of the house, if a thief steals the lockbox, it doesn't matter that the rest of the house is safe. They got the gold. That is exactly the point. In this case, the highly valuable supplier and provider data, the

detailed personal information of dentists participating in this government scheme, was sitting right there on that isolated server. The hackers didn't need to breach the entire health department network. They found an isolated pocket of high -value data, and they took it. So if you're listening to this right now, what is the main takeaway? Even if you live halfway across the world and have nothing to do with Australian dental vouchers, why should the average person care about this? The main lesson is that hackers are aggressively shifting their tactics toward what we call supply

chain attacks. Supply chain attacks? Yeah. For years, massive organizations have been fortifying their front doors, securing patient databases, locking down customer credit card portals. Because those giant front doors are getting harder to kick in, attackers are looking for the side windows. Even when the news headline is about a massive health system breach, the real targets are increasingly the suppliers, the contractors, and the third -party providers. The vendors. The people doing business with the government or the giant corporation.

Precisely. If you are a dental provider on this scheme, or frankly, any small business contracting with a larger entity, you now need to be hypervigilant. Hackers know that an independent dental clinic likely doesn't have a dedicated cybersecurity team monitoring their network 24 -7. Right. So, the hackers steal your details from the government portal, then they use those highly specific verified details to launch devastating spear phishing payloads against your clinic. And for anyone unfamiliar, a spear phishing payload isn't just a generic spam email. It's a highly targeted

weaponized email that looks exactly like it's coming from a legitimate source because the hackers have all your internal info. Exactly. They can impersonate the government health department using the exact voucher terminology they stole. They trick your front desk staff into clicking a malicious link and suddenly they have access to your private clinic network. Oh, wow. Or worse, they use the dentist's trusted credentials to send a payload back into the main government network, bypassing all the heavy security because the system thinks it's just a trusted vendor

logging in. It's a cascading effect. You start by compromising the voucher system and you end up compromising hundreds of individual businesses and then potentially using those businesses to hack back into the main system. Exactly. Supplier and provider data is a primary target now. It is the new frontier of cybercrime. The days of only worrying about the central database are over. It is wild how quickly a story can shift when you peel back just one layer. We started this deep dive looking at a localized Australian

dental voucher breach, a story about administrative web portals, misconfigured subdomains, and subsidized root canals. Just everyday administrative stuff. And within minutes, we are dissecting a global cyber investigation involving conflicting narratives over data compression, dark web identity brokers, and the involvement of the FBI and Homeland Security. It really highlights how interconnected and fragile the digital supply chain truly is. It does. And if you think about it, this raises an important

question for you to mull over after we sign off today. Okay, what's that? We've seen throughout this deep dive that third -party suppliers, like local independent dentists, are becoming primary targets because they hold lucrative data but might lack enterprise -grade security. Right. If local businesses are the new backdoor into critical government infrastructure, is it even possible for a massive health system to truly secure its borders? Or is a massive digital network only as secure as its least tech -savvy contractor? That is a chilling thought to leave on. A multi

-billion dollar health network brought to its knees by a misconfigured server handling dental vouchers. It really makes you rethink what a low stakes target actually looks like. Absolutely. Thank you for joining us on this deep dive. Keep questioning the narratives. Keep looking at what they aren't telling you. And we'll catch 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. Last Week in Tech - A Brutal AI-Driven Tech Sell-Off, a Perfect-10 Siemens Flaw Under Attack, and Cisco's Exploited VPN Bug

    Nov 8, 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, 30 Oct to 6 Nov 2026. US tech stocks sold off hard on Thursday 5 November: the Nasdaq Composite...

    Credit the people on this episode