Antivirus False Positive Testing and Tracking (Part 3)

[GCuser99]

This is an update (May 2026) on our previous AV False-positive tracking discussion.

Since the beginning of 2026, the SeleniumVBA Excel macro version has not experienced a MS Windows Defender False-Positive detection. Many thanks to the community (especially @hanamichi77777 and @6DiegoDiego9) for helping to find ways to improve the codebase's risk profile. Also thanks to @hanamichi77777's persistence in submitting false-positive reports to vendors participating in VirusTotal scans. As of May 6, 2026 VT's AV software vendors show no false-positive detections!

We will continue our diligence to monitor the situation. I'll post updates to the table below on a regular basis. As with before, contributions from other users are welcomed.

Note: The ActiveX DLL and MS Access db versions, as yet, have not been problematic with regard to FP's.

Date	SeleniumVBA Version	Win Defender	Virus Total Score
8/8/2026	SeleniumVBA.xlsm v7.3	no detection 1.457.63.0	0/64
8/8/2026	SeleniumVBA_prior_to_2508.xlsm v7.3	no detection 1.457.63.0	0/64
7/9/2026	SeleniumVBA.xlsm v7.3	no detection 1.455.54.0	0/64
7/9/2026	SeleniumVBA_prior_to_2508.xlsm v7.3	no detection 1.455.54.0	0/64
6/16/2026	SeleniumVBA.xlsm v7.3	no detection 1.453.121.0	0/64
6/16/2026	SeleniumVBA_prior_to_2508.xlsm v7.3	no detection 1.453.121.0	0/64
5/20/2026	SeleniumVBA.xlsm v7.3	no detection 1.451.8.0	1/64
5/20/2026	SeleniumVBA_prior_to_2508.xlsm v7.3	no detection 1.451.8.0	1/65
5/6/2026	SeleniumVBA.xlsm v7.3	no detection 1.449.447.0	0/63
5/6/2026	SeleniumVBA_prior_to_2508.xlsm v7.3	no detection 1.449.447.0	0/64
4/24/2026	SeleniumVBA.xlsm v7.3	no detection 1.449.275.0	1/64
4/24/2026	SeleniumVBA_prior_to_2508.xlsm v7.3	no detection 1.449.275.0	1/65
4/16/2026	SeleniumVBA.xlsm v7.3	no detection 1.449.134.0	2/66
4/16/2026	SeleniumVBA_prior_to_2508.xlsm v7.3	no detection 1.449.134.0	2/65
4/14/2026	SeleniumVBA.xlsm v7.2	no detection 1.449.99.0	0/64
4/14/2026	SeleniumVBA_prior_to_2508.xlsm v7.2	no detection 1.449.99.0	3/65
4/2/2026	SeleniumVBA.xlsm v7.2	no detection 1.447.129.0	1/65
4/2/2026	SeleniumVBA_prior_to_2508.xlsm v7.2	no detection 1.447.129.0	3/64
3/16/2026	SeleniumVBA.xlsm v7.2	no detection 1.445.559.0	3/65
3/16/2026	SeleniumVBA_prior_to_2508.xlsm v7.2	no detection 1.445.559.0	4/65
2/12/2026	SeleniumVBA.xlsm v7.2	no detection 1.445.13.0	3/66
2/12/2026	SeleniumVBA_prior_to_2508.xlsm v7.2	no detection 1.445.13.0	4/65
12/30/2025	SeleniumVBA.xlsm v7.2	no detection 1.443.402.0	5/65
12/30/2025	SeleniumVBA_prior_to_2508.xlsm v7.2	no detection 1.443.402.0	5/65

[hanamichi77777]

The false positive from Bkav had returned, but I received an email from them today confirming it has been cleared.
With this, we are officially back to zero detections. Congratulations!

I hope this wonderful SeleniumVBA will be used by many people.

[hanamichi77777]

I wanted to share a quick update and some positive news regarding the project's security status.
I recently ran the SeleniumVBA v7.3 files through VirusTotal, and they continue to maintain a perfect, clean record.

File: SeleniumVBA.xlsm

File: SeleniumVBA_prior_to_2508.xlsm

Thank you for continuing to provide such a clean, reliable, and secure wrapper for the community!

[hanamichi77777]

Measures to prevent re-detection when releasing updates

I feel that replacing WMI in the WebDriverManager class with an alternative is highly effective in reducing the risk score, as our VirusTotal scans have continuously maintained a perfect zero detection status. Up until now, I had to submit false positive reports to VirIT, Kingsoft, and Bkav with each update, so it would be wonderful if we no longer need to do that in the future.

I have attached the file where only the WebDriverManager class has been replaced, so let's see how it goes.
SeleniumVBA.xlsm

[hanamichi77777]

I've been monitoring the situation with the fixed file for two weeks, and the VirusTotal score has remained at zero throughout.
In addition, I've gone ahead and implemented the BiDi extension version, which is now publicly released, and even in a WebSocket environment the VirusTotal score has stayed at zero.
Given this, I'm confident that the maintenance burden will be reduced as follows:

・Since re-detection won't occur even on updates, false-positive reports will no longer be necessary.
・Password-protected files will also no longer be needed.

I hope this thread will truly no longer be needed going forward.