How to Stop Chrome Password Breach Warning Dialog When Using Puppeteer Automation?

Other Questions Puppeteer
1

I’m working with Puppeteer to automate Chrome browser tasks and keep getting this annoying dialog that pops up saying something like “Your password was found in a data breach. Please update it in Google Password Manager.”

I’ve tried adding these Chrome flags to stop it but the warning still shows up:

var launchSettings = new LaunchOptions
{
    ExecutablePath = @"C:\Program Files\Google\Chrome\Application\chrome.exe",
    Headless = false,
    Args = new[]
    {
        "--disable-features=PasswordLeakDetection",
        "--no-sandbox",
        "--disable-save-password-bubble"
    },
    DefaultViewport = null
};

var browserInstance = await Puppeteer.LaunchAsync(launchSettings);
var newPage = await browserInstance.NewPageAsync();

await newPage.GoToAsync("https://example-login-site.com");
await newPage.TypeAsync("#username-field", "testuser");
await newPage.TypeAsync("#password-field", "mypassword123");
await newPage.ClickAsync("#submit-btn");

Any ideas on how to completely get rid of this popup? Can I maybe use some JavaScript to dismiss it automatically or are there other Chrome arguments I should try?

Using PuppeteerSharp version 20.0.5 with Chrome 131.0.6778.86 on Windows 10.

Thanks for any help you can provide!

2

try adding --disable-password-manager-reauthentication and --disable-web-security to your args. using --user-data-dir=temp_profile can also help by starting with a clean profile, so no saved passwords trigger the warning.

3

The issue persists because Chrome’s breach detection works at a level that the flags may not fully address. I encountered this specific problem recently while running automated login tests. A solution that worked for me was to use a combination of --disable-features=VizDisplayCompositor,PasswordLeakDetection, along with --disable-background-networking and --disable-sync. Chrome actively checks passwords against breach databases through background processes that typical password manager flags do not affect. You might also consider adding --disable-features=Translate,OptimizationHints, as these can interfere with automation. If the warnings still appear, adding --disable-component-extensions-with-background-pages can prevent security-related extensions from running. This combination should effectively eliminate the breach warnings while keeping your automation intact.

4

Same issue here with Chrome automation. The problem’s usually existing Chrome profiles messing with your flags. I fixed it by combining --disable-features=PasswordLeakDetection,PasswordManager with --incognito mode - bypasses stored credentials completely. Also try --disable-notifications and --disable-extensions since some built-in security extensions can trigger these warnings on their own. If you need stored credentials, create a dedicated test profile with --user-data-dir=./test-profile and manually clear all saved passwords from it first. Bottom line: make sure Chrome starts completely clean without any existing password data that could trigger the breach detection.