>> My virus checker has found the following on my system, can anyone tell
>> me how to remove it, Im told there is a fix on windows.update but when
[quoted text clipped - 4 lines]
>> Settings\Shazza\Application
>> Data\Sun\Java\Deployment\cache\javapi\v1.0\file\Dummy.class-4253870d-51ed4935.class
> I do not have the answer. What I normally do is to Google for the Virus
> and usually find a resolution. This is not a virus but a Trojan.
I don't think Trojan is a particularly good label for it - you don't
appear to need to accept that it is to be trusted. Presumably it does
not spread, so not a virus. But if you run an (unsigned) applet you
should expect to be safe (so long as your JRE is up to date).
> I understand that to avoid this problem in the future, set you Java cash
> to 0.
That will just stop it being reported. It wont stop you running it, you
just wont know about it.
The important point is that the file is just cached on your machine -
*it is not being reported as functioning*. So long as you have a
reasonably modern JRE (or no JRE at all), you should be okay.
> Sorry I could not be more specific but you will find that by using Google.
Googling is good. The virus checking tool even gives you some keywords
to go on. Understanding the pages returned might be more difficult.
Tom Hawtin

Signature
Unemployed English Java programmer
http://jroller.com/page/tackline/
IchBin - 06 Jun 2006 15:55 GMT
>>> My virus checker has found the following on my system, can anyone
>>> tell me how to remove it, Im told there is a fix on windows.update
[quoted text clipped - 12 lines]
> not spread, so not a virus. But if you run an (unsigned) applet you
> should expect to be safe (so long as your JRE is up to date).
I only call it a Trojan because it will not spread like a virus. Also
all of the references I have found on the Internet call it a Trojan. I
did not take the liberty to call it one by my own derived definition.
>> I understand that to avoid this problem in the future, set you Java
>> cash to 0.
I only mention this so that once the OP finds the files and deletes them
that by setting the cash to zero this will prevent this from happing
again. This is recommended again from what I found out on the Internet.
> That will just stop it being reported. It wont stop you running it, you
> just wont know about it.
[quoted text clipped - 5 lines]
>> Sorry I could not be more specific but you will find that by using
>> Google.
Most of the sites I found ask for some repost like the HijackThis
program and two other programs. From this they can determine which files
to delete. A lot of the references and recommendations are not very
foreword but some did give a satisfactory resolution.
> Googling is good. The virus checking tool even gives you some keywords
> to go on. Understanding the pages returned might be more difficult.
>
> Tom Hawtin
Thanks in Advance...
IchBin, Pocono Lake, Pa, USA
http://weconsultants.servebeer.com/JHackerAppManager
__________________________________________________________________________
'If there is one, Knowledge is the "Fountain of Youth"'
-William E. Taylor, Regular Guy (1952-)
Thomas Hawtin - 06 Jun 2006 17:39 GMT
>>> I understand that to avoid this problem in the future, set you Java
>>> cash to 0.
[I've put the quoted text back into the correct order. -- th]
>> That will just stop it being reported. It wont stop you running it,
>> you just wont know about it.
> I only mention this so that once the OP finds the files and deletes them
> that by setting the cash to zero this will prevent this from happing
> again. This is recommended again from what I found out on the Internet.
That wont do anything to stop the hostile code working. It will just
mean that virus software wont come up with the inappropriate warnings.
Switching off the cache seems like a daft thing to do.
Tom Hawtin

Signature
Unemployed English Java programmer
http://jroller.com/page/tackline/
Oliver Wong - 06 Jun 2006 16:51 GMT
>>> Exploit/ByteVerify
> The important point is that the file is just cached on your machine - *it
> is not being reported as functioning*. So long as you have a reasonably
> modern JRE (or no JRE at all), you should be okay.
From what I saw on websites, this virus/trojab/whatever seems to be
exploiting flaws in the Microsoft JVM. Since AFAIK, MS has stopped making
updates for this JVM, users will never see a "Your JVM is out of date,
please update it" message.
So it might be worth mentioning that anyone who is using a Microsoft JVM
should probably uninstall it and replace it with a JVM from Sun:
http://java.sun.com/j2se/1.5.0/download.jsp (click on the "Download JRE"
option, not the "Download JDK" option).
- Oliver