IMPORTANT: Possible Trojan horse detected in uploads

Posted:
4 Nov 2005 at 02:02
Source:
NickPOL and Trafton

*** UPDATE – Initial results seem to have been a false positive. The files appear to be clean. -Trafton ***

Just to be clear, although it should be clear to anyone reading this post, the user mentioned was not at fault at all and did nothing wrong. There was no other way in my opinion to handle this issue, users had to be warning, but it’s a regret that due to false positives by virus scanners someone’s name ended up on the frontpage like this. – FQuist


Tests run on several programs by Gunout have resulted in inconclusive results for Trojan horses. This does not mean that Gunout has done anything wrong. We are simply being careful with these inconclusive results and have submitted them for further analysis.

If you have downloaded one of the following files, please do not run them at this time:
Online Race(UnlockRace.exe)
Online Race(jj2rugunout.exe)
jj2 hidden colors(j2color.exe)
Online Cooperative Game(jj2cap.exe)
online cooperative play(jj2captsf.exe)
JJ2 Speed Unlocker(jj2speed.exe)

If you have ever ran any of these files, please contact Trafton for investigative purposes, via PM, MSN Messenger, or AOL Instant Messenger. If you have formatted your computer since you ran these programs, chances are that you are safe. It is not necessary to format your computer to remove the keylogger if there is one, though.

This may very well turn out to be much fuss over nothing, but nothing is definitive at this time.

- FQuist and Trafton


Comments

cooba on 4 Nov 2005 at 14:26

I used to run SpeedUnlocker a while ago… ;|

Past of Leveldesign on 4 Nov 2005 at 17:03

I searched with Google for “Hotkeyshook.A” and mentioned, that there are many gaming-communitys with users who found hotkeyshook.A in a File. All of these use NOD32 btw ;)

—Nick [PoL]

The - Wrath on 5 Nov 2005 at 00:14

Thanks for trying to scare people then.

Lark on 5 Nov 2005 at 17:24

No idea what this is about. But anyway. I’d like to leech off of this newspost to tell everyone that I’m going to do the featured download eventually, and I’ve just been busy lately.

Username on 6 Nov 2005 at 09:45

A public apology should be offered since this was a false alarm. Simply stating the files were harmless seems inconclusive on behalf of that uploader’s dignity; which is hardly encourging for that particular user, or users new and old, to submit material.

Grytolle on 8 Nov 2005 at 10:42

What is speed unlocker? ;S

minmay on 9 Nov 2005 at 02:44

Way to scare the community. =D

FQuist on 9 Nov 2005 at 18:17

“Username”: I’m not sure about this. While of course we do regret that all this caused a user’s name to be put on the frontpage and his programs be named as suspect, I do not feel we have been able to help any of this – we hardly are responsible for how multiple virus programs, and even a proffessional virus lab, detected a keylogger in this file. There was nothing else we could have done with the information we had – there was a high possibility the files were suspect, and one has to protect the site users too. I think this was handled with care, and never was Gunout definitely accused of being a hacker.

I have large doubts this would make people upload less files. Surely an utility developer has to understand not all files on the web are safe and that safety must be ensured.

Username on 13 Nov 2005 at 06:42

I suppose I should explain my post, though I thought it was simplistic enough and straight forward.

I had simply stated that the user in question should receive a public apology. I actually agree with the quite justifiable need to notify the public of potentially harm; HOWEVER, since the warning was inaccurate, the staff should have apologized to that user, and the community for that matter, for any inconveniences the warning may have caused and for any humiliation or negativity the uploader may have experienced. Consider the uploader’s feelings, the community’s concern, and the image of the site, for that matter. Remaining rather alooft on putting a proper conclusion to ALL parties involved to the site’s understandable error can create a negative image of those involved in this site’s upkeep not taking responsibility for mistakes – including honest ones. It just comes across as being thoughtless and even rude to brush this issue aside without a proper, courteous conclusion. True, the site was not legally responsible for any uploaded material, but the site WAS responsible for posting the warning, and thus, was responsible for any injurious effects or feelings towards that uploader, or any uploader in this situation, and to the community itself. If you regret posting a user’s name on the main page, why not apologize? Online or offline, proper manners should be upheld, especially when one is serving the public.

Yes, it was much appreciated to warn the community about potentially illicit software; I’m just simply stating the only thing missing was an apology – even if a short one.

After all, what harm can an apology do? Better to apologize than to appear pretentious or thoughtless.

Username on 18 Nov 2005 at 07:27

“it’s a regret that due to false positives by virus scanners someone’s name ended up on the frontpage like this”

Thank you for taking my point into careful consideration. A simple, outright apology to that user would have sufficed, but very professional mannerism and this is a significant step in concluding this issue properly. Commendable effort, and perhaps now with this small reminder, all parties involved will receive proper respect and consideration where due if an event such as this were to occur in the future.

Here’s to a staff that listens.

American on 20 Nov 2005 at 00:22

I’d be happy to give a public apology, but I do not think this person uses J2O or JJ2 anymore.

Username on 22 Nov 2005 at 07:27

Still, there may be a chance that user could come back – if not now, some day in the distant future. You shouldn’t entirely discount this as a loss; which is precisely why a formal public apology can do no harm. Thanks to FQuist for doing so.

Oh well. A lesson learned. We all make mistakes.

Post a comment

You need to log in to post comments on this newspost.