Here's the part that should genuinely surprise you: even if you use two-factor authentication, a passkey, and a strong unique password, a hacker who steals the right browser cookie can walk right into your account anyway. No password needed. No 2FA prompt. Nothing. And this kind of attack has been quietly exploding for years.
Google's answer is called Device-Bound Session Credentials, or DBSCs, and it's now shipping in recent versions of Chrome for Windows and macOS. The core idea is elegant: instead of just storing a session cookie in your browser like a sticky note anyone can grab, Chrome now ties that cookie to a cryptographic key that lives inside your device's dedicated security chip — a TPM on Windows machines, a Secure Enclave on Apple devices.
To understand why this matters, you need to understand how session cookies work. When you log into your bank or your email, the server hands your browser a cookie that essentially says "this person already proved who they are." Every subsequent page load shows that cookie instead of asking you to log in again. It's convenient, but it also means that cookie is basically a skeleton key. Steal it, paste it into another browser, and you're in — same access, same permissions, no questions asked.
Attackers have known this forever, but the attack became far more attractive once the industry pushed hard on 2FA and passkeys. Those protections made traditional phishing dramatically less effective. So criminals pivoted. Infostealer malware — software designed to quietly vacuum up browser data — became a booming underground industry. Adversary-in-the-middle attacks, which intercept cookies in transit, followed the same logic. Both approaches are specifically optimized to grab session cookies, because that's now the most reliable path to account access.
DBSCs break this entire chain. When a compatible website sets a session cookie, Chrome now requires the browser to sign it using the private key stored in the security chip. The critical detail: the chip is designed so that key never leaves the hardware. An attacker who steals the cookie still can't do anything with it, because they can't produce a valid signature without the physical device it came from.
"The attacker can steal the cookie, but they can't answer a DBSC challenge," security researcher Scott Helme explained in a writeup on the feature. The stolen cookie becomes useless without the private key, and the private key isn't going anywhere.
The catch, for now, is availability. DBSCs are live in Chrome 147 on Windows and Chrome 150 on macOS, but they're only enabled for a subset of users while Google runs what appears to be a broader rollout test. Websites also need to explicitly support the standard before users get the protection, which means adoption will be gradual.
But the direction here is clearly right. Session cookie theft has been a known, serious problem for years, and most consumer-facing security advice does essentially nothing to address it. A hardware-backed fix that works invisibly in the background is exactly the kind of unglamorous security work that actually moves the needle. If Google rolls this out broadly and other browser vendors follow — which, given the open standard, they could — a whole category of account takeover attacks gets substantially harder overnight.