Malware Can Abuse Windows Hello for Business Keys for Persistent Entra ID Access
Malware Can Abuse Windows Hello for Business Keys for Persistent Entra ID Access
Entra ID researcher Dirk-jan Mollema demonstrated that malware already running in a signed-in Windows session can silently use the victim’s Windows Hello for Business key to authenticate to Microsoft Entra ID.
The attacker can then establish longer-term cloud access, register a device it controls, obtain a Primary Refresh Token (PRT), and add further authentication methods where tenant policies permit.
On TPM-backed systems, the attacker does not extract the private key, recover the PIN, or trigger a biometric prompt. Windows ticketing keeps private-key operations available while the user is interactively signed in, allowing code running as the user to ask Windows to sign authentication data. Administrator privileges are not required.
The technique requires code execution in the victim’s signed-in session. Mollema describes the behavior as a consequence of how Windows Hello for Business works and says it was left as-is. The disclosure does not report active exploitation or victims. Mollema recommends monitoring unexpected device registrations.
The disclosure does not identify the exact Windows builds or Windows Hello for Business deployment models tested. The Hacker News found no CVE or Microsoft advisory tied to the technique in searches of Microsoft’s Security Update Guide, NVD, and CVE.org as of August 6, 2026. The Hacker News has contacted Microsoft and Mollema; replies are pending.
Microsoft documents the ticketing behavior. Mollema said the ability to invoke Windows Hello for Business keys from a compromised session was presented at DEF CON 32 in 2024. That method could produce a signed assertion for a PRT, but also required access to an Entra-registered or joined device.
The new work removes that requirement by treating the Windows Hello for Business key as a FIDO2 passkey through WebAuthn. Mollema found that the five-minute Entra ID challenge is not bound to a session, user, or tenant.
An attacker can therefore request it on another host and have the compromised endpoint produce the signed assertion. ROADtools, a framework for interacting with Entra ID, can use the assertion to request tokens or open a browser session as the victim.
Mollema found that the token carries no device ID claim. A token without that device binding lets the attacker register a new device, request a PRT for it, and reach Microsoft cloud services. Microsoft documents that a PRT remains valid for 90 days and is continuously renewed while the user actively uses the device.
Mollema found that the WebAuthn sign-in can satisfy Conditional Access policies requiring Microsoft’s phishing-resistant authentication strength. He said the sign-in also counts as fresh multi-factor authentication, allowing an attacker to add passkeys or Windows Hello for Business keys on the new device where policies allow. Separate device-state or compliance policies can still interrupt the chain, so the complete persistence route will not work in every deployment.
The finding exposes a limit of phishing-resistant authentication: the credential can remain hardware-bound and unexported while malware inside the signed-in endpoint session invokes it for the attacker.
Mollema published the PowerShell proof-of-concept scripts in the ROADtools repository. The Hacker News found fido_assertion.ps1 and hellopoc.ps1 in the folder on August 6, 2026. For detection, he recommended hunting for Windows Hello for Business sign-ins with an empty device ID. Legitimate incognito or non-SSO browser sessions can produce the same pattern.
About Author
