Hi there.
Just completed a Full System Scan (FSS) which picked up a single Trojan.Gen.2 type Virus in my local Java cache...

File Insight says, as above, "This threat has been removed. No further action is needed." Also note the part where it says "Deleted." As a matter of fact, the file was not Deleted but a notification sent to Quarantine.
When I clicked on locate, above, it clearly showed me the file in it's original place within the filesystem.
Upon checking the properties on the file it was modified (presumably to take out the offending code.)
I then proceeded to Delete it the entry from Quarantine and all is fine.
So my question is, why say something is removed and deleted when an alert is sent to Quarantine and the file is still present in the filesystem?
Is it just the Virus (threat) which was deleted from the modified file?
I thought that the entire file (or a copy of it) goes to Quarantine, no?
Just need to fine-tune my mindset. 
Thanks,
Atomic_Blast :)
P.S. The Virus (if it is one) was planted on my system within the last 72 hours. How did it get there in the first place?
It seems that this Virus is not new. Could it be a FP? 
Hi there,
Gave my previous post some additional thought. 
I think that the file was modified, since the virus was stripped from it and the file repaired.
When it said that the "threat" has been removed, the software is referring just to the virus.
The word "contained in" is the actual file before being modified.
If this logic is correct, then only four questions remain...
1) When something is sent to Quarantine, is it a actual copy of the file and/or just an alert?
2) Under what exact conditions is a file actually deleted from the system, versus sent to Quarantine?
3)The Virus was planted on my system within the last 72 hours sine the last FSS. How did it get there in the first place?
4) It seems that this Virus is not new and could encompass many things. Could it be a FP?
Clarification appreciated.
Thanks!
Atomic_Blast :)
Hi Atomic_Blast,
Quarantined files are essentially compressed, inactive copies of infected files that have been removed from your hard drive. They are retained in Quarantine so that you can restore them if their removal results in other problems such as connectivity issues or system performance problems - sometimes it is better to have an active infection and a computer that works than a clean computer that no longer functions because a removed virus has taken a critical file with it. Once a threat has been qurantined and your system shows no signs of distress, you can clear the Quarantine entries, which will permanently delete the file.
Java is a big target for malware writers. I keep the Java plug-in disabled in by browser until I am at a site that requires it, which most do not. You should also go into your Java settings and clear the cache and then uncheck the option to "Keep temporary files on my computer." See the following for information on how to do that:
http://www.java.com/en/download/help/plugin_cache.xml
Hi SendOfJive:
Thanks for the response.
I understand what you are saying but the infected file in question appeared to be handled like this -
Infected file detected -> Virus removed -> Modified file written back to filesystem -> Original file in Quarantine.
Is that correct?
If so, kindly advise on items 3 & 4, as to why NIS detected this older Virus during a complete
Full System Scan the other day and not before the last 72 hour period, in which a FSS was run.
How did it get in? Could it be a new variant?
I appreciate your help! 
Atomic_Blast :)
I am not sure what vukavuka.class is or how it got on your machine. Have you run any Java applets lately? Is your Java program up to date?
Hey SendOfJive:
Java is up-to-date - Version 6 Update 30, installed over one week ago.
Uninstalled old version and used CCleaner to get rid of the extra garbage.
Then cleanly installed new revision, as above.
A bit weird, I think... Glad that the "virus" was limited to the Java Cache, yet it got through.
Thanks,
Atomic_Blast :)
Atomic_Blast wrote:
Hi there.
Just completed a Full System Scan (FSS) which picked up a single Trojan.Gen.2 type Virus in my local Java cache...

[...]
(I've read the rest of your thread as of the date of this post - just required your screenshot above to make the comparisons easier!)
The '[Contained In]' part of the detection assessment that you've provided above indicates that the host 'jar_cache*.tmp' file in question was most likely a container file, similar to an archive file format like a zip file.
When archive files are scanned, files considered threats are deleted from the archive but the archive itself remains intact as it may contain other files that are not malicious. Consequently, the 'vukavuka.class' file was deleted from your 'jar_cache*.tmp' archive with the 'jar_cache' archive being left in place in it's original file location.
To illustrate with a more obvious example, the 'eicar_com.zip' test file below was downloaded from the usual site. As expected, Norton allows this zip file to be downloaded without incident. If an on-demand scan is performed on this archive, then you get results similar to yours:

The 'eicar.com' file inside the archive was deleted/quarantined and the 'eicar_com.zip' file remained intact (albeit empty). If you were to purposely try and extract the file within this archive, then Norton Auto-Protect will jump in and block this 'malicious' test file.
So, if you download this test file and do nothing ie simply let it sit there, then nothing will happen; it's no threat to your machine. Essentially, this zip file is inert. If a Full System Scan runs, either automatically or manually, and you have Norton configured to scan compressed files, then the 'eicar.com' file within this archive will be detected as a result of this scan. The detection date will be date when this file was detected rather than the date when this file actually arrived on your machine.
Given this behaviour, it kinda makes questions 3 and 4 redundant.
I hope this clarifies things.