Author Topic: bkdr troj pjam35 found  (Read 6344 times)

0 Members and 1 Guest are viewing this topic.

infinisri

  • Guest
bkdr troj pjam35 found
« on: May 16, 2003, 11:31:44 AM »
I detected PJAM35 with a BKDR DELOADER.
Avast 4 missed it.

I was able to catch using Trend-Micro HouseCall.

Does that mean my signature db is not up to date?
Or does Avast miss some.

Offline raman

  • Avast Evangelist
  • Advanced Poster
  • ***
  • Posts: 1062
Re:bkdr troj pjam35 found
« Reply #1 on: May 16, 2003, 11:40:08 AM »
Did you update your Avast Version? What kind of OS do you use, if i remeber that Backdoor needs Winxp!? Do you still have the file? If so, send it to support@asw.cz or to exclude a false alarm from Trend, you can use this link to test the file with Kav:  http://www.kaspersky.com/remoteviruschk.html
MfG Ralf

infinisri

  • Guest
Re:bkdr troj pjam35 found
« Reply #2 on: May 16, 2003, 06:53:32 PM »
I am running Win2K on a Sony Vaio laptop.

The PJAM35 was an exe file, so I promptly deleted and cleared recycle bin and rebooted.

I do not think it was a false alarm from Trend. There was an associated file also called ~glh<something>.tmp
which was stored in the WinNT\System\Fonts file.

If it occurs again, I will send the file by email before eliminating it.