We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

McAfee flagged a trojan in win64/en-CA/Firefox Setup 89.0.1.exe

  • 3 回覆
  • 1 有這個問題
  • 1 次檢視
  • 最近回覆由 mabelisle

more options

Hi,

I got a McAfee report on the first machine that I tried to deploy this file.

Firefox Setup 89.0.1.exe contains the GenericRXAA-AA!92712AE6AC5F Trojan. Undetermined clean error, OAS denied access and continued. Detected using Scan engine version 6200.9189 DAT version 10008.0000.

I scanned the file with on VirusTotal and verify the hash. It doesn't bring up anything.

Does someone know anything about this?

Thanks.

Hi, I got a McAfee report on the first machine that I tried to deploy this file. Firefox Setup 89.0.1.exe contains the GenericRXAA-AA!92712AE6AC5F Trojan. Undetermined clean error, OAS denied access and continued. Detected using Scan engine version 6200.9189 DAT version 10008.0000. I scanned the file with on VirusTotal and verify the hash. It doesn't bring up anything. Does someone know anything about this? Thanks.

被選擇的解決方法

This doesn't sound like a specific detection:

Undetermined clean error, OAS denied access and continued.

"Denied access" sounds like a Windows permission/privilege issue?

Some results in web search:

https://www.google.com/search?q=%22Undetermined+clean+error%22+%22OAS+denied+access+and+continued%22&client=firefox-b-1-d

從原來的回覆中察看解決方案 👍 0

所有回覆 (3)

more options

選擇的解決方法

This doesn't sound like a specific detection:

Undetermined clean error, OAS denied access and continued.

"Denied access" sounds like a Windows permission/privilege issue?

Some results in web search:

https://www.google.com/search?q=%22Undetermined+clean+error%22+%22OAS+denied+access+and+continued%22&client=firefox-b-1-d

more options

Have you checked with McAfee support? Make sure McAfee is up to dat.

more options

It turned out to be that when the installer was executed from a network drive, it probably didn't have all the permissions needed like @jscher2000 was implying.

False alarm, half a day of work lost but it's how it goes.

Thanks for the help.