Google Chrome's Safety Check feature, which checks if users' saved passwords have been compromised, will now “run automatically in the background” on desktop
Google's Safety Check feature for Chrome, which, among other things, checks the internet to see if any of your saved passwords …
Context & Ripple Effects
Google has steadily moved password-breach alerts from an optional Password Checkup Chrome extension into broader account and browser surfaces, including Chrome 79’s breach notifications.
The new desktop behavior continues that arc: rather than waiting for users to open a security tool, Chrome makes compromised-password monitoring a background function. It matters because Chrome is turning a discrete check into an ongoing browser responsibility.
First-order effects
- Desktop Chrome users will receive ongoing checks of saved passwords for compromise without manually starting Safety Check.
- Google deepens Chrome’s role in credential security, building on its earlier password-breach notifications in Chrome 79.
Second-order effects
- Password-manager and browser rivals face greater pressure to make breach monitoring automatic and easy to act on, not merely available as a manual audit.
- Sites affected by reused or exposed credentials may see more users prompted to reset passwords; Google had already explored reducing that repair friction through Chrome-assisted password fixes.
Third-order effects
- If background monitoring becomes standard across browsers, password safety will increasingly be treated as a default platform service rather than a task left to individual users.
- That shift could raise expectations for browsers to detect and help remediate account-risk signals, while concentrating more security decision-making inside major browser ecosystems.
The trend: Browsers are evolving from page-rendering tools into always-on account-security layers that identify and increasingly help resolve credential risk.