The Threat Is No Longer Just About Code

For years, the story was simple: North Korean operatives posed as remote IT contractors, slipping into Western tech firms to steal code and earn hard currency for the regime. That playbook has changed. Recent investigations have uncovered suspected DPRK-linked workers embedded in sales, marketing, and even the medical profession.

This isn’t a minor shift. It’s a strategic expansion of what security researchers call the IT worker scheme — and it means the hiring manager at your clinic or your B2B sales team could be the next target.

How the Scheme Works

The DPRK’s operatives don’t show up with a badge. They work through a network of front companies, fake identities, and overseas intermediaries. A candidate might have a polished LinkedIn profile, years of fabricated experience, and a flawless interview manner. The catch? The person on the call isn’t the person who’ll be doing the work.

In many cases, a U.S.-based or third-country national takes the interview, while a North Korean operative performs the actual job duties remotely. The salary is funneled back to Pyongyang, often via cryptocurrency or shell accounts.

Why Healthcare and Sales?

Healthcare offers access to sensitive patient data and research — a goldmine for intelligence agencies. Sales roles, meanwhile, provide a foot in the door at hundreds of companies, offering a vantage point for corporate espionage and supply chain infiltration. These sectors also tend to have less rigorous vetting than government or defense contracting.

The result is a quieter, more insidious threat. A sales rep with access to client lists. A medical coder with access to records. Neither raises an eyebrow.

Real-World Cases and Red Flags

Investigations by firms like Mandiant and others have traced specific incidents where DPRK operatives successfully secured roles outside IT. In one case, a suspected operative was hired for a sales position after a series of video interviews with a stand-in. In another, a medical data entry role was filled by someone using a stolen U.S. identity.

So what should employers watch for? Here’s a practical checklist:

• Video interview mismatches: The person on screen looks different from their ID photo, or their lips don’t sync with the audio.
• Reluctance to turn on the camera: Persistent excuses about hardware issues or poor internet.
• Overly generic resumes: Experience listed at obscure companies that have no digital footprint.
• Requests for specific payment methods: Cryptocurrency, prepaid cards, or wiring to third-party accounts.
• Inconsistent time zones: A candidate claiming to be in the U.S. but always available at 3 a.m. local time.

None of these are smoking guns alone. But together, they warrant a deeper look.

What Companies Can Do Right Now

The good news? Mitigation is possible. Start with identity verification that goes beyond a cursory background check. Use live video interviews with a second interviewer present. Check references manually — call the actual company, not the number on the resume.

For remote-first organizations, consider deploying endpoint monitoring that flags unusual data access patterns. A sales rep pulling thousands of records at 2 a.m. is a red flag, regardless of their job title. And for healthcare employers, compliance with HIPAA isn’t just a legal requirement — it’s a front-line defense against insider threats.

Training matters too. Your HR team should know what the IT worker scheme looks like, even if they’ve never heard the term. A short briefing on these tactics can prevent a costly hire.

The Bigger Picture

This expansion signals that North Korea is adapting to Western defenses. As tech companies tighten their vetting, the regime’s operatives are simply moving to softer targets. Healthcare and sales are just the latest stops on that path.

The threat isn’t going away. But awareness is half the battle. If you’re hiring for a role that touches sensitive data — in any sector — treat the interview process like a security review, not just a talent search.

Stay updated on the latest tactics in our guide to remote work security best practices, and check out our breakdown of insider threat detection strategies for more actionable advice. For a deeper dive into the DPRK’s methods, see our analysis of state-sponsored cyber espionage trends.

Another Zero-Day, Another Headache for Security Teams

The researcher known as Nightmare Eclipse has done it again. Over the weekend, the prolific bug hunter released a new proof-of-concept exploit dubbed HardBreacher, this time aimed at a privilege escalation flaw in Kaspersky Endpoint Security.

It’s the latest in a string of public disclosures from the researcher, who has been on a tear lately, dropping PoC exploits for a range of Windows and Microsoft Defender vulnerabilities. But this one hits a different target — and it sounds nasty.

Nightmare Eclipse, also known as Chaotic Eclipse, has been vocal about their frustration with how Microsoft handles vulnerability reports. That frustration has translated into a steady stream of public exploits. Most have stayed at the PoC stage, but a few have been picked up and weaponized by real-world attackers.

What HardBreacher Does

According to the researcher, HardBreacher exploits a privilege escalation vulnerability in Kaspersky Endpoint Security. The impact, if the exploit lands, is described in dramatic terms.

“The PoC is not in the best shape at all, it is basically duct taped, I just managed to make it work and that’s all,” Nightmare Eclipse wrote. Fair enough — but the effect is anything but amateur.

“The interesting part about this is Kaspersky completely loses it when you take control over the UI process,” the researcher added. “You can cause it to stop functioning, grant/block access to files it’s not supposed to. If the PoC succeeds, the entire operating system becomes a hot mess.”

That description suggests a full compromise of the endpoint protection agent, which is exactly what you’d expect from a privilege escalation flaw in a security product. When the thing that’s supposed to protect you turns into a weapon, the whole system is in trouble.

Kaspersky Says It’s Already Patched

SecurityWeek reached out to Kaspersky, and the company confirmed the underlying issue has been resolved.

“The corresponding fix is delivered via an automatic update, or users can trigger a database update manually,” a Kaspersky spokesperson said.

That’s good news for enterprises running Kaspersky Endpoint Security — assuming they’ve let the updates flow. The company’s response suggests the fix was already in the wild before the exploit went public, which is the best-case scenario for defenders.

A Pattern of Public Disclosures

HardBreacher isn’t the only recent release from Nightmare Eclipse. The researcher has also published ShieldBreak, which reportedly allows an attacker to spawn a shell with System privileges, and LegacyHive, another privilege escalation tool.

The trio of exploits paints a picture of a researcher who’s done with responsible disclosure and is now going public with findings. It’s a controversial approach, but one that’s increasingly common in the security world.

For defenders, the takeaway is straightforward: keep your endpoint security products updated, and take these public PoCs seriously. They’re not just theoretical exercises.

Related reading: Log4j remote code execution scare and critical Ruby on Rails vulnerability in attackers’ crosshairs show how quickly public disclosures turn into active exploitation.

What This Means for Your Organization

If you’re running Kaspersky Endpoint Security, the fix is already available. But the incident raises a broader question: how many other security products have similar flaws sitting undiscovered?

Security researchers are increasingly choosing public disclosure over coordinated vulnerability disclosure, and that trend isn’t going away. The best defense is a patch management process that doesn’t wait for the headlines.

Also worth remembering: Nightmare Eclipse’s earlier exploits have been exploited in the wild. The line between PoC and weapon is thin, and it only takes one attacker with a bit of ingenuity to cross it.

Stay updated, stay patched, and keep an eye on what this researcher does next.

Android 17 Brings ECH to the OS Level

Google has quietly rolled out a significant privacy upgrade in Android 17. The new version introduces support for Encrypted Client Hello (ECH), a standard that stops network providers from seeing which websites you visit. This isn’t just a browser tweak — it’s baked into the operating system itself.

For years, your internet service provider (ISP) could see the domain names of every site you accessed, even if the content was encrypted. ECH changes that by encrypting the part of the TLS handshake that reveals the server name. Now, with Android 17, that protection applies across the entire OS, not just in Chrome or Firefox.

The announcement came on Thursday, with Google positioning ECH as a cornerstone of its broader network security push. The company also highlighted efforts to shore up cellular vulnerabilities and protect home network privacy.

How ECH Works: The Technical Side

When you connect to a website, your device sends a TLS handshake that includes the domain name in plaintext. That’s how network providers know you’re visiting example.com even if the page itself is encrypted. ECH encrypts this handshake, so the server name is hidden from anyone sniffing the connection.

This is a big deal. DNS over HTTPS (DoH) and DNS over TLS (DoT) already hid your DNS queries, but the TLS handshake itself remained a leak. ECH closes that gap.

Android 17 implements ECH at the OS level, which means every app that uses the system’s network stack benefits automatically. You don’t need to configure anything or install a special browser. It just works.

What This Means for Your Privacy

For the average user, the practical effect is simple: your network provider can no longer build a profile of your browsing habits based on domain names. That’s a major win for privacy, especially on public Wi-Fi networks where snooping is easier.

It also matters for people in countries with strict internet censorship. ECH makes it harder for authorities to block access to specific sites, though it’s not a silver bullet — they can still block by IP address or use other techniques.

Beyond ECH: Other Security Upgrades in Android 17

ECH isn’t the only security feature in Android 17. Google also addressed cellular vulnerabilities that could expose your location or allow attackers to intercept calls. These fixes target the baseband processor, which handles radio communication and has historically been a weak point.

Home network privacy also got a boost. Android 17 now handles certain network configurations more securely, reducing the risk of man-in-the-middle attacks on your local network.

Here’s a quick rundown of what’s new:

• OS-wide ECH support for encrypted TLS handshakes
• Patches for cellular baseband vulnerabilities
• Improved home network privacy protections
• Seamless integration with existing apps — no developer action required

Why This Matters for Your Network Provider

Network providers have long relied on seeing domain names to throttle traffic, target ads, or comply with government requests. ECH undermines that visibility. Providers can still see your IP address and the amount of data you transfer, but they lose the ability to know exactly which sites you’re visiting.

That’s a significant shift. It’s also a reason why some ISPs have pushed back against ECH in the past, arguing it complicates network management and parental controls. Google’s decision to bake it into Android 17 suggests the company is prioritizing user privacy over carrier convenience.

If you’re concerned about your own setup, you might also want to explore how to change your DNS settings on Android for an extra layer of privacy, or check out the best VPN apps for Android to complement ECH.

How to Get Android 17 and ECH

Android 17 is rolling out now, but availability depends on your device. Pixel phones get it first, followed by other manufacturers. If you’re not sure whether your device has received the update, go to Settings > System > System update and check.

Once you’re on Android 17, ECH is enabled by default. There’s no toggle to flip or setting to hunt down. That’s the beauty of OS-level integration — it’s just there, protecting you without any effort.

For developers, the good news is you don’t need to change your apps. The system handles ECH transparently. If you’re building a network-heavy app, though, it’s worth testing to ensure everything still works as expected.

The Bottom Line

Android 17’s ECH support is a quiet but meaningful step forward for online privacy. It closes a long-standing gap in encrypted communications and does so in a way that requires zero user action. That’s rare in the security world, where the best protections often demand the most setup.

It’s not perfect — IP address leaks and other metadata remain — but it’s a solid improvement. If you value your privacy, updating to Android 17 is a no-brainer.