Is this Java Agent BH BJ BK something to worry about??

this was moved to the virus chest,from zipped backups on J Disk…

why on the J disk, and why mbam didnt find anytging im not sure.

is this actualy a virus, if so what should i do next, thnaks

As it was moved to the chest, don’t worry…!!
Keep it there. You can rescan/delete/restore it later, if needed.
If you think it’s a FP, you can report it from the chest.
asyn

cannot select any options, apply is also greyed out, in the chest…oops my bad,

i was looking from scan logs instead of directly in maintenance, chest,

so ill leave it for now, how long can it stay in chest, or is it based on size of chest?

Right clicking should give you the options…!!
asyn

yes, thanks, if it were to stay in chest, or be deleted, do you think this might affect me when restoring that particular backup from J:…

It can stay there forever, don’t worry - it’s safe. :wink:
asyn

As much as I can see in your screenshot, these files are related to java, so there shouldn’t be any problems…
asyn

whe i went to correspond. folder in c drive, it was empty…weird it finds this on J: , but not c:, thanks

full path below:

scan once with malwarebytes with full system scan but update it before. If you have time download also SAS (superantispyware), update it and make a full system scan :slight_smile:

Regards,
Tenko

ok,

now im getting these new java temp files in the virus chest, on my full custom scan …it SEEMS like since ive had these the computer is having problems shutting down properly and according to my power options (maybe just coincidence)…

  1. is this something seen before (i couldnt find much info)

  2. are they real threats

  3. can i just leave them in the chest, then delete

That avast5 temp folder should be empty after a successful scan, the contents of that folder are copies of files that avast unpacks/imports, etc. so they can be scanned.

So I’m just wondering why they remained in the avast5 folder, it should be empty. This has in the past been associated with having another security application running at the same time. When avast unpacks/copies files into this folder the other resident scanner, lock the file and scans it, that act may stop avast scanning that file and clearing it from the folder.

So the next time you run a scan avast finds the old contents in the folder and alerts.

  1. Since these came from the avast5 temp folder there is no issue of getting rid of them from the chest as the were temp files.

Thank you David, i assumed it might be bad news when i saw the [Trj]

the only other scanner is Windows Defender

thanks again

You’re welcome.

It can, but what If will be chest full? Then the next infected files be deleted, or the chest capacity will be automatically larged?

The chest is unlikely to get full, it shouldn’t be that regular occurrence that you get an alert, if you are getting them or such a regular basis, I would review your security safe practices ;D

There is no rush to delete anything from the chest, a protected area where it can do no harm. Anything that you send to the chest you should leave there for a few weeks. If after that time you have suffered no adverse effects from moving these to the chest, scan them again (inside the chest) and if they are still detected as viruses, delete them.

still don’t know what happens If your chest will be full?
anyway nice christmas everyone!

You would get a message saying so, it is more often the size of the file being bigger than the maximum size, rather than the chest being fully. The default size is 256MB, which can be changed as can the max file size to be sent.