[🐛 Bug]: Virus detected with 4.21.0 windows selenium_manager.exe

[Lukenickerson]

What happened?

I installed the latest v4.21.0 version of Selenium-webdriver into a new node repo, and attempted to run a jest test that starts up a selenium driver browser (Chrome). The browser never started, and I received the error "Unable to obtain browser driver." at the command line. Meanwhile my virus detection (FortiClient) detected a virus and prevented the windows/selenium-manager.exe file from running.

Virus info: https://www.fortiguard.com/encyclopedia/virus/8233130

If I revert back to 4.20.0, there are no issues, and selenium web driver works as expected: browser opens, tests are run, etc.

How can we reproduce the issue?

1. Have FortiClient installed and running
2. Install v20.5.0 of Node js
3. npm init
4. npm i selenium-webdriver -- and make sure you have 4.21.0 installed
5. Run a js file that does something like...

import { Builder } from 'selenium-webdriver';
const driver = new Builder().forBrowser('chrome').build();

Relevant log output

Process: C:\Programs\nvm\v20.5.0\node.exe
Item: ...\node_modules\selenium-webdriver\bin\windows\selenium-manager.exe
Virus: Malicious_Behavior.SB//167591167
Status: Quarantined

Operating System

Windows 10

Selenium version

selenium-webdriver 4.21.0

What are the browser(s) and version(s) where you see this issue?

N/A

What are the browser driver(s) and version(s) where you see this issue?

N/A

Are you using Selenium Grid?

No

[github-actions]

@Lukenickerson, thank you for creating this issue. We will troubleshoot it as soon as we can.

---

Info for maintainers

Triage this issue by using labels.

If information is missing, add a helpful comment and then I-issue-template label.

If the issue is a question, add the I-question label.

If the issue is valid but there is no time to troubleshoot it, consider adding the help wanted label.

If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C), add the applicable G-* label, and it will provide the correct link and auto-close the issue.

After troubleshooting the issue, please add the R-awaiting answer label.

Thank you!

[diemol]

This is a duplicate of #12935

This happens whenever we update dependencies.

[github-actions]

This issue has been automatically locked since there has not been any recent activity since it was closed. Please open a new issue for related bugs.