1-minute read
What a defender needs to know
Entra ID researcher Dirk-jan Mollema demonstrated that code already running in a signed-in Windows session can invoke the user’s Windows Hello for Business key without extracting it, knowing the PIN, or triggering a biometric prompt. The technique can produce cloud authentication and, where policy permits, persistent access from an attacker-controlled device.
The private key remains protected by the TPM. Windows’ ticket-based PIN caching keeps sign-in keys available for private-key operations while the user is interactively signed in, so malware can ask Windows to sign a WebAuthn challenge. The resulting token can lack a device ID claim, allowing a path to device registration, a Primary Refresh Token, and additional authentication methods. The disclosure reports no active exploitation or victims.
Related reporting: Google-synced passkey attacks cover an adjacent post-compromise path through a different TPM-backed credential system.
Run the empty-device-ID Windows Hello for Business hunt, then compare hits with endpoint activity, device registrations, authentication-method changes, passkey additions, and later token use. Remove unverifiable devices and invalidate suspicious sessions. Confirm sensitive access requires the intended device state where possible, and separate benign incognito or non-SSO browser matches from unexplained cloud changes. Review the user’s complete sign-in history. Preserve process and PowerShell evidence from suspicious endpoints before rebuilding or returning the device to trusted service under response policy.
The private key can stay sealed while the account moves. Reconcile the joined-endpoint evidence with the Entra timeline.