Jump to content

Vortex v1.0 only - Trojan Virus in member.exe ?


amoeba00

Recommended Posts

Been using Vortex for a while (last version .18.6). Decided to upgrade to v1.0 - and Windows AV is reporting a very specific virus on one of the files: member.exe

 

Location: Vortex\resources\app.asar.unpacked\node_modules\native-errors\Detours\bin.X64\

Virus: Trojan:Win32/Skeeyah.A!MTB

 

Just downloaded v.19.1 to test and it didn't trigger this alert. Also, there isn't the full green check box on the Virus Scan (just the blue "some manually verified files") - so this doesn't necessarily fall under the usual "My AV is reporting a virus" concern. The alert happens on both the custom and regular files.

 

What's interesting is that when I first downloaded and installed this package last week - I didn't get the alert. I mistakenly selected the regular installer and just now realized it was using the C:\. So when I came back to download the custom installer one - all this happened. (Of course, I don't have the original file to compare).

 

Anyway - given that it wouldn't be the first time packages have been infected after the fact and there is no published hash file of Vortex of which to compare the original source - led me to post this.

 

Can someone confirm that it's a known false positive?

If so, maybe update the FAQ to include this specific item - since it's new to v1.0.

 

Thanks for your time.

 

OS: Windows 10, v1903

Definitions as of 8/4/2019 6:17am

Link to comment
Share on other sites

I just got the same this morning. At first I thought it was a mod I downloaded not fully scanned but now I'm not so sure.

 

If anyone can find out what the case is, I'm sure a lot of users (self included) would be appreciative. Last thing I want to do know is nuke my os and reinstall unless I have too! :confused:

 

AD

Link to comment
Share on other sites

Updated today and a Trojan was quarantined in member.exe.

Trojan:Win32/Skeeyah.A!mtb

 

Ransom.Win32.STOP.AN

ALIASES:

Win32.Trojan-Ransom.STOP.VZ9O0W (GData), Trojan:Win32/Skeeyah.A!MTB, (Microsoft), W32/Kryptik.GVDM!tr (Fortinet)

 

Threat Type: Ransomware

Encrypted: Yes

Link to comment
Share on other sites

Neither Norton nor Malwarebytes detect the virus mentioned. They both deem Vortex 1.0 safe. I downloaded 1.0 from Nexusmods several days ago. I do not use the Vortex updater.

 

EDIT: I just now re-downloaded Vortex 1.0 from Nexusmods and re-installed it. Nothing has changed. Both Norton and Malwarebytes deem Vortex 1.0 to be safe. I downloaded the default install version of Vortex.

Link to comment
Share on other sites

Got the same warning this morning when auto-updating it. Deleted the "infected" file, completely removed Vortex, did a full scan of the system and came up clean. Downloaded Vortex manually from the site, installed, same warning came back.

 

Pushed the installer to VirusTotal and it came back completely clean.

 

https://www.virustotal.com/gui/file/7f6411e323b721bda09477d0c885368120b71ee9c00a5c682f6850b244eba3ba/detection

 

Restored the member.exe file from quarantine and pushed that to VirusTotal, that also came back clean, with the exception of Microsoft detecting Trojan:Win32/Skeeyah.A!MTB

 

https://www.virustotal.com/gui/file/255d34ac5786570b9066e325cb8bb2bac34411650ebfbac0906d315c516d3397/detection

 

This reeks to me of Defender's heuristics engine having a mental breakdown, rather than an actual issue with Vortex.

Link to comment
Share on other sites

Whelp, this is actually really interesting. I did the update through Vortex within a few days of 1.0 being released and Windows Defender didn't pick up anything then, nor did it pick up anything when running Vortex (although, does Defender even check files when said program is ran?). So it's curious as to what changed.

 

In any case, I checked what Detours is even about and according to https://www.npmjs.com/package/detour , Detour is used for routing purposes. So that can be anywhere between Knowledge Base, the dashlets, and retrieving and displaying mod information when double clicking on mods.

 

Last update on it was 3 years ago so unless if Nexus made changes to it, it helps to close certain reasons.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...