"DBSC works by storing a private key in your device's TPM (the same device that the fingerprint sensor or similar biometric devices on your laptop or phone uses) and using that key to sign your cookie," explained Malte Ubl.
Device Bound Session Credentials (DBSC)
Vercel has begun a gradual rollout of Device Bound Session Credentials (DBSC) on its platform to reduce the risk posed by information-stealer malware. The feature binds a login session on vercel.com to a user's device by storing a private key in the device's TPM and using that key to sign the session cookie. According to the company, "The private key can never be retrieved ever again. Not by us, not by you, not by the malware."
The announcement was made by Vercel's CTO, Malte Ubl, on X, and targets logins to Vercel's developer-facing console where projects and deployments are managed. Vercel positions DBSC as a layer of protection that prevents stolen session cookies from being reused on other devices.
Chrome's App‑Bound Encryption and the DBSC pairing
Vercel said DBSC complements Chrome's App‑Bound Encryption. While App‑Bound Encryption aims to make it harder for infostealer malware to extract browser cookies, DBSC takes the next step by ensuring that even if a cookie is stolen, it cannot be replayed from a different device. Vercel's rollout notes that DBSC currently works in Chrome on macOS and Windows and that the company is rolling the feature out gradually to ensure edge cases involving OAuth apps are handled appropriately.

The cyber insurance questionnaire just landed. Now what?
SOC 2, HIPAA, insurance renewals - someone has to own security strategy. Nubivance provides fractional CISO leadership without the full-time salary.
Get a security leadDPoP for the Vercel CLI
Alongside DBSC for browser sessions, Vercel is also rolling out a similar protective technology called DPoP for the Vercel CLI. The company framed these changes as platform-level mitigations aimed at reducing the value of stolen credentials across different access vectors used by developers.
Security Review public beta for Pro and Enterprise teams
Earlier the same week, Vercel launched Security Review in public beta for Pro and Enterprise teams. The feature is an addition to Vercel Agent that, once enabled, scans code changes on every push to connected GitHub repositories. Vercel says the system uses code and team-defined policies to flag issues such as missing authorization checks and exposed secrets.
If the Vercel Agent has the necessary permissions, it can validate and commit fixes; Vercel noted that agent-generated fixes will be billed separately. Security Review scans will be free until November 10, 2026, the company said. Ubl added that Vercel's security team had shipped the feature internally a couple of months prior and decided to make it broadly available after internal success.
Context: the April breach and the threat actor response
Vercel's recent security product pushes come after an April security breach that the company said affected a subset of customers. In that incident, attackers gained access to Vercel systems by compromising an employee's Google Workspace account at Context.ai. Vercel reported the attacker used those credentials to reach internal systems and view environment variables that had not been marked as sensitive.
Following the breach, a threat actor impersonating ShinyHunters attempted to sell the allegedly stolen source code, access keys, and database data. Those events are part of the backdrop Vercel cited in explaining why additional controls like DBSC, DPoP, and Security Review are being deployed.
What this means for developers, security teams, and adversaries
- Developers: Developers who manage projects on vercel.com gain a session model that refuses cookie replay across devices when DBSC is active; however, the protection is currently limited to Chrome on macOS and Windows while the rollout addresses OAuth edge cases.
- Security teams and Pro/Enterprise buyers: Security Review offers an automated, policy-driven scan of GitHub pushes with agent-assisted fixes available if permissions allow, and Vercel has set scans to be free through November 10, 2026 while charging separately for agent-applied fixes.
- Adversaries and opportunistic sellers: Vercel's measures — DBSC, DPoP, and automated code/secret scanning — are designed to decrease the resale value of stolen cookies, keys, and source material, a response plainly linked to the April compromise and subsequent attempted sales.
Next questions for Vercel's rollout
Vercel has taken concrete steps to harden developer access and to surface code-level risks, but the company itself notes the rollout is gradual. The immediate questions left on the record are practical: how quickly DBSC will expand beyond Chrome on macOS and Windows, how OAuth edge cases will be resolved in real-world teams, and how broadly customers will adopt agent permissions that allow Vercel to validate and commit fixes.
The company has tied these product moves to an operational imperative that followed the April breach. For teams that host, deploy, or build on Vercel — and for buyers evaluating Pro and Enterprise plans — the coming weeks will show whether these controls materially reduce credential reuse and secret exposure in the platform's ecosystem.
Source: BleepingComputer — Vercel rolls out new protection against stolen session cookie attacks




