Page 1 of 1

Malicious code warning: Deep Space Pirates

Posted: Tue Feb 28, 2012 12:36 pm
by Greyth
Hi, I searched for an appropriate thread but couldn't find...

I went to download the Deep Space Pirates oxp and Chromium warned that the file appears to be malicious :o

Re: Malicious code warning: Deep Space Pirates

Posted: Tue Feb 28, 2012 12:45 pm
by Fatleaf
Confirmed, I too am getting the "This file appears to be malicious" box with a discard option. I am using Windows 7 with Chrome.
But you can choose the option to "keep" as well. There is an arrow for more options next to the discard button. I have just downloaded it.

Hope it helps.

Re: Malicious code warning: Deep Space Pirates

Posted: Tue Feb 28, 2012 1:19 pm
by Eric Walch
Greyth wrote:
I went to download the Deep Space Pirates oxp and Chromium warned that the file appears to be malicious :o
It is intentional that its a malicious oxp. The whole purpose of it is to place pirates in front of the player :P Im am just surprised that chromium examines files that thorough including the meaning of the code.

Anyhow, it contains only textfiles I know and the version 17.0 of chrome for the mac (updated today) does not complain.

Re: Malicious code warning: Deep Space Pirates

Posted: Tue Feb 28, 2012 1:31 pm
by Fatleaf
I have just downloaded another OXP and got the same warning message. I think Google has changed something that is giving the warning. You can still choose the option of 'keep' so you can download it.

Re: Malicious code warning: Deep Space Pirates

Posted: Tue Feb 28, 2012 1:38 pm
by Greyth
Actually, thinking about it, I got an update for Chromium from Canonical about 24 hours ago. I'll redown some OXP's and see if it's a general issue. Thanks for allaying my concern... there is the matter that other users may be put off by such a warning?

Re: Malicious code warning: Deep Space Pirates

Posted: Tue Feb 28, 2012 1:55 pm
by Greyth
I did download 5 oxp's and 4 were reported to appear malicious. So, it doesn't affect all oxp's - only some. How singularly odd.

Re: Malicious code warning: Deep Space Pirates

Posted: Tue Feb 28, 2012 2:08 pm
by Smivs
Is there any common ground, for instance are the 'malicious' ones from the same hosting site or anything like that?

Re: Malicious code warning: Deep Space Pirates

Posted: Tue Feb 28, 2012 2:14 pm
by Fatleaf
Smivs wrote:
Is there any common ground, for instance are the 'malicious' ones from the same hosting site or anything like that?
Good question. I have only been getting this from today.

Re: Malicious code warning: Deep Space Pirates

Posted: Tue Feb 28, 2012 2:17 pm
by maik
Could be it checks for JavaScript code...

Re: Malicious code warning: Deep Space Pirates

Posted: Tue Feb 28, 2012 3:36 pm
by Thargoid
Ditto for me - just downloaded the 3 zips for YAH and two warned about malicious code. The combo sets (A-F, "Yaw_V4.zip") didn't trigger, but the other two ("YOUR_AD_HERE v 4.1.7.zip" and "YOUR_AD_HERE_set_G.zip") both did. This being under Win7 and Chrome 17.0.963.56 m.

Re: Malicious code warning: Deep Space Pirates

Posted: Tue Feb 28, 2012 4:50 pm
by DaddyHoggy
Considering Set G is the one I uploaded I can confirm that I am too inept to include any malicious code!

Re: Malicious code warning: Deep Space Pirates

Posted: Tue Feb 28, 2012 5:02 pm
by Eric Walch
Maik wrote:
Could be it checks for JavaScript code...
Probably not, considering:
Thargoid wrote:
"YOUR_AD_HERE_set_G.zip") both did.
That oxp only contains .plist files, .dat files and .png files.

A bad thing, because when you get to many false alerts, you start ignoring them...

Re: Malicious code warning: Deep Space Pirates

Posted: Tue Feb 28, 2012 5:50 pm
by JazHaz
I just got this for OoDebugConsole too.

Re: Malicious code warning: Deep Space Pirates

Posted: Tue Feb 28, 2012 5:57 pm
by Smivs
This sounds like a little bug in Chrome to me...expect a patch any time now.

Re: Malicious code warning: Deep Space Pirates

Posted: Fri Mar 02, 2012 12:34 pm
by JensAyton
There was a problem with overzealous anti-virus programs a while back; it seemed to be because openstep-style plists were interpreted as “weird” JavaScript.