Jump to content

SkyrimLauncher.exe detected as Malware.Sandbox.32


RID93

Recommended Posts

Hello everyone! Recently, my MalwareBytes install has started detecting the launcher for TES: Skyrim as malware (Malware.Sandbox.32). Probably a false positive, especially since I've had it on my computer for a while now, but here's the file just to be sure.

sample.zip log.txt

Link to post
Share on other sites

I did uncheck these options, but I tend to mechanically check "Scan for rootkits" whevener I do a manual scan. I've started one without it and the launcher doesn't seem to be detected this time.

Link to post
Share on other sites

1 minute ago, RID93 said:

I did uncheck these options, but I tend to mechanically check "Scan for rootkits" whevener I do a manual scan. I've started one without it and the launcher doesn't seem to be detected this time.

Nevermind, MB does detect it actually.

Link to post
Share on other sites

4 minutes ago, Porthos said:

I only asked because I did not have a detection on the file.

 

Strange. I updated MB rather than just the viral database, and I still get the same result. I do have "Scan within archives" and "Use artificial intelligence to detect threats" checked, though, if it helps.

My Avira doesn't detect it. I passed the file through VirusTotal and their version of MB doesn't detect it either. I just get 2 hits with antiviruses I never heard of.

Link to post
Share on other sites

  • Staff

This has been whitelisted. Note: With rootkit on it lowers the whitelisting capabilities so fps may occur. You will just have to set an exclusion if its not detected with rootkit off. Rootkit is not needed 99.99% of the time. It should only be run when the normal engine cant remove something. 

Link to post
Share on other sites

15 hours ago, shadowwar said:

This has been whitelisted. Note: With rootkit on it lowers the whitelisting capabilities so fps may occur. You will just have to set an exclusion if its not detected with rootkit off. Rootkit is not needed 99.99% of the time. It should only be run when the normal engine cant remove something. 

Thanks for the explanation, I'll refrain from using it next time!

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
Back to top
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.