Vercel rolls out new protection against stolen session cookie attacks
The interesting part here is that Vercel is treating session cookies as a hardware problem, not just a protocol one. For years the industry has thrown more flags, more heuristics, more CAPTCHAs at the problem, but the cookie itself stayed a bearer token: anyone who grabs it gets in. Binding the credential to the device that issued it changes that math, because the stolen artifact stops being sufficient on its own.
I'd want to know how the gradual rollout handles the edge cases, especially the legitimate ones. Users who switch browsers, clear their cache, or log in from a new machine are going to hit friction, and if the fallback path is weak, the protection only covers the happy path. The other question is whether the device binding survives the real world, where malware often runs on the same device that holds the valid session.
I think this is the direction the whole industry has to move. Info stealers have gotten cheap and effective, and every major platform is quietly doing some version of this. Vercel shipping it as a default posture for a developer platform is a good sign, but the proof will be in how it behaves under attack and how little it annoys the people who aren't under attack.
