I literally just finished writing about how ShinyHunterz walked off with a petabyte of TELUS Digital’s data yesterday, and my coffee hadn’t even gone cold before this Tieu Dental breach alert hit my feed. Another day, another healthcare organization leaking sensitive patient data because some ass-clowns decided cybersecurity was someone else’s problem. Jesus Christ on a network cable—when will these fucking idiots learn that dental records are just as valuable to attackers as medical histories?

What happened — According to Lynch Carpenter’s investigation notice released March 18, 2026 at 09:11 ET, Tieu Dental is facing claims of a possible patient data disclosure. While the full scope remains under investigation, the breach notice confirms unauthorized access to patient information occurred. Dental practices like Tieu Dental hold exceptionally sensitive data: full names, dates of birth, addresses, insurance information, treatment histories, and in many cases, Social Security numbers tied to medical billing. This isn’t just about cavities and cleanings—we’re talking about information that could enable medical identity theft, insurance fraud, and targeted social engineering attacks against vulnerable patients.

Why it matters — Healthcare providers continue to be prime targets because attackers know the operational pressure to pay ransoms or settle claims is immense. When a dental practice’s systems are compromised, patients can’t get appointments, records become inaccessible, and trust evaporates overnight. Unlike credit card numbers that can be canceled, dental and medical histories are permanent liabilities. A patient whose HIV status or psychiatric treatment details get leaked has no way to “rotate” that information like a compromised password. The downstream consequences—fraudulent insurance claims, blackmail, reputational damage—can follow victims for decades.

What went wrong — Again, it’s the same old story: inadequate access controls, unpatched systems, and a fundamental failure to treat patient data as the crown jewel it is. Dental clinics often operate on shoestring IT budgets, legacy software that can’t be updated without breaking critical workflows, and a dangerous misconception that HIPAA compliance equals security. Spoiler alert: checking a box on a compliance form does nothing when threat actors are actively exploiting unpatched vulnerabilities in your outdated practice management software. The attackers didn’t need sophisticated zero-days; they likely walked in through phishing emails or known vulnerabilities that had patches sitting ignored for months.

The Fix — Fixer’s Advice — Here’s what you do if you run a dental practice, healthcare clinic, or any organization handling sensitive patient data:

1. Encrypt patient data at rest and in transit—yesterday. If your practice management software doesn’t support AES-256 encryption for databases and TLS 1.3 for communications, replace it. This isn’t optional; it’s table stakes for handling PHI. Tools like VeraCrypt for local storage or cloud services with built-in encryption (AWS S3 with SSE-KMS, Azure Storage Service Encryption) are non-negotiable.
2. Segment your network so clinical systems can’t reach the internet directly. Isolate appointment scheduling, billing, and record systems from general web browsing and email workstations. Use VLANs or physical air gaps to ensure that if a front-desk worker clicks a phishing link, the malware can’t pivot to your patient database. This is basic network hygiene that costs nothing to implement but stops 80% of attack chains.
3. Implement strict access controls with role-based permissions and MFA everywhere. The receptionist doesn’t need access to full treatment histories. The hygienist doesn’t need to see billing information. Enforce least-privilege access and require phishing-resistant MFA (like FIDO2 security keys) for any system accessing patient data. Yes, it’s annoying—but less annoying than explaining to patients why their root canal history is for sale on dark web forums.
4. Backup daily, test weekly, and store backups offline or immutable. Ransomware and wiper attacks thrive when backups are connected to the network. Use the 3-2-1 rule: three copies of data, on two different media, with one copy offsite. For backups, make them immutable using AWS S3 Object Lock or Azure Immutable Storage so attackers can’t delete or encrypt them even with domain admin credentials.
5. Train staff monthly with phishing simulations tied to real consequences. Click a fake phishing link in simulation? You get extra training—but if you fall for it three times, you lose network privileges until you pass a competency test. Make it personal: show them exactly how a breach could lead to their own family’s health data being exposed.

As I wrote in my research on dark web extortion economics, stolen healthcare data isn’t just used for one-off ransom payments—it’s packaged, sold, and recycled in fraud campaigns for years. The Tieu Dental breach isn’t an isolated incident; it’s symptomatic of an industry that treats patient data as an afterthought rather than its most valuable asset. 

The broader pattern here connects directly to what I documented in my analysis on why there will be a Cyber 9/11 soon—these small-scale breaches are building blocks in a much larger threat landscape where healthcare infrastructure remains critically vulnerable. As I explored in my post on ShinyHunterz hitting TELUS Digital, the BPO and healthcare sectors share the same fundamental security failures: outdated systems, inadequate segmentation, and a dangerous reliance on compliance theater over actual security controls.

Fix your shit before Lynch Carpenter comes knocking on your door.