Skip to content
Google Implements DPoP in OAuth 2.0 to Combat Token Theft

Google Implements DPoP in OAuth 2.0 to Combat Token Theft

First seen 30 Oct 2026, 01:43 UTC • •

Article Content

Browse articles
ThreatCluster AI
ThreatCluster •October 30, 2026 at 03:45 UTC

Google has introduced support for Demonstrating Proof-of-Possession (DPoP) in its OAuth 2.0 platform to mitigate token theft and replay attacks. DPoP binds tokens to client-generated asymmetric key pairs, making stolen tokens unusable without the corresponding private key. This enhancement is particularly focused on long-lived refresh tokens, which are often exploited for persistent online impersonation. However, access tokens will continue to use the standard Bearer token model due to performance concerns. The implementation requires developers to handle cryptographic keys and timestamps, increasing client-side complexity. DPoP does not protect web application session cookies, which remain vulnerable to malware. Google is also developing Device Bound Session Credentials (DBSC) to address this gap. DPoP is not suitable for multi-agent workflows, and Google recommends using its Cloud Secure Token Service for delegation. The security of the DPoP private key relies on the client’s security measures.

Start a free Starter trial for enhanced analysis

Ask AI about this cluster

Updated just now How this analysis works

Timeline

2026-10-29
Google announces DPoP support
Google introduced DPoP in its OAuth 2.0 platform to strengthen security against token theft.
News.Lavx.Hu
2026-10-30
InfoQ reports on DPoP implementation
InfoQ published an article detailing Google's DPoP support and its implications for OAuth 2.0 security.
infoq.com

More articles in this cluster (5)

Following this threat?

Track NodeStealer in your own feed — you're alerted when they show up in new reporting, leak sites or exploitation.

Free account · no card needed

Common questions

What does DPoP do?
DPoP binds tokens to asymmetric key pairs, preventing stolen tokens from being reused.
Which tokens are affected by DPoP?
DPoP is currently supported only for refresh tokens in Google's OAuth 2.0.
What are the client-side requirements for DPoP?
Developers must generate cryptographic keys, handle timestamps and nonces, and construct specific HTTP headers.