Liveness Detection: 6 Seconds to a Stolen Google Account

Breaking down the credential enrollment attack vector in modern authentication pipelines reveals a critical architectural lesson: a system can have mathematically unbreakable cryptography at login and still suffer complete account compromise within seconds.

Recent reporting on Google passkey exploits underscores a gap that engineering teams frequently overlook. WebAuthn and FIDO2 standards have effectively mitigated credential interception and traditional phishing during authentication (navigator.credentials.get()). However, the attack surface has shifted upstream to the credential creation and enrollment phase (navigator.credentials.create()).

The Ingestion Vulnerability in WebAuthn Workflows

In the documented attack pattern, the underlying public-key cryptography (ECDSA/Ed25519) was never breached. Instead, attackers exploited session downgrade fallbacks—such as prompting a user for a legacy TOTP or SMS verification code via a reverse proxy. Once the attacker established an authenticated session, they executed an automated enrollment request to register their own device's public key to the victim's account. The entire process completed in roughly six seconds, leaving the attacker with persistent, cryptographic access that survives password resets.

The protocol functioned exactly as designed. The architectural failure was treating credential registration as routine account metadata modification rather than a high-risk trust escalation.

The Parallel in Biometric and Computer Vision Systems

This authentication disconnect directly mirrors a common challenge in computer vision and facial comparison architectures.

When building facial comparison pipelines, engineers often focus heavily on the metric space—optimizing deep convolutional networks to generate 128-d or 512-d feature vectors where Euclidean distance or cosine similarity accurately reflects identity. However, Euclidean distance analysis is only as reliable as the reference embedding registered in your database.

If a pipeline does not enforce rigorous Presentation Attack Detection (PAD)—evaluating passive texture, micro-movements, and specular reflection against standards like ISO/IEC 30107—a poisoned reference image can be ingested during initial enrollment. Downstream, the facial comparison algorithms will execute with mathematical precision, but they will be calculating distances against a compromised baseline.

In both WebAuthn and biometric comparison systems, authentication is a point-in-time calculation; enrollment is an enduring trust anchor.

Engineering Mitigations for Dev Teams

To prevent enrollment-based hijacking across authentication and identity pipelines, engineering teams should implement specific architectural safeguards:

1. Step-Up Verification on Credential Creation: Never allow navigator.credentials.create() to inherit existing session trust without explicit, multi-factor re-authentication locked to the existing highest-tier authenticator.
2. Out-of-Band (OOB) State Alerts: Implement asynchronous event triggers (via webhooks or transactional notification queues) that alert all active devices instantly when cryptographic keys or biometric profile baselines change.
3. Strict Enrollment Gates in Biometrics: Decouple standard comparison endpoints from enrollment endpoints. Require active/passive liveness validation before computing and committing new reference embeddings to cold storage.

Securing the authentication endpoint is only half the battle. If your onboarding and enrollment pipeline treats key generation as a low-friction background task, the strength of your downstream matching algorithms won't prevent unauthorized takeover.

How is your team structuring session step-up and out-of-band verification when users register new cryptographic credentials or update reference profile data?