Malware Can Abuse Windows Hello for Business Keys for Persistent Entra ID Access

Summary: Security researcher Malcolm Stagg has disclosed a new attack class called NatJack that manipulates network address translation (NAT) connection state to hijack active TCP sessions, spoof DNS responses, disclose victim IP addresses and mapped ports, and exhaust NAT tables. Presented at Black Hat USA 2026, Stagg said the techniques were demonstrated across network infrastructure devices

Windows Hello has become one of Microsoft’s flagship identity technologies, replacing traditional passwords with biometric authentication, PINs, facial recognition, and fingerprint verification backed by hardware security features such as the Trusted Platform Module (TPM). By ensuring that biometric data never leaves the device and that authentication secrets remain protected by dedicated hardware, Windows Hello has long been considered one of the strongest defenses against credential theft.

New security research, however, demonstrates that even strong authentication mechanisms can be abused once an attacker has already compromised the operating system.

Researchers have shown that malware running with sufficient privileges can manipulate Windows Hello to silently authorize malicious operations on behalf of a victim. Rather than breaking the biometric authentication system itself, the attack abuses legitimate operating system functionality after the user has already authenticated, illustrating an increasingly important principle in modern cybersecurity: secure authentication cannot fully protect a system that is already under an attacker’s control.

The distinction is critical.

Windows Hello is not being “cracked” or bypassed in the traditional sense. Attackers are not stealing biometric templates, defeating facial recognition, or extracting fingerprint data from the TPM. Instead, malicious software leverages legitimate Windows APIs and trusted authentication workflows to request user verification for operations that ultimately benefit the attacker rather than the user.

This type of attack is often described as living off the land.

Instead of deploying custom exploits against security technologies, attackers abuse built-in operating system capabilities exactly as they were designed to function. The malicious activity blends into normal system behavior because the software relies on trusted Windows components rather than suspicious external code.

Researchers demonstrated that malware can trigger Windows Hello authentication prompts under false pretenses, encouraging users to verify their identity while believing they are authorizing a legitimate system action. Once authentication succeeds, the malware can use that approval to perform sensitive operations requiring user presence.

The attack therefore targets human trust rather than biometric security.

Users have become accustomed to Windows Hello prompts appearing during routine administrative tasks, password manager access, software installation, credential retrieval, and security-sensitive operations. Frequent legitimate authentication requests make it increasingly difficult for users to distinguish between genuine operating system prompts and those initiated by malicious software already executing on the device.

The findings reinforce a broader cybersecurity reality.

Authentication answers one question exceptionally well:Who is using the device?

It does not necessarily answer another equally important question:Who requested the authentication?

If malware successfully gains code execution before the user authenticates, it may simply wait until Windows Hello becomes available and then persuade the operating system to request legitimate biometric verification on its behalf.

This illustrates why endpoint compromise remains one of the most serious threats in enterprise security.

Modern operating systems employ hardware-backed authentication, encrypted credential storage, secure boot, virtualization-based security, memory isolation, and trusted execution environments. These technologies significantly increase the difficulty of credential theft and unauthorized access.

Yet once malicious code obtains sufficient privileges inside the trusted operating system, many defensive assumptions begin to change.

Rather than attacking cryptography directly, adversaries increasingly focus on manipulating legitimate workflows.

This strategy has become increasingly common across multiple platforms.

Cybercriminals already abuse OAuth authorization requests, multi-factor authentication prompts, browser permission dialogs, accessibility features, remote assistance tools, and trusted administrative utilities. The objective is rarely to defeat security mechanisms outright. Instead, attackers persuade users—or the operating system itself—to invoke those mechanisms on their behalf.

Security researchers often describe these techniques as consent attacks.

The underlying technology functions correctly. The user simply grants authorization without fully understanding the consequences.

The Windows Hello research demonstrates that biometric authentication is not immune to this broader category of attack.

The findings are particularly relevant as passwordless authentication continues expanding throughout enterprise environments.

Organizations increasingly deploy Windows Hello for Business, FIDO2 security keys, passkeys, biometric authentication, and hardware-backed credentials to eliminate traditional passwords. These technologies substantially reduce phishing risks and credential theft but cannot entirely prevent malware from exploiting authenticated sessions after legitimate users have successfully logged in.

This reinforces the importance of defense in depth.

Strong authentication remains essential, but it must be complemented by endpoint detection and response (EDR), application control, privilege management, behavioral monitoring, code integrity enforcement, and continuous security validation capable of detecting malicious activity after authentication has already occurred.

Researchers also emphasize the importance of user awareness.

Unexpected Windows Hello prompts should not automatically be trusted simply because they appear authentic. Users should understand which applications are requesting authentication and why, particularly when prompts appear unexpectedly or outside normal workflows.

For software developers, the research highlights another challenge.

Applications requesting biometric authentication should clearly communicate the purpose of the request, minimizing opportunities for malware to exploit user familiarity with generic authentication dialogs. Improving contextual transparency may reduce the effectiveness of attacks relying on deceptive authorization requests.

Microsoft’s broader passwordless strategy remains fundamentally sound.

Windows Hello continues providing significantly stronger protection than traditional passwords against phishing, credential stuffing, password reuse, and many forms of identity theft. The research does not undermine those benefits. Instead, it demonstrates that authentication technologies should be evaluated as components within larger security architectures rather than standalone solutions.

No authentication mechanism can fully compensate for malware already executing with trusted privileges.

As operating systems continue strengthening identity protections, attackers increasingly shift their attention toward manipulating the trusted workflows surrounding those protections instead of attacking the cryptography itself.

The Windows Hello research serves as another reminder that cybersecurity is no longer defined solely by stronger authentication. The next generation of defenses must also ensure that authenticated actions genuinely reflect the intentions of the user—not merely the objectives of malicious software operating in the background.

In the era of passwordless computing, protecting identity is no longer just about verifying who is authenticating. It is equally about verifying what is being authorized,why the request exists, and whether the software initiating it can truly be trusted.

Key facts

  • A new attack class called NatJack has been disclosed
  • NatJack manipulates network address translation (NAT) connection state
  • The attack can hijack active TCP sessions
  • It can also spoof DNS responses
  • NatJack may disclose victim IP addresses and mapped ports
  • Techniques were demonstrated across network infrastructure devices

Why it matters

The NatJack attack class highlights a novel vulnerability in network infrastructure, specifically targeting the manipulation of Network Address Translation (NAT) states. This could allow attackers to hijack legitimate TCP sessions, leading to significant disruptions in network communication and potential data exfiltration. Organizations relying on NAT for network management and security need to assess their exposure to these techniques and consider enhanced monitoring and mitigation strategies.