vrserver.exe being flagged by antivirus

[Hobby Boy]

Today, my antivirus detected the vrserver.exe file Steam\vr\runtime\bin\ as a virus, along with trz61C4.tmp. Is the software actually malicious or is this a false positive from my antivirus?

I'm using Avast 9 with the latest definitions.

[Shire's Finest]

same thing happened to me, i think its a false positive

[Hobby Boy]

There is also a thread about this on the Avast forums: https://forum.avast.com/index.php?topic=151118.0

[gleofrocga]

trz61C4.tmp sounds malicious to me. What directory is that file in? Ive seen it in some other post about an infected services.exe file.

[Hobby Boy]

It was in the same folder as vrserver.exe. Virustotal also came out clean on it.

[Rabbit]

same here avast 9 flagged vrsteam.exe as Win32:Malware-gen while I was playing TF2

[Julian Carax]

Mine too.

[Maresto]

lol

[Julian Carax]

Just put directory in scan exclusion for avast. Waiting for an update from avast...

[Hobby Boy]

The temp file had the same SHA256 checksum as vrserver.exe. I guess it was the temp file that Avast left when it asked me to reboot my computer (I didn't).

[SpecOp Clergy]

Originally posted by Rabbit:

same here avast 9 flagged vrsteam.exe as Win32:Malware-gen while I was playing TF2

Just happened to me, too. When I booted up Steam, this file was flagged and quranteened. Probably a false positive as I doubt Steam would let some malicious code get in there. Still, keeping an eye on this thread. Avast wanted to do a bootscan, but seeing how I just did a full system scan yesterday, I didn't see the need.

[sashqaxd]

123

[apple juice]

I got the same notification, PLUS somebody tried to request a new password for my account, so maybe there is something malicious going on.

[Humdrum Sebby]

Avast has detected Steam stuff as malware in the past, this is first time it's happening for me.
I would guess that it's just a false positive, but it's always good to stay safe.

[Julian Carax]

Now it's not more detected as malware. Maybe an update from avast fixed that stuff...

[rocky]

Same here, I wanted to check it wasn't a false positive before running a lengthy boot-time scan. Hopefully avast sort it out, for now either trust it is just a false positive or let avast do what it needs to do with deal with the "malware".