Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

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

  • 3 پاسخ
  • 1 has this problem
  • 1 view
  • آخرین پاسخ توسّط 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.

Chosen solution

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

Read this answer in context 👍 0

All Replies (3)

more options

Chosen Solution

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.