Are These a Problem?

I just finished running an in-depth AV/Trojan scan with Online Armor, and had the following suspicious files listed.  Are these legitimate?

 

3,404 views 9 replies
Reply #2 Top

Every once in a while false positives pop up.  I can't imagine that SD is going to allow anything nasty to happen.  What I would do though is email support@stardock.com and give them the information that way they can get back to Online Armor.

Reply #4 Top

Since these are Skin files and not WB's files I believe it would not fall under a WB false positive. but it still could be a false positive..

It suprises me that all of a sudden it finds a 4 year old file suspicious, as I doubt you installed the skin any time recently since its no longer available here for download. So IMO i think it would be a false positive, but if you dont want to take the chance you can always remove it.

 

I was going to download and investigate it but alas as I stated earlier is not available for download..

Reply #5 Top

Tim offered me a link to the skin at Skinbase... I have downloaded it and scanned it with AVG8, I even unpacked the WBA and scanned the files individually. It has come up with no suspicious files.

From what I can remember an image can contain a virus, but it would need the coresponding Exe to run it. Which WB would not be. So as far as I can tell even if the files were infected.. without the exe used to extract and run the data it would be rendered null.

Hopefully yrag or someone with a bit more knowlege can confirm this..

Reply #6 Top

Thanks guys.  I'll be sure that Stardock gets this just so they can contact OA and report it as an FP.:thumbsup:

Reply #7 Top

Glad it wasn't a nasty in your 'puter, Ed.

Reply #8 Top

That's a weird one.  We've had false positives in the past of .dlls and what not in the apps themselves, but to detect bitmaps as a threat is unusual.  Not really much we could do with them, as it's not detecting part of the app itself, other than report a false positive through the same channels as anyone else.

Any report on what it actually detected them as?

Reply #9 Top

Maybe the scanner didn't know what to make of the spaces at the end of the file name? Do the other files (in that folder) have similar spaces before the .bmp?